To confirm an appointment requested by SMS, block the slot, send the invitation to the customer's email, then restate the day and time by SMS, in that order. With a Muzau agent, the confirmation SMS only goes out once the appointment is booked. If your setting does not let it book on its own, your team confirms in Muzau: the slot is checked again to be free, and if it was taken in the meantime, nothing goes out.
The customer writes “Thursday 2:30 pm works for me.” You reply “Noted,” and the conversation ends there. Nothing has gone into their calendar, sometimes nothing into yours, and nobody checked that Thursday 2:30 pm was still free. Three days later, the SMS is far back in their phone, and the appointment depends on their memory.
Confirming an appointment requested by SMS takes three steps, in this order: check that the slot is free and block it, send the invitation the customer adds to their calendar, then write to tell them it is done. In the other order, you confirm a time that may no longer be free.
When the customer picks a slot offered by the SMS agent, it asks for their email address before booking the appointment. With Google Calendar or Outlook connected, the appointment goes into your calendar and the customer is invited to it; with no calendar, Muzau reserves the slot and sends a calendar invitation to the customer and to you. The detail of the exchange is on the page booking an appointment by SMS.
The sentence that confirms is not left to the AI: Muzau's code writes it, once the appointment is really booked. The SMS restates the slot and the address the invitation is going to, and this sentence is never cut to fit 160 characters. If the customer sends another SMS in the meantime, the reply that confirms still goes out.
If your setting does not let the agent book on its own, it replies to the customer: “I'm passing your appointment request to the team, who will get back to you to confirm it.” A card is waiting for you in “To do,” with a reply ready as one SMS and the first free slot already written in; you can pick another from those offered. On click, the slot is checked again to be free, the invitation goes to the email given by SMS, then the SMS goes from the agent's number. If the slot has just been taken, nothing goes out and the next one is offered; if the calendar cannot be read, nothing goes out either. Without an email given by SMS, the invitation cannot go out: you reply without the appointment.
The appointment follows its own setting, not the one for the agent's replies. If you keep approval on replies but let the agent book appointments, the appointment can be booked and its invitation sent by email while the SMS announcing it waits for your approval in “To approve.” The customer then has the invitation without the reply: approve those SMS first. To read and pick up these conversations, see answering your customers' SMS from a computer.
With or without a tool, a confirmation fits in one SMS and answers in advance the questions the customer will ask themselves the day before.
A template that fits in 160 characters: “Confirmed: Thursday [date] at 2:30 pm, at our office. The invitation is going to [email]. To change it, reply to this SMS.”
The mistakes to avoid: confirming before checking the calendar, which opens the door to two customers in the same slot; asking for the email before the customer has picked their slot; confirming by SMS without sending an invitation, which leaves the appointment out of the customer's calendar.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.