- Print
- PDF
Virtual Agent 2.0 Workflow and Triggers
By default, VA 2.0 generates account notes when consumers interact with the system. There are specific triggers for consumer interactions within VA 2.0 available to customize workflow.
Caution
These triggers are designed to initiate specific workflows based on user interactions and actions within the VA 2.0 system.
Exercise extreme care when creating Action Paths to be applied to your workflow, as they have the potential to cause significant issues if not properly configured or executed.
Please be sure to review all potentially associated workflow before making these workflows active.
Available Triggers
Each trigger can be paired with an Action Path to automate responses to specific consumer actions in VA 2.0:
onAfterVirtualAgentDispute: Fires after a consumer submits a dispute from VA 2.0.
onAfterVirtualAgentDocumentsUploaded: Fires after a consumer uploads a document from VA 2.0.
onAfterVirtualAgentMessage: Fires after a consumer submits a message via the Contact Us page.
onAfterVirtualAgentPersonInsert: Fires after a consumer registers an account.
onAfterVirtualAgentPersonUpdate: Fires after a consumer updates their name, date of birth, or Social Security Number (SSN). Also fires after a consumer updates contact information.
onAfterVirtualAgentPersonContactUpdate: Fires after a consumer updates contact information (Address, phone, email). Default settings respect Do Not Call/Mail/Email/Text preferences from the primary account.
onAfterVirtualAgentPaymentDelay: Fires after a consumer delays payment.
onAfterVirtualAgentPaymentSkip: Fires after a consumer skips a payment.
onAfterVirtualAgentPaymentFail: Fires after a failed payment in VA 2.0.
VA Pages, Consumer Actions & Available Triggers
To fully leverage these triggers and create tailored workflows, you'll need to configure your action paths accordingly. Each trigger corresponds to a specific consumer action, allowing you to automate processes within VA 2.0.
Account Profile Registration Page
Action: Consumer registers a new account.
Workflow Note: Creates an account note when a consumer successfully logs in.
Setup Action Path Workflow: Set up the trigger onAfterAccountPersonInsert with an action path for customizable workflow.
Edit Account Page
Action: A registered consumer account is updated (e.g., Date of Birth or SSN update).
Workflow Note: Creates an account note for each change.
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentPersonUpdate with an action path for customizable workflow.
Note
When a consumer registers or updates account contact details, ACE only stores the new info if that data was previously missing on the primary account. Existing data is not overwritten unless Priority 1 fields are involved.
Contact Options Page
Action: A consumer updates their account contact details (e.g., email, phone, address).
Workflow note: Creates an account note for each change.
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentPersonContactUpdate with an action path for customizable workflow.
Caution
Both onAfterVirtualAgentPersonContactUpdate and onAfterVirtualAgentPersonUpdate may fire when contact details are updated. Proper configuration is essential to avoid duplication or conflict in workflow logic.
Default Behavior: All updates respect Do Not Call/Mail/Email/Text preferences on the primary account.
Dispute Page
Action: Consumer initiates a dispute within VA 2.0.
Workflow Note: Generates an account note containing the consumer's provided reason, along with file names if attached.
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentDispute with an action path for customizable dispute resolution.
Document Upload Page
Action: Consumer uploads a document.
Workflow Note: Creates an account note with a message from the consumer (if provided).
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentDocumentUploaded with an action path for customizable workflow.
Contact Us Page
Action: A consumer submits a message.
Workflow Note: Creates an account note with the message from the consumer.
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentMessage with an action path for customizable workflow.
Modify Plan Page
Scheduled Payment Delay
Action: Consumer delays a payment
Workflow Note: Creates an account note with payment delay information
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentPaymentDelay to handle delayed payments.
Skip Payment
Action: Consumer skips a payment
Workflow Note: Creates an account note with skip payment information
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentPaymentSkip to handle skipped payments.
Note
When an agent sets up a Promise Plan in the ACE UI, it won't be visible to consumers in the VA 2.0. This means that consumers are unable to make any changes to the promise plan created by the agent. Instead, consumers have the option to either make a one-time payment or establish a secure Payment Plan directly from the VA 2.0, and these two payment methods can operate simultaneously.
Failed Payment
Action: Consumer payment made via VA fails.
Setup Action Path Workflow: Set up the trigger onAfterVirtualAgentPaymentFail with an action path for customizable workflow.
Read Creating an Action Path for additional information.