Peak Automations / Support triage
The inbox is full.What in it is urgent?
When an e-mail arrives in the connected Gmail mailbox, an AI step classifies it into your categories through the Peak AI Gateway. A condition decides the route: a task for the person in charge, a note in the Inbox or a Slack message to the right channel. In the test run you see how Peak would classify your sample e-mail.
Put the goal into words. Add perspectives and timing right below.
Try it with a made-up request.
Sample e-mail / fictional data
How a request finds its route.
- Intake
- New Gmail e-mail: “invoice charged twice”.
- Classification
- AI step: category billing, urgent.
- Route
- Task for accounting and a Slack message in #support.
Your triage in three answers
Which e-mail goes where?
Fill in the example with made-up categories. You see which details Peak needs for the automation. Nothing is read, saved or connected.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A clear route per request.
Draft · not yet put together
- The intake
- Still open
- The routes
- Still open
- The urgency
- Still open
From e-mail to the person in charge
Classify. Route. Trace.
The order turns a full inbox into a list with clear owners.
- 01Classify
The AI step reads the e-mail.
IntakeNew Gmail e-mail: “invoice charged twice”.
It picks only from the categories you set. What it can't place with confidence stays visibly open.
E-mail → category - 02Route
A condition picks the route.
ClassificationAI step: category billing, urgent.
Per category a task, an Inbox note or a Slack message is created through your own connection.
Condition → task or channel - 03Trace
Every run is in the history.
RouteTask for accounting and a Slack message in #support.
You see which e-mail took which route and why. Peak reports missing permissions or connections before you switch on.
Sample artifact → run log
The next proof is the product
Classify the next support e-mail.
In Peak Automations you describe the triage in one sentence, and Peak builds the trigger, AI step and condition. After the test run with a sample e-mail you switch the version on.
Start with Peak AutomationsPeak Automations / Your next step
The urgent first.
Try the example with the request that last sat around too long.
See the triage example
Every request has a route.
Task for accounting and a Slack message in #support.
Frequently asked questions
Which mailboxes work?
Gmail today, through your workspace's connection. Other mailboxes are not connected.
Does Peak answer customers?
No. Peak classifies and routes; people answer.
What if the AI classifies wrongly?
The AI step picks only from your categories, and the history shows every decision. The test run shows the result in advance.