İçeriğe geç

Peak Automations · Follow-ups

No follow-up slips through again.
You stay the sender.

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

CONTEXT BEFORE ACTION

Your sentence.
A flow you check.

01 / Your request

83/600 · fixed examples, no model call

Peak Automations / Your flowEXAMPLE
02 / The visible proposal3 example steps

No-show

Why: A task reminds you without Peak writing to anyone itself. Whether and how you check in is your call.

  1. 01Trigger: booking outcome in Peak Booking is “no-show”
  2. 02Wait: one day
  3. 03Step: task “offer a new slot” for you, linked to the booking
Check all steps & reasons

02 / How follow-ups are built

Trigger. Wait. Step.

A follow-up is an ordinary automation: an event, an optional wait, then a step.

01 / The starting point

An occasion

When someone misses a booked meeting, remind me the next day to check in with them.
Your sentenceNo-show

For example a lost deal, a booking with the outcome “no-show” or a submitted form.

02 / Visible proposal

A wait

Your request / Proposed flowLOCAL EXAMPLE
  1. 01
    Example step

    Trigger: booking outcome in Peak Booking is “no-show”

  2. 02
    Example step

    Wait: one day

  3. 03
    Example step

    Step: task “offer a new slot” for you, linked to the booking

03 / Your decision

A step

Create a task, notify someone or a Gmail email. An AI step can draft the text; you confirm it.

Local review

Your review is still open.

These marks start nothing.

Proposal and activation stay separate

Where follow-ups stop.

01 / Here in the browser

No autonomous chasing

Peak writes to nobody on its own. There is no chain that emails contacts again and again without you.

Your requestFixed ruleExample steps
The sculpture illustrates the flow. It is not a product interface.
02 / In the real product

Email only with confirmation

The Gmail step sends from your workspace's account and waits for a confirmation in the Inbox first.

Activation
Only after a passed test
Rights
Roles in the workspace
03 / The limit

Nothing sent from here

This page creates no task and sends no email. The examples are fixed.

ProposalActivation

The next step

Your next follow-up is already on your list.

Start Peak Automations and describe the occasion where things most often stall for you today.

Describe a follow-up flow in Peak Automations
Peak Automations · Follow-upsA task appears.

Local example · sample data · nothing is sent

Frequently asked questions

Does Peak write to contacts on its own?

No. An email from the connected Gmail account always waits for your confirmation.

How long can a wait be?

Between one minute and 30 days. For later dates the task gets a due date.

Can a draft be written automatically?

Yes, an AI step can write a draft through the Peak AI Gateway. It is only sent after your confirmation.