Peak Helpdesk / Email support
Everyone reads the email.Nobody replies.
In a shared inbox everyone thinks someone else is on it. In Peak Helpdesk every forwarded email becomes a ticket with a number, an assignee and a response promise. The reply goes out from your connected Gmail or Outlook account, with the ticket number in the subject.
One answer changes the follow-up
Pick a sample rating.
Local draft · no product activationTest the sample rule · nothing is sent.
02 / The next question
Has anyone replied already, and by when does the customer need an answer?
From your mailbox with [#123]; if sending fails, the ticket says so.
Example · no real tickets · not the product interface
Check the rule yourself
Change the rating. See the difference.
Pick a rating. At 0 to 6 the clarifying question appears, at 7 to 10 it doesn't. Nothing is read or sent.
Local rule demo · Please use neutral sample details only.
Pick a rating to see the next step.
The answer sets the direction.
- Rating
- —
- Follow-up
- Waiting for a rating
No example picked yet.
The rule behind the example
First settle who replies. Then reply.
In the example a rating of 0 to 6 triggers a clarifying question. From 7 it's clear who answers the email and by when.
- 01Rate
Whose turn is it?
IntakeForwarding to your workspace's address.
You rate how sure you are who answers the sample email. The next question depends on it.
Input → rating from 0 to 10 - 02Clarify
At 0 to 6, assign first.
0–6Follow-up7–10FinishThe sample rule asks for status and deadline. In Peak Helpdesk the “unassigned” queue shows what nobody owns yet, and “needs reply” shows what comes first.
Condition → 0–6: clarifying question - 03Reply
From your own mailbox.
ReplyFrom your mailbox with [#123]; if sending fails, the ticket says so.
In the trial run, rating and question stand together. It is a local preview, not an email to a real customer.
Sample artifact → inbox note
From the example to a real inbox
Forward your support address.
In Peak Helpdesk you get an address for your workspace. Forward your support address to it, connect your Gmail or Outlook account in Peak Chat and answer the first email as a ticket.
Start with Peak HelpdeskPeak Helpdesk / Your next step
No support email is left lying.
Test both paths in the example. Then forward your real support address.
Test the sample rule
A shared inbox nobody forgets.
From your mailbox with [#123]; if sending fails, the ticket says so.
Frequently asked questions
How do emails get into Peak Helpdesk?
By forwarding to an address only your workspace has. Pulling directly from Gmail is planned.
Which address do replies go out from?
From the Gmail or Outlook account you connected in Peak Chat, with signature and ticket number in the subject.
What if a reply could not be sent?
The ticket tells you. Nothing disappears silently.