No-show handling in Default at a glance
Send meeting reminders by email
Reminders are messages in the sequence an event uses. Guests receive email; hosts can receive email or Slack. Set their timing before or after the meeting starts. Default does not send meeting messages by SMS. Each booking keeps a saved copy of its sequence, and that copy decides which reminders send. Later edits apply to new bookings. A disabled or removed reminder has no alternate sender, and an event set to no messages sends no reminders for new bookings. An event that was never on a sequence keeps the reminders its own event settings configure. If saving a booking’s copy fails, Default retries within a bounded recovery window. Failed sends also have a limited number of retries; recovery is not a guarantee that a missed reminder will be sent. Setup imports existing reminder choices without turning disabled messages on. A reminder sent to a host shows a View button for the meeting and a Join button. It has no guest reschedule or cancel links, which only guest reminders carry.1
Add a reminder message to a sequence
Open Settings and select Sequences under Workspace Settings. Open a sequence and
select Add message, which opens a menu of message types, and pick Reminder. Set
Send to, Channel (Email or Slack), and the timing row, Before or After
the meeting, with an amount and a unit (minutes, hours, or days), then select Save. Select Review changes, then Publish: linked
events use the published version for new bookings, so a message that is only saved as a draft
never sends. Sequences is admin-only. See Sequences.
2
Link the sequence to the event
Open the event and pick the sequence in its Messages view, under Sequence. Select
Save at the top of the event to apply the choice.
When a meeting is booked, Default skips any before-meeting reminder whose send time has already
passed — for example a 24-hour reminder on a same-day booking. After-meeting reminders still send,
even if their send time passed before the booking was processed. When a meeting is rescheduled,
Default moves remaining reminders to the new time and skips any whose send time has already passed.
When a meeting is canceled or marked as a no-show, Default cancels its pending reminders.
If a later reschedule makes a skipped reminder’s send time upcoming again, Default schedules it
for that new send time.
Give guests a way to reschedule instead of skipping
A guest who can’t make the meeting is more likely to move it than to skip it when the link is in front of them:- Insert the Reschedule link and Cancel link variables into reminder and confirmation messages. See Variables.
- Keep Include calendar links in footer on for the event’s calendar invite, so guests can reschedule or cancel from the invite itself. It’s on by default for new events. See Calendar invite.
Mark a meeting as a no-show
Reps mark no-shows by hand. Default has no automatic no-show detection: it doesn’t read calendar responses or video attendance to decide whether a guest showed up.
Only meetings with the status Booked or Rescheduled can be marked. The meeting’s hosts,
the teammate who booked it, admins, and people with manager access to the meeting can mark it.
See Meetings and
the Chrome extension.
What marking a no-show does in Default
When a meeting is marked as a no-show, Default:- Removes the meeting’s calendar event and video call, the same way a cancellation does.
- Sets the meeting’s status to No show. The meetings dashboard shows the badge, and the Status filter can find it.
- Sends enabled no-show messages from the booking’s saved sequence: email to guests, and email or Slack to hosts. A host who muted the alert is skipped. If the saved sequence has no enabled no-show message for a recipient, nothing sends in its place.
- Cancels the meeting’s pending reminders, including reminders set to send after the meeting.
- Gives routing credit back to each host who got the meeting from a queue, when the queue’s policy allows it. See Routing credit for no-shows.
- Fires the Meeting Status workflow trigger with the status No show.
Routing credit for no-shows
A no-show shouldn’t use up a rep’s turn in a round robin. When a host got the meeting from a queue, Default credits them back if the queue’s policy has both of these on the Credit Behavior tab:- Enable crediting
- No-show meetings
Follow up on no-shows with a workflow
Use the Meeting Status trigger to act on every no-show the same way:1
Start on no-shows
Create a workflow with the Meeting Status trigger. Under Meeting statuses, select
No show. Optionally narrow it with Event types, Specific events, or Sources.
2
Tell the host
Add a Send Slack Message node and pick the Primary host from the data picker as a
recipient.
3
Start a follow-up sequence
Add a sequencing node, for example Add to Outreach Sequence, with the lead’s email from
the Lead fields under Meeting details. Pick a sequence written for missed meetings.
4
Log it in your CRM (optional)
Add Create Record with a Salesforce Task or a HubSpot engagement, such as Note, as
the Object to record the missed meeting on the lead’s record.