helpdash1
Open a front door for requests.
Customers sign in to the portal with their own authentication, submit a request and see the tickets that belong to them. Portal access and operator access use separate guards.
Explore self-serviceFor Customer portal
A place your customers can check for themselves.
Not every update needs an email. Give customers somewhere to look, and give your team fewer “any news?” messages to answer.
Start with HelpdashTTom at BrightsideAn example conversation
Where can I check what is happening with my request?
Self-serviceEverything in its place.
- Team
- Customer portal
- Owner
- Assigned
- Context
- Conversation + customer
- Next step
A day in your workspace
A customer submits, follows and finds the answer without waiting.
2
Let progress speak for itself.
A customer can follow the status of their request and reply in the same place, so the conversation stays attached to the ticket your team is already working on.
Explore the shared inbox3
Answer before the question arrives.
Publish help articles to a searchable public help centre. The article your team writes once can resolve the request before it is submitted.
Explore the knowledge baseYour identity, on your customer’s screen.
A portal that looks like you.
Configure brand identity and portal host settings so the portal presents the brand your customer recognises.
Requests that arrive ready to work.
Use ticket forms with custom fields and conditional sections so a submitted request carries the detail your team needs.
One conversation, several ways in.
Portal submissions join email and website chat in the same shared inbox, with the same ownership, notes and service deadlines.
Let’s make it work
for your team.
Start exploring your own workspace, or walk through your support setup with us.