This article briefly summarizes all the core mechanisms of the babelforce manager to create customer experiences and end-to-end service processes. If you want to learn about process flows in detail, we recommend you reading our tutorial. However, this article provides a short overview of the babelforce mechanisms.
You can control every aspect of both, the end-user journey as well as the back-end processing of information. The basic tools to design processes are:
1. Triggers - define conditions used to evaluate the current context (the Trigger releases a certain action, if all conditions are fulfilled)
2. Selections - dynamically choose the agents who will handle certain end-user interactions
3. Events - interaction and system Events that you can use to carry out an Action
4. Actions - provoke a change or trigger the next step in a component or an interaction channel
Here is an example scenario that can be created using all these control mechanisms:
The user calls the customer service hotline and the call is routed to the right agent in the contact center. The agent receives a ticket in Zendesk at the same time as the call arrives. The ticket already shows the name and details of the customer. The ticket is also tagged with information about the caller and the call.
How do you configure the babelforce manager to do this:
An inbound call to the babelforce telephone number for your contact centre (Event is "Inbound Call") results in the Action "Lookup end-user" in Zendesk and a second Action to create a new ticket.
Simultaneously, a Trigger checks that the called hotline number is the one of the support team numbers. This information is used to build a Selection of available agents who are in the support team. Other agents who handle other processes will not be called.
Once the agent accepts the call, the Event "Call bridged" is used to execute the Action "Push ticket" to that agent.
The Actions that influence Zendesk tickets are also configured to add tags with additional information so that Zendesk can process the ticket. The link between an Event and an Action can itself depend on a Trigger: e.g. only tag the ticket with "brand_a" if the support telephone number called matches "445012345555".
The same core mechanisms are then available for you to reuse them in all other kinds of situations. For example, the call can be routed in the IVR based on Triggers. Hence, you can define common sets of conditions in Triggers and make use of them repeatedly for all kinds of interactions and process implementations.