Now that you learned all about Event triggers and how to select the event you need, we will look at the next: Actions.
Actions perform the magic in your CRM or Helpdesk. They can create tickets, text messages, emails, logs or make your call leave a queue.
You can perform a great variety of actions. In combination with events you have many possibilities to automate your processes.
|call||Actions that are related to an active call|
|Hangup call||This action hangs up the call. The caller will be disconnected||Usually, when a call reaches the end of a call flow, it will end automatically. However, you might want to hangup a certain type of call, for instance from a specific number or a certain country so customers don't have to pay too much while waiting (you might combine this with a callback)|
|Actions that are all about emails|
|Send email||With this action you can send an email to a predefined email address.||A common use case is a voice mail: in case you have a small team without a help desk or CRM integration, you want to make sure your team receives an email with the link to any voice mail a customer left.|
|zendesk||Actions in Zendesk|
|Lookup enduser||This action searches, based on the phone number, for the enduser in Zendesk.||If you want to attach a ticket to an end-user in Zendesk, select this action. You will need another action "Update ticket" to assign it. This action, however, is required to enable this process. Usually, you will use this action with the event "Inbound Call" or "Call Created".|
|Create ticket||To create a new ticket for an incoming or outgoing call use this action.||There are many different use cases why you would want to create a new ticket. Very often, customers want a new ticket for every incoming call, some like to have a ticket for a voice message or whenever a call is bridged. Decide what process fits your business needs best.|
|Update ticket||This action will update the Zendesk ticket associated to a call or task. It will only fire if there already was a ticket created.||There are many reasons why you would want to update a ticket. Updates are used for assigning tickets to end-users and agents, for adding wait- and talk-time, details about the caller, recordings, etc. You can combine this action with most events. For instance, "Recording Finished" and "Update ticket" gives you the option to add any recording as soon as a recording ended.|
|Push ticket||Push a ticket to the agent taking the call.||In most cases, this action is used in combination with call bridged. Whenever an incoming call is connected to an agent, the ticket will automatically pop-up so the agent doesn't have to search the queue for the ticket. It can also be used when calls are transferred between agents.|
|queue||Queue related actions|
|Leave queue||A call leaves a queue to continue to another application module.||You want a call to leave a queue if you guide it to the next step in your call flow, for instance you want to offer the customer a callback or voicemail option or forward the caller to a queue with other agents (for instance overflow).|
|sms||Actions with SMS|
|Send sms||At any given time you can send a text message to a customer.||Often, this action is used to confirm a callback request. For instance, a customer pressed 1 for a callback, she will not only hear a confirmation on the phone but also receive a text message (in case she called with a mobile phone).|
|transaction||Transaction related actions|
|Create transaction||If you want to create a transaction at any given time, this is the action you want to use.||Some customers log callback requests with transactions. So for instance, whenever a call is finished and the customer opted for a callback request, this action will log this request as a transaction.|
|HTTP callback||Send a HTTP callback to any system.||babelforce allows you to send data to external databases or sheet services as for instance Google sheet. You might want to log every instance an agent changes their presence state and log the current state and time in Google. This you can do with a http callback.|
|log||Log message actions|
|Log message||Create an extensive log message. This action is mainly used for debugging call flows.||Whenever you are designing or redesigning your call flow, you might want to see some more extensive information in your live logging. This action will print more detailed information about, for instance, your expressions.|
|Set variables||This action allows you to set and define a session variable.||Session variables are a powerful tool. They allow you to store information about a call or a task that you can later use in your call flow or print in your logs or tickets. For instance, whenever customers call a certain number, you can set a session variable that defines the brand and then print this information in the ticket so you know for which brands customers contact your service.|
|babelforce||For some actions you will be using a babelforce integration. This means you integrate your own babelforce login and perform events in your own system. There are some great features available as you will discover.|
|Lookup enduser||babelforce searches for an end user in any integration.||If you want to use end user data in your call flow, for instance send an email to a user, you can use this action to retreat the end user's email address from your crm or help desk. babelforce then stores the information in a placeholder for end user email address. Use it for sending out an email to the customer calling your service.|
|Upload lead to list||You can instantly add a phone number to an outbound dialer lead list.||Imagine you have a customer selecting a callback. The moment this customer pressed the key for a callback, her number is added to the automated outbound dialer campaign. One of your agents is logged into the campaign and will, within seconds, be connected to the customer and solve the request|
|Push data to an agent||This action allows you to push data to babelConnect.||This feature is very useful if you want to enable agents to quickly access an external link. For instance, when the customer called, he was asked to enter the order number. As soon as the call is bridged, the agent will receive a link in babelConnect that will lead her to the customer's order. Great, right?|
|freshdesk||Actions in Freshdesk|
|Create a ticket||To create a new ticket for an incoming or outgoing call in Freshdesk use this action.||There are many different use cases why you would want to create a new ticket. Very often, customers want a new ticket for every incoming call, some like to have a ticket for a voice message or whenever a call is bridged. This is all depending on your individual processes.|
|Update a ticket||This action will update the Freshdesk ticket associated to a call or task. It will only fire if there already was a ticket created.||There are many reasons why you would want to update a ticket. Updates are used for assigning tickets to agents, for adding wait- and talk-time, details about the caller, recordings, etc.|
|Add a note to a ticket||This little action allows you to add notes to an already created ticket||It's similar to the update ticket feature, however, it's more specific and quicker to setup. It gives you the option to add a note to a ticket, like informing the agent about the wait time of the customer.|
|Send email & create ticket||With this action you can send customers an email and leave a note in your Freshdesk about the email.||This is a little more difficult to implement but a great feature. Let's take the case of callback again. SMS are nice but you might not have the information about the SMS in your helpdesk. This action actually allows you to not only send an email to the customer as soon as he requested the callback. You will also have a note added to the user's Freshdesk account.|
|geckoboard||Actions in Geckoboard|
|Append data to dataset||With this action, you can add data to a Geckoboard dataset.||Your team uses Geckoboard? That's great. You can use this action, for instance, to show how many calls your team members took per day.|
|pushover||Actions for pushover|
|notify||If you use a push notification service, you can send notifications with this action.||Why customers use pushover notifications is very much dependent on each customer's processes. For instance, a pushover could be send if all agents presence state was switched to busy. If this condition applies, managers can receive a push notification to check on their team.|
Now you have a first overview of the actions that are possible in babelforce.
To round this up, there is one more field in every event that you need to fill out and this is "Triggers". For now, just select the standard trigger "Always" - we'll get to more complex setups soon enough.
Congratulations, you can now create your first own triggers: you know which event triggers are possible and we introduced you to all actions that can be combined with the triggers.
Let's start getting with some real examples. In the next sections we will look at a few use cases and explain how you implement them in babelforce.