A caller describes a problem in ordinary language. ServiceTitan expects an operational job type. The integration needs a controlled mapping between the two, because the wrong category can change how the office plans the visit.
Treat classification as selecting from an approved business vocabulary. Do not let the voice agent invent categories or choose a technically specific repair diagnosis from a caller's short description. Preserve what the caller said separately from the selected job type.
Build the map with dispatchers
ServiceTitan describes job types as categories used during booking and visible on job records and reports. Review its job type documentation with the person who owns dispatch policy.
For each allowed type, document qualifying phrases, required questions, exclusions, priority policy, and when staff review is mandatory. Bind mappings to the client's configured identifiers. A label such as “No Heat” is insufficient if the integration points to another tenant or an inactive category.
Work through an ambiguous HVAC call
A fictional caller says, “The downstairs system won't come on, and I think the thermostat is broken.” Capture the reported condition and ask whether the request concerns heating or cooling. Do not convert the caller's guess into a confirmed thermostat fault.
If the approved map allows “No Heat” after that clarification, select it and retain the caller's thermostat comment in the notes. If the answer remains unclear, create a reviewable intake request rather than defaulting to a replacement or installation category.
| Caller statement | Proposed handling |
|---|---|
| “No heat downstairs” | Approved heating service category |
| “I want a new system quote” | Estimate request category |
| “It was repaired yesterday” | Ask about existing job, flag callback review |
| “Something smells dangerous” | Follow approved urgent escalation policy |
| Two unrelated systems | Ask whether separate requests are required |
These rows illustrate policy design, not a universal dispatch rule. The business must approve the mapping and the questions before callers encounter it.
Keep classification evidence inspectable
Record the original description, answers to required questions, mapping version, chosen category, and any human override. That makes a disputed category debuggable. A summary saying “AI chose HVAC repair” does not explain why.
A narrow map creates more manual review but fewer unsupported classifications. A broad map covers more callers while increasing the risk that vague language is treated as operational certainty. Start with common categories and expand using reviewed examples.
Review the proposed workflow alongside the HVAC project context, then test against the client's actual configuration.
Questions about job type mapping
Can the model choose from the full category list?
Only if the list and selection policy are appropriate for the workflow. Restricting to approved intake categories is easier to verify.
Should urgency determine the job type?
Urgency and work category are separate decisions. Follow the dispatcher's explicit policy for both and preserve reported safety concerns.
What happens when a category is renamed?
Review the identifier mapping and semantic meaning. A label change may be cosmetic, or it may reflect a new booking policy that requires retesting.