Peak Automations / For customer support
The inbox is full.The urgent e-mail is somewhere inside.
A support inbox mixes questions, complaints and billing topics. With Peak Automations an automation reacts to new e-mails in your connected Gmail: an AI step sorts each e-mail into exactly one of your categories, a second one summarises it, and Peak creates a task for the person responsible. Replies are still written by a human.
Put the goal into words. Add perspectives and timing right below.
Two typical requests. The AI only picks from your categories.
One inbox / two typical requests
From a new e-mail to a task.
- When
- An e-mail arrives in the connected Gmail
- Then
- Classify and summarise with AI
- Afterwards
- Create a task for the person responsible
Your support automation
Which categories does your inbox need?
Create a local note with sample details. Please don't enter real customer data; nothing is connected, read or saved.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three thoughts. A sorted inbox.
Draft · not yet put together
- The intake
- Still open
- The categories
- Still open
- The step
- Still open
Two requests in everyday support
Which request comes in most often?
Choose the request. Classification, next step and sample note follow the case.
Unhappy customer
An e-mail with a complaint arrives in the support inbox.
- The action
- The AI step classifies it as a complaint; only then does Peak create a task with a summary for the team lead.
- The intent
- Complaints land straight away with the person who can decide.
The complaint note
- Trigger
- New Gmail e-mail
- Condition
- Category is “complaint”
- Step
- Task with AI summary
The example makes the flow clear. The product proof shows where it starts in Peak Automations.
To the product proofDoes this fit you?
Sort and assign. Replying stays with you.
One e-mail,
one clear place.
This is where Peak Automations helps.
- You receive requests via Gmail or a form and want to stop sorting them by hand.
- You want complaints to reach the right person sooner.
- You want to read back why an e-mail landed where it did.
Test before go-live
What it doesn't do today.
- Peak doesn't reply to customers on its own. An outgoing e-mail always waits for your confirmation.
- New tickets in Peak Helpdesk are not a trigger in Peak Automations today.
- Outlook as a trigger and branching within a single automation are not available yet.
The next proof is the product
Let the first e-mail be classified as a test.
Connect Gmail in settings, describe the automation in one sentence and start the test run. It shows which category the AI would have chosen, without creating a task.
Start Peak AutomationsPeak Automations / Your next step
Sort first. Then reply well.
Pick the request that sits longest in your inbox. That becomes your first support automation.
See the support examples
Every request gets a place.
Create a task for the person responsible
Frequently asked questions
Does Peak reply to customers automatically?
No. An outgoing e-mail is a risky step and always waits for confirmation. The automation sorts and assigns.
Can the AI invent its own categories?
No. The “Classify with AI” step picks exactly one of the categories you set and shows how confident it is.
Which inboxes work?
As a trigger today, Gmail through the workspace connection. Forms from Peak Forms and Typeform work too. Outlook as a trigger is not available yet.