TaskRouter is an attributes-based routing system for your Flex contact center. TaskRouter uses Tasks to represent a unit of work that needs to be completed across your configured communication channels and provides a set of tools to allow you to intelligently route a task to the agent best suited to handle it.
TaskRouter includes a variety of objects, including Workflows, which are human readable definitions of your routing logic, and Task Queues, which represent key segments of agents. All of these moving parts come together to offer you customizability and scalability for your routing rules.
Flex uses Tasks to power many parts of your contact center, including:
Upleveling Agent Experience with Task Attributes
You can dynamically expose task data in the Flex UI. This helps to ensure that your agents have context for the work they’re doing, and even allows you to change the look, feel and features of the Flex UI depending on the current Task.
By default, TaskRouter understands that you’ll create tasks for sms and voice. You can also define custom channels, like WhatsApp, Facebook Messenger, or Web Chat. You can route tasks based on their channels, and render the channel to the Agent in the Flex UI.
As TaskRouter works, it generates a stream of valuable events and statistics about agent activity, task volume, and more. Flex can consume this Task data as the basis for workforce management in your contact center with Flex Insights.
TaskRouter for Flex differs from a vanilla TaskRouter implementation in the following ways:
Allows One Workspace
You’re limited to one workspace when using Flex. For majority contact centers, a single workspace is all you need, but you can work with your Twilio team to understand if this might be a limitation for you.
Now that you know a little bit about TaskRouter, why not try: