A caller receives “your visit is booked,” but the office sees an enquiry waiting for review. The integration may have created exactly the record it was designed to create. The spoken confirmation is what overstated the result.
For a ServiceTitan workflow, decide whether you are recording a request, creating a job, or confirming a scheduled visit. Do not treat those labels as interchangeable.
Why does the record type matter?
ServiceTitan's Scheduling Pro overview distinguishes jobs from booking requests and describes different places they appear for office review. Your particular integration must verify which operation and configuration it uses.
A saved request can be useful without being a confirmed appointment. It may capture enough information for dispatch to review availability and contact the caller. The problem begins when the receptionist claims a later stage has already happened.
Define confirmation from the office's workflow
Use a fictional service enquiry to agree on these states:
| State | What the caller can truthfully hear |
|---|---|
| Details collected | The receptionist has the requested information |
| Request saved | The office has a request reference |
| Review pending | Availability or approval is still outstanding |
| Appointment confirmed | The required scheduling checks and saved result are complete |
The final row needs a business definition. A job record alone may not establish a particular arrival window or assigned technician. Confirm those details with the client's operations team.
Return the record type, reference, status, and permitted confirmation wording from the integration boundary. Do not ask the language model to guess the meaning of an opaque success response.
Treat status transitions as separate operations
A dispatcher may review a request and create or schedule follow-up work later. Preserve the relationship between those records so staff can trace the original call.
If a caller rings again, the receptionist should not automatically create a second request because it cannot find a confirmed appointment. Search or reconcile using the approved identity and record references.
Also distinguish an update to an existing request from a new request. A corrected address should not silently remain only in the latest transcript while the office sees an older location.
Test what staff see after the call
For a proposed integration, inspect the destination screen with a fictional customer. Confirm the record's type, state, required fields, and follow-up owner. Then ask an office reviewer what they would do next.
Test a successful save, rejected request, uncertain timeout, repeated delivery, and later conversion into the office's next stage. Each should produce matching language and records.
The access-readiness guide covers prerequisites. The HVAC case study provides an example of keeping intake distinct from dispatch in my independent product.
ServiceTitan request questions
Can a booking request still be a useful pilot outcome?
Yes, if staff review is intentional, visible, and owned.
Does an API success response prove a visit is confirmed?
No. Verify the operation's business meaning and resulting record.
Where should confirmation wording be decided?
Agree it with operations and encode the allowed states before launching the workflow.