Dispatch and field work
Assigning an on-call technician following your rotation, then tracking a job until somebody closes it.
ServiceTitan
Your request is written into Zenvox. At ServiceTitan, access runs through a partner status nobody has established — and this page rounds none of it up.
7 days, 20 answered calls, no card
Where your request lands
The request is written into Zenvox: customer, address, type of work, urgency and availability. ServiceTitan keeps the truth of your dispatch, your estimates and your invoicing; nothing is written there today. Your dispatcher picks up a qualified request in the morning, with its recording, instead of a message to retype.
Research stayed careful on this vendor, so this page does too. An interface getting started guide plus an integration environment are documented; booking, estimating, dispatch and payment need endpoint by endpoint verification. Access runs through a request, a vendor relationship and a partner status nobody has established, while an event catalogue remains unvalidated.
ServiceTitan is operations software for companies with several trucks and dispatch running all day; the receptionist replaces no dispatcher, she works while he is busy.
Read, create, update, cancel
On this vendor, research stops at documentation, and confidence it grants itself is low. Four lines reflect that, rounding nothing up.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Finding a customer, job or appointment is described. Access depends on an accepted request plus partner status nobody holds yet. |
| Create | To qualify | Creating a booking and an estimate appears in getting started material. Every write endpoint gets verified on its own ahead of any announcement. |
| Update | To qualify | Moving a visit assumes a validated event catalogue. There is none; failing that, periodic re-reading would have to be sized, which is different work. |
| Cancel | To qualify | Cancelling crosses dispatch and payment. Until both chains are proven separately, a receptionist leaves them alone. |
What is included, what needs an add-on
Answering every call, qualifying, telling a no heat emergency apart from a maintenance request, alerting a right person: that is your base. A ServiceTitan connection would save retyping tomorrow morning; it changes nothing about what a receptionist does during a call.
Authorisation, and where truth sits
On this vendor, access gets requested well ahead of any engineering.
- Access gets requested from this vendor; partner status plus narrow scopes condition any opening
- Its integration environment may hold a copy of your production data: dedicated test accounts come first
- A system of record gets chosen per object — customer, job, appointment
- You revoke authorisation whenever you want; a receptionist returns to native mode
Commercial terms, along with feature coverage in Canada and in French, were left unestablished by research.
Ten at night, during a cold snap. No connection is authorised; a receptionist works in native mode.
CustomerWe have no heat. Our furnace shut down and my house is getting cold.
ReceptionistI will take a name and a callback number first. Is that unit fully shut down? And is anybody elderly or a baby at home?
ReceptionistI am flagging a no heat emergency, along with an address, postal code and equipment type. An on-call technician gets alerted immediately, then calls you back with a window.
An emergency reaches a right person at night, while an ordinary queue waits until morning. A dispatcher opens ServiceTitan tomorrow and finds a fully written request in Zenvox, alongside a recording and a transcript.
If no connection exists
That is today, and a structured company copes well enough until access opens.
- A request gets created in Zenvox, carrying trade qualification plus an urgency level
- An on-call technician gets alerted on his phone, waking up no dispatcher
- By morning, a queue reads at a glance and copies into ServiceTitan
- No base capability rests on partner status at this vendor
Questions about this connection
Is Zenvox connected to ServiceTitan?
No. Access runs through a request, a vendor relationship and a partner status that are not established, and nothing is written into ServiceTitan today. The request is written into Zenvox, with the customer, the address, the type of work and the urgency.
Does the receptionist replace my dispatcher?
No, she works while he is busy. She answers every call, tells a no heat emergency apart from a maintenance request and alerts the right person; in the morning your dispatcher picks up a qualified request with its recording instead of a message to retype.
What do we lose while access is not open?
The retyping tomorrow morning, and nothing else. The emergency reaches the right person at night, the morning queue reads at a glance, and no base capability rests on partner status at that vendor.
Can the connection be tried in a test environment?
That is the point to settle before the first interface call. The vendor integration environment may hold a copy of your production data, so dedicated test accounts come first.
Does everything work in French and in Canada?
Feature coverage in Canada and in French at this vendor was left unestablished by research, and so were commercial terms. On the Zenvox side the receptionist answers in French and in English, and that depends on no connection.
Where to next
See a trade concerned, or a full software list.
ServiceTitan