Proposed lead: Randi Thompson, with the buyer’s dispatch owner and integration engineer.
Why it matters: ServiceTitan documents configurable job types, dispatch-fee messaging, scheduling permissions and escalation. A buyer can therefore ask about specific configuration and records rather than accept a generic integration claim. (help.servicetitan.com)
Question to put to the expert:
For an AI answering service for plumbers or HVAC contractors, which integration tests distinguish a usable booking from a promise the business cannot fulfil?
A strong answer should cover:
- Correct service address, territory, job type and customer identity.
- The difference between an appointment window and a guaranteed technician arrival.
- Capacity, membership and dispatch-fee rules approved by the business.
- Separate permission to book, reschedule and cancel.
- Handling of unavailable capacity, unsupported work and requests outside approved scope.
- Whether a dispatcher can identify, inspect and correct the resulting job.
Evidence to request: Buyer-authored test calls linked to the actual job records and configuration used during the test.
Follow-up: Show us an out-of-area caller and a fully booked evening. What does the agent decline to promise?
Buying boundary: Treat native integration as a deployment characteristic to evaluate—not a substitute for testing.
Expert quote: [Reserved for an approved interview quotation.]