"Tuesday at ten": how a voice agent turns a phrase into a calendar event
Booking a caller in is harder than it looks: the slot may be taken, and "Tuesday at ten" has to become an exact instant in the company's time zone. Here is the second half of the voice receptionist.
Can a voice agent book a caller into the calendar itself?
It can, once two things are settled. "Tuesday at ten" has to become an exact instant in the company's time zone, not the caller's. And the slot has to be checked before the event is created: if it is taken, the agent offers two specific nearby times instead of apologising. A booking with a low-confidence email is created without an invitation and flagged for a person.
The previous article about the voice receptionist took apart the fragile half: capturing an email by ear. But collecting the details is not enough. The call has to end with something in the calendar, or someone still has to ring back.
The second half is no simpler than the first.
The time zone belongs to the company
“Tuesday at ten” is not a time. It is an intention that has to become an exact instant.
Whose Tuesday, and whose ten? The caller may be in another state. The agent runs in a data centre and has no local time at all. The only right answer is the company’s time zone: the practice works to its own hours and appointments are made in them.
So the zone is a parameter of the agent rather than something inferred. The agent turns the phrase into an exact dated time carrying that zone and passes that on, not the words. Everything downstream works with an unambiguous instant.
The same goes for working hours. Weekdays nine to five is a setting, not something the model knows. The agent does not offer Saturday because it was told which windows exist.
Check, then create
The second decision is simple to state and large in its consequences: look first, create second.
The scenario searches the calendar between the named time and half an hour after it. Nothing there, and a half-hour event is created with the name, phone and email in the body, and the same booking goes as a row into a sheet that serves as a simple CRM.
If it is taken, the agent does not say “unfortunately that time is unavailable” and start over. It names two specific nearby options: an hour later and two hours later. The difference between “that slot is taken” and “I can do eleven or twelve” is the difference between a call that ended in nothing and a call that ended in a booking.
Uncertainty travels all the way
The third decision ties the two halves together.
If the email could not be captured and the agent marked it as low confidence, that mark is not lost on the way. When the event is created, no invitation is sent to the attendee: a message to the wrong address is worse than none. The row in the sheet is flagged, and a receptionist can see which bookings need confirming by hand.
That is a general rule for any system where some of the data may be wrong. Carry the uncertainty flag to the last step. A system that knows the data is doubtful and acts as though it were certain is worse than one that never knew.
What to take from this
Three things that do not depend on the tools.
Store time as an exact instant with a zone, and take the zone from the business rather than from whoever is speaking. Check availability before creating, and answer a taken slot with options rather than an apology. And carry the low-confidence flag to the end, so the last step can act on it.
You can talk to an agent like this in your browser: the voice receptionist page. If you want one for your own bookings, get in touch.