List of Triggers and Examples

In HubSolv, you can select from over 25 triggers to automate actions following certain events and in relation to different stages of your sales or product lifecycle. 

Below is a list of actions which HubSolv can trigger within the System. Please note this list is subject to change as new triggers are created and old ones become redundant.

See some examples below of these Triggers in action and what they are commonly used for. 

Trigger	Definition
Added to Campaign by User	Whenever a client is added to a campaign manually. When a client is added, what do you want to happen immediately?
Added to Campaign by Other Method (API, Import etc.)	Whenever a client is added to a campaign via something not of user interaction so an API Lead being posted in for example.
Status Changed	Whenever the status is changed on a client - what do you want to happen when a status is changed?
Assigned to User	Whenever a client is assigned to a user - when a user is assigned, what is then triggered? Further down the process, would an action to task the assigned user to chase the client for documents be of use?
SMS Received from Client	Whenever an SMS is received from the client - when you receive an SMS from a client, should there be an automated action as a result?
Email Bounced	If the email fails to send it will bounce back, this will cause this action to trigger
Email Clicked	Whenever the client clicks the email, it will cause this action to trigger
Email Dropped	If the email fails to send it will drop, this will cause this action to trigger
Email Opened	If the email is opened then this trigger will activate.
Email Spam Complaint	If we receive a spam complaint from the email being sent this will trigger.
Email Unsubscribe	If we receive an unsubscribe notification from the client from an email we sent then this action will trigger.
Document Sent	When a document is sent to the trigger this action is triggered.
Document Waiting Review
Document Signed	When the document comes back from Signable as signed then this action triggers.
Document Aborted
Document Expired
Bank Statements Requested
Bank Statements Received
Case Created on CreditorDesk
Email Received from Client	If we get an email back from the client then this trigger will activate
Notification Received	Whenever a notification is received from another hubsolv or an external API then this trigger will activate (Diallers for example)
I&E Updated (API)
I&E Item Expired
Life Insurance Asset Created
Legend: Bold = Deprecated

Added to Campaign by User - The example below is of a trigger set up to send an email to the client who has been created on the system manually by a HubSolv user. (Video with audio)

Added to Campaign by Other Method (API, Import etc.) - The example below triggers an SMS to go out automatically as soon as a new lead has entered the campaign. (Video with audio)

Status Change - The most commonly used Trigger for multiple situations. See a few examples below;

1. Trigger a workflow - Your automated workflow will need a trigger (likely based on a Client Status) to be put into action. The example in this video shows you how to activate a workflow based on a trigger for 'No Answer'. This can be used as a strategy for chasing non-responding leads or leads that HubSolv users haven't been able to get in touch with. (Video with audio)

For more information on Workflows click here

2. Send to a new campaign - Depending on your process, a client may be required to move from one campaign to another based on their status. The example below is of a trigger that will send the Client from the 'lead' campaign to the 'IVA Agreed' campaign where there will be a whole new set of statuses and process to allow the user to complete the case. In this example, the status to move the client from one campaign to the other is 'IVA Agreed'. (video with audio)

3. Send SMS - The example below is of a trigger which will send an SMS to the client immediately when the status is set to 'Scheduled Callback'. The scenario being that the client has got in touch to state when would be the best time for the user to call. this trigger can come with another action to task the user within the system to call the client. 

Assigned to User - The example below shows how the 'Assigned to User' trigger can task the user to chase the client for documents. 

SMS Received From Client - The example below shows the process when an SMS is received into HubSolv and a task is assigned to the relevant user to call them. You can also set a condition on this to be only when set to for example 'No Answer' status.

Email Triggers -   Bounced/Clicked/Dropped/Opened/Spam/Unsubscribe - These triggers are all based on leads/clients engaging with the email and what action needs to be taken subsequently after. For example, if an email has bounced, an action could be set up to send an SMS as a second way to get in touch. Other actions can be associated to these triggers such as moving the lead/client to a 'dead leads' campaign, for example, alerting all users not to contact them if they unsubscribe or mark the email as spam. 

For assistance on the rest of the available triggers contact the helpdesk ([e-mail])  and we will be able to help set up the relevant trigger for the action you want to perform.