What we would aim for
After a call ends, a customer and a work order with the caller, the address, and the job details. The exact record, and how a returning customer is matched, would be confirmed against your account.
Field service
On requestIf the office dispatches from Service Fusion, the finished product is a customer and a work order there. That is what we would build toward. Today the receptionist books a calendar and texts your on-call number, and your office keys the job in.
On request. Not live. There is nothing to connect. We scope it with a shop that runs on Service Fusion.
After a call ends, a customer and a work order with the caller, the address, and the job details. The exact record, and how a returning customer is matched, would be confirmed against your account.
Access to your Service Fusion account for the connection, and a decision on which job type and status a phone call starts as.
Assign a technician or choose a time. Dispatch stays with your office.
Nothing is written for a call you answer. A call the receptionist takes would write after it ends.
The same, at any hour, so the morning starts with the overnight calls already entered.
What scoping would cover. Nothing to connect today.
What a phone call should start as in Service Fusion.
How the connection to your account would be authorized.
Adapter work is quoted at setup and tested before live calls.
Not yet. It is on request, scoped and quoted at setup.
Yes. It answers, books a calendar slot, and texts your on-call number. Your office enters the job.
No. It answers the phone. Service Fusion stays your system of record.