Control your Voice Agent's task creation with task types to optimize call containment

Prev Next

Mandatory Workflow Change

This change will automatically apply to all customers who have this feature enabled at the time of this release. Review the changes below.

Control your Voice Agent's task creation with task types to optimize call containment

This enhancement gives you three layers of control over post-call task creation and routing, allowing the Voice Agent to handle more calls independently and boost overall call containment.

Available inCoreProMax
Feature type
Enhancement
Industry
Residential Service and Replacement
Roles
AdministratorsCSRs
Region
United StatesCanada

What's changing

Before, the Voice Agent created tasks from every call the same way, with no way to control which call outcomes generated a task, no way to describe what a task type actually covers, and no way to route it to anyone specific. That lack of control meant many businesses chose to escalate more calls to a live person instead of trusting the Voice Agent to fully handle and record the outcome.

Now, you get three layers of control, and each one builds on the last:

  1. Choose which call outcomes create a task. Decide whether Booked, Unbooked, Excused, and Escalated calls each generate a task, so you're not stacking a Voice Agent task on top of a process you already have covered elsewhere.
  2. Build out specific task types with descriptions. Within each category, turn on the exact task types you want, and add a description so the Voice Agent knows precisely when to use each one, instead of guessing.
  3. Direct tasks to the right person. Assign each task type to a specific team member so it lands with whoever should actually act on it, instead of sitting unassigned.

Put together, this is what lets you push more of your call volume through the Voice Agent with confidence, because you now have the tools to make sure every outcome is captured and routed correctly, which is what drives call containment up.

Task type names are critical to how the Voice Agent matches a call, so clear, specific names matter. Descriptions won't fix a vague name, but they do add clarity on exactly which task should be assigned for a given call follow-up. This only creates tasks in ServiceTitan Task Management — it doesn't route to Task Hub or CRM Tasks.

Important: Out of the box, only your default task types from your ServiceTitan settings are turned on (often this is three task types). The Voice Agent only creates a task when a call outcome matches one of your enabled task types exactly. If a call comes in for something outside those defaults, such as a refund request, no task gets created for it at all, and there's no notification that one should have been. Review and expand your task types, and add a general catch-all task type, so calls don't fall through with no record, and you don't lose the containment gains this feature is meant to deliver. We recommend creating additional task types, per the examples below.

Workflow comparison — before & after

← Before
✓ After
1.The Voice Agent automatically creates tasks after certain calls.
1.Go to Voice Agent settings and open Skills & Capabilities.
2.Every task type is created the same way, with no option to turn any of them off or control which call outcomes generate a task.
2.Decide which call outcomes should create a task: Booked, Unbooked, Excused, and Escalated calls can each be turned on or off.
3.Tasks have no way to route to a specific team member automatically.
3.Go to the Task Types screen and turn on the specific task types you want within each category, and add a description so the Voice Agent uses the right one every time.
4.Assign each task type to a specific team member, or leave it unassigned so it goes to the Voice Agent.
5.Add a catch-all task type so calls that don't match a specific type still generate a task instead of getting dropped.
⚠ Businesses would need to review every escalated call and see if a CSR should call back, then route to the right person and handoff.
✓ Businesses can confidently let the Voice Agent handle more call outcomes end to end, since every one is captured and routed correctly, which directly increases call containment.

How it works for your industry

Residential Service and Replacement
  • A business already using Dispatch Pro to dispatch technicians on booked jobs turns off tasks for Booked calls, keeps Unbooked and Excused calls on, builds out specific task types like "Refund Request" and "Credit Card Update" with descriptions, and assigns billing-related task types straight to their billing specialist, letting the Voice Agent fully handle those calls without a live handoff.
  • A larger call center that already staffs every escalated call turns off tasks for Escalated calls, since their live team already creates its own follow-up record.

How to prepare

01
Start from a strong reference list rather than building task types from scratch. Go to Voice Agent settings > Skills & Capabilities and review the four call-outcome categories: Booked, Unbooked, Excused, and Escalated — this is where you turn on which call outcomes should create a task. We recommend starting with all four turned on, then narrowing down once you see what's actually coming through.
  • If you already dispatch booked jobs through Dispatch Pro, you likely don't need a task for Booked calls.
  • If your team already has its own process for escalated calls, consider turning off tasks for Escalated calls to avoid duplicates.
02
Whenever you change what escalates to a human, review your task types at the same time. If you stop escalating a certain kind of call, make sure a task type still exists to capture it, or that detail will be lost entirely.
03
Even starting from the reference list above, add a general catch-all task type so any call outcome that doesn't fit still generates a task instead of being silently dropped. Treat this as required setup, not optional cleanup.
04
Use the descriptions in the reference list as a starting point, but tighten the task type names themselves.
05
Decide which task types should route to a specific team member instead of defaulting to the Voice Agent.
06
Bookmark any knowledge base articles or Academy videos for team training, and share the "don't just turn it on and walk away" guidance with your team.