Confirmations, reminders, and follow-ups each answer one question at one moment. Confirmation and a single six-hour reminder ship today; timed sequences are documented on the reminders page. The reminder strategy guide covers timing.
Before you start
- The moments that need information: confirm, prepare, remind, follow up.
- One purpose per message.
- A cancelled test booking to confirm reminders stop.
How to complete this task
- Map the moments that require information: confirmation, preparation, reminder, and follow-up.
- Assign one purpose and one action to each message.
- Schedule reminders according to the cost and lead time of the meeting.
- Test content, links, and suppression after cancellation.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
An invitee received no confirmation.
Confirm the booking reached its confirmed state, then check the address, the delivery record, and whether email credentials are configured on this deployment.
Reminders arrive at unhelpful times.
Match reminder timing to preparation cost. A 24-hour reminder suits a meeting that needs work beforehand; a one-hour reminder suits a short call.
A cancelled meeting still sent a reminder.
Suppression on cancellation must be tested explicitly. Cancel a test booking and confirm no later message is sent.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
