Hoppa till innehållet
Peak Atlas

Peak Automations / Follow-up template

Said is not done.
Commitments become tasks.

After a good conversation only one thing is often missing: that someone writes the commitments down. This template lets an AI step pull the commitments from an analysed conversation, turns them into tasks and prepares thanks and the follow-up meeting. You decide who follows up.

For which occasion?

Change the trigger. The preview next to it reacts instantly.

Edit all texts and details ↗Test the automation locally ↗
Local demo with sample data
Automation · previewPreview reacts instantly
Peak AutomationsLocal demo with sample data

When Peak Conversations has analysed the talk with Nordwind Studio GmbH (example)

pull out the commitments with an AI step, create one task per commitment and add a note with a summary to the contact.

Use sample data only.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Edit your draft in detailText, details & next action
01

Your sample automation

Make it yours.

Additional details

Name, e-mail and occasion are always part of the trigger as sample data in this demo.

JSON file for your local draft. Not an import into Peak Automations.

01 / Anatomy of the automation

Conversation, commitments,
next meeting.

The trigger is the end of a conversation or an event. The steps record what was agreed. The check says what waits for your confirmation.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview
When Peak Conversations has analysed the talk with Nordwind Studio GmbH (example)

pull out the commitments with an AI step, create one task per commitment and add a note with a summary to the contact.

Context → Details → Next action

The trigger says when the automation starts.

02 / The details
4visible details
01Namn02E-mail03Request04Company
03 / The next actionText preview

And then?
A clear next action.

Test run with a sample conversation. Every task names the place in the conversation it comes from.

Test the flow in the preview directly above.

02 / Three situations

Recorded, surveyed,
rescheduled.

Choose how your conversation ends: with a recording, a feedback form after the event or the wish for another meeting.

Another example replaces the current demo draft.

  • 01 / Conversation analysedSelected

    The conversation becomes a list.

    An analysed conversation is ready.

    Commitments from Peak Conversations

    „When Peak Conversations has analysed the talk with Nordwind Studio GmbH (example)“

    4 details · Company
  • 02 / After the eventSample draft

    Say thanks while it is fresh.

    Feedback form in Peak Forms.

    Feedback after the event

    „When the feedback form for [event] is submitted in Peak Forms“

    5 details · Company + Timing
  • 03 / Follow-up meetingSample draft

    The next meeting already has room.

    Peak Booking: outcome set.

    Prepare a follow-up meeting

    „When the outcome “Follow-up wanted” is set in Peak Booking“

    4 details · Timing

03 / Move on deliberately

What was discussed stays visible.

In Peak Automations you describe the flow in one sentence or pick the template. Peak checks connections and permissions, shows the flow as boxes and arrows, and you start a test run. Only then do you activate it. Every change becomes a new version, and the run history explains in plain language what happened.

Your context, your details and your next action — as one connected draft.

Please fill in the draft texts before you take them along.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Frequently asked questions

Does the AI step invent dates?

No. It only pulls out what is in the analysed conversation. Unclear due dates stay open.

Does Peak send e-mails without me?

No. Every e-mail to the outside goes through your connected mailbox and waits in the Inbox for your confirmation. Risky steps also need an owner or admin approval.

Which accounts do I need for it?

Only the ones that appear in the template. A person connects them in Settings → Integrations, and the connections belong to the workspace. Peak connects nothing by itself.

More in Peak Automations