Peak Helpdesk · Planned
A customer portal is planned.Today everything runs by email.
A portal where customers see their requests and their status themselves is not built in Peak Helpdesk yet. Today your customer gets every reply by email from your mailbox, with the ticket number in the subject. If they reply, their email lands on the right ticket again. This concept shows what a portal could look like later.
Put the goal into words. Add perspectives and timing right below.
Concept with sample data · none of this is available today.
Concept / two customer views
What the customer could see.
- Overview
- Planned: all their own requests with numbers.
- ステータス
- Planned: open, waiting on you, solved.
- Today
- Replies by email with [#123] in the subject.
Your portal in the concept
What should your customer see?
Set who would use the portal, what appears first and what the customer can do there. The preview stores nothing.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three answers. One portal concept.
Draft · not yet put together
- 顧客
- Still open
- ステータス
- Still open
- Action
- Still open
Two typical customer views
What should your customer see themselves?
Pick the customer view. The concept shows what a portal could show later and what exists instead today.
Many requests over the year
The buyer wants to know which of her requests is still open.
- The action
- Planned: she opens the portal and sees her requests. Today she asks by email, and your team sees all tickets of this person at a glance.
- The intent
- An honest status, today through your team.
Concept: the overview
- [#101]
- Solved (sample data)
- [#114]
- Waiting on your reply (sample data)
- [#120]
- In progress (sample data)
The concept shows the idea. Today your customer gets every reply by email with a ticket number.
To the next stepIs this for you?
A clear job. Clear limits.
A customer who
has more than one request open.
This is where the example helps.
- Your customers often have several requests at once.
- You want to give every ticket a clean status today.
- Replies by email with a ticket number are enough for you to start.
No portal today
What this preview doesn't do.
- A customer portal is planned and not available today.
- Customers cannot sign in and view their tickets today.
- This preview creates no ticket and sends nothing.
What you can do today
Give every ticket a clean status.
In Peak Helpdesk every ticket has a number, status, assignee and promise. Replies go out by email with the ticket number in the subject; the customer's replies land on the ticket again.
Start with Peak HelpdeskPeak Helpdesk / Your next step
A clean status comes before the portal.
Try the concept on your most important customer. Keep the status in Peak Helpdesk today.
View the concept
For customers with more than one request.
Replies by email with [#123] in the subject.
Frequently asked questions
Is the customer portal available?
No, the customer portal is planned. This page shows a concept with sample data.
How do customers see the status of a request today?
Through your email replies. The ticket number sits in the subject, so every exchange stays in the same case.
Do customers need an account?
Not for email or Live Chat. Whether the portal will need a sign-in is still open.