Use the appointment record as your source of truth, then give the customer a simple way to confirm or request a change.
1. Check the appointment record
Start with confirmed bookings whose customers agreed to receive messages. Include the date, local time, location, service, and booking reference in your working list. Check reschedules and cancellations immediately before sending. A contact list exported yesterday may already contain appointments that have moved.
2. Make the requested reply unambiguous
Identify your business before listing the appointment details. Ask for one short reply such as CONFIRM or CHANGE. Explain that a change request will be reviewed by the team rather than promising that any requested time is available. Keep promotional offers out of the confirmation.
3. Prepare a small manual batch
Create a contact group for the appointments being confirmed and insert supported custom fields through the variable selector. The brackets in the example are writing placeholders, not ready-to-use variables. Preview missing times and long locations. Tiringo does not synchronize your calendar; refresh the booking data yourself.
4. Close the loop with staff
Assign someone to review replies and update the appointment system. A delivered message does not confirm attendance. Track confirmations, change requests, and actual attendance separately. Start with one upcoming appointment group, then use the reply patterns to improve the next draft.
5. Handle the exception before the reminder
If a customer requests a change, pause any later reminder for the old appointment until staff have resolved it. Keep a short list of pending changes alongside the calendar. Otherwise a technically correct confirmation can contradict the conversation the customer just had with your team.
- Name the person responsible for changes.
- Record the revised appointment before replying.
- Remove cancelled bookings from the next export.
