The office closed at five. At 6:40 the phone rings. What happens next tells you almost everything about how a business runs.
Here is what happens when a system answers it.
The conversation
The system picks up, says it is an automated assistant, and asks how it can help. The caller has a leaking tap under the kitchen sink and wants someone to come out. The system asks where in the home, which area they are in, and whether it is dripping or running. It asks for a name and a number to call back. It offers the next open morning window and the caller takes it.
It asks one more thing: may it send a text to confirm? The caller says yes.
Nothing in that conversation is improvised. The questions come from the page the owner approved. A price was not quoted, because that is on the never list.
The record
While the call is still going, the system is writing. A contact is created or found. The job is logged with the fault, the area and the window. The booking goes into the calendar the dispatcher already uses. The call is logged against the contact with a short note, not a transcript.
When the call ends, the text goes out: the window, the name of the business, a line to reply to if anything changes.
The hand-off
If the caller had said water was pouring through a ceiling, the conversation would have gone differently. The system would have flagged it as urgent, told the caller what to do about the stopcock, and alerted the person on duty with the address and the number. It would not have tried to book a morning window for a flood.
Monday morning
The dispatcher opens the calendar and the job is there, with the contact, the fault and the confirmation already sent. Nobody listened to a voicemail. Nobody called back to ask the questions again. The caller's weekend was not spent wondering whether anyone heard.
You can have this conversation yourself. There is a live line on the demo page; say what you would say to a real company and watch what the system writes down.