Перейти к содержанию

Peak Automations / Review collection

The project went well.Only nobody asked.

The best time for a review is right after a good result, and that's exactly when the team has moved on. With Peak Automations a won deal or a completed final task starts a run: an AI step drafts a short, personal request, and the e-mail waits for your confirmation before Peak sends it from your connected Gmail.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
See the review flow

Try it on a local sample project.

Satisfied is good. Asked is better.

Close / draft / confirmation

01When02Then03Only after confirmation
Working example / review

How the request comes about.

When
A project's final task is completed
Then
Draft a personal request with AI
Only after confirmation
Send from the connected Gmail
Editorial structure sketch · not the product interface

Your review request

From three answers to a prepared request.

Fill in the example with a made-up project and see how moment, confirmation and request fit together. Nothing is sent.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Automations / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three questions. A request at the right time.

Draft · not yet put together

The trigger
Still open
The confirmation
Still open
The request
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

From result to review

A good result. A good question.

The order makes sure the request is prepared in time and never sent unseen.

  1. 01Case

    The right moment triggers.

    When

    A project's final task is completed

    “Deal won” or “task completed” with a condition on the final task's title starts the automation.

    Event → condition
  2. 02Action

    The draft waits for you.

    Then

    Draft a personal request with AI

    “Draft text with AI” writes to your instruction. Because the e-mail goes outside, the run pauses until someone confirms.

    Working tool → draft, confirmation
  3. 03Result

    The request is on its way.

    Only after confirmation

    Send from the connected Gmail

    After confirmation Peak sends and records a note on the contact. In the local example you get a review note.

    Sample artifact → review note

The next proof is the product

Test the request with an e-mail to yourself.

Describe the automation in one sentence, connect Gmail in settings and start the test run. The test shows the draft and where the run waits for your confirmation.

Start Peak Automations

Peak Automations / Your next step

The best review is the one someone asked for.

Try the example with the project type after which your customers are happiest.

See the review flow
Local working example

Ask while it's fresh.

Send from the connected Gmail

Frequently asked questions

Does Peak send review requests automatically?

Peak prepares the e-mail. Because it goes outside, it waits for confirmation before Peak sends it from your Gmail.

Does Peak publish reviews?

No. Peak writes nothing to review sites. You manage replies and permissions yourselves, for example in Peak Proof.

When is the right moment?

A good trigger is “deal won” or a project's completed final task, narrowed with a condition.