An occasion
When someone misses a booked meeting, remind me the next day to check in with them.
For example a lost deal, a booking with the outcome “no-show” or a submitted form.
Peak Automations · Follow-ups
Describe when to follow up. Peak creates a task for it, notifies the right person or prepares an email from the connected Gmail account. Emails reach outside and so wait for your confirmation. Peak does not chase anyone on its own.
Local example · sample data · nothing is sent
Why: A task reminds you without Peak writing to anyone itself. Whether and how you check in is your call.
02 / How follow-ups are built
A follow-up is an ordinary automation: an event, an optional wait, then a step.
When someone misses a booked meeting, remind me the next day to check in with them.
For example a lost deal, a booking with the outcome “no-show” or a submitted form.
Trigger: booking outcome in Peak Booking is “no-show”
Wait: one day
Step: task “offer a new slot” for you, linked to the booking
Create a task, notify someone or a Gmail email. An AI step can draft the text; you confirm it.
Your review is still open.
These marks start nothing.Proposal and activation stay separate
Peak writes to nobody on its own. There is no chain that emails contacts again and again without you.
The Gmail step sends from your workspace's account and waits for a confirmation in the Inbox first.
This page creates no task and sends no email. The examples are fixed.
The next step
Start Peak Automations and describe the occasion where things most often stall for you today.
Describe a follow-up flow in Peak AutomationsLocal example · sample data · nothing is sent
No. An email from the connected Gmail account always waits for your confirmation.
Between one minute and 30 days. For later dates the task gets a due date.
Yes, an AI step can write a draft through the Peak AI Gateway. It is only sent after your confirmation.