İçeriğe geç
Peak Atlas

Peak Automations / Support routing template

Every request has an address.
Even the one without a subject.

When every request lands in one mailbox, chance decides who answers. This template lets an AI step sort the request, creates a task for the responsible team and reports urgent ones at once. Whatever stays unclear goes to a person.

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 a new e-mail to [support@example.com] arrives in Gmail

sort it with an AI step as question, bug or billing and create a task for the matching team.

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

Intake, sorting,
ownership.

The trigger is the channel the request comes through. The steps sort it and pass it on. The check says what happens when the sorting is uncertain.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview
When a new e-mail to [support@example.com] arrives in Gmail

sort it with an AI step as question, bug or billing and create a task for the matching team.

Context → Details → Next action

The trigger says when the automation starts.

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

And then?
A clear next action.

Test run with three sample e-mails. Uncertain sortings go to [person] in the Inbox.

Test the flow in the preview directly above.

02 / Three channels

Mail, form,
your own system.

Choose where your requests come from. Sorting works the same, only the intake is different.

Another example replaces the current demo draft.

  • 01 / E-mailSelected

    The mailbox pre-sorts itself.

    New e-mail to the support address.

    Support through Gmail

    „When a new e-mail to [support@example.com] arrives in Gmail“

    4 details · Company
  • 02 / FormSample draft

    Form in, task out.

    Your website's support form.

    Support through Peak Forms

    „When the “Request help” form is submitted in Peak Forms“

    5 details · Company + Phone
  • 03 / UrgentSample draft

    Urgent does not wait.

    Your own system reports an error.

    Error report through a webhook

    „When an error report with level “critical” arrives through the webhook“

    4 details · Timing

03 / Move on deliberately

Less forwarding, faster answers.

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

How reliable is the sorting?

The AI step names a category with a confidence. Below your threshold, the request goes to a person instead of a team.

Can my own system send requests?

Yes, through the webhook trigger. It only accepts calls with this automation's key.

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