Help desk for saas companies
Support for software teams, with engineers in the loop
In a SaaS company the person who can answer is often not the person who replies. Desk lets engineers read tickets and leave notes without an agent seat, keeps bug reports On hold with the clock paused, and sends every ticket event to your own tools.
What gets in the way
- Bug reports bounce between support and engineering in Slack threads
- The person who can check the logs needs a paid seat to see the ticket
- Outages bring in 40 copies of the same question in an hour
- Customers ask the same how-to questions after every release
How saas companies set up Desk
- 1
A form inside your app
Embed the support form with hidden fields for the user id and plan, so every ticket arrives with the account it's about.
- 2
Engineers as collaborators
Mention an engineer in a note. They read the ticket, check the logs and note the answer. Only the support person replies.
- 3
On hold while it's fixed
A canned response tells the customer the bug is logged, sets the ticket On hold and tags it bug. The resolution clock pauses until it's fixed.
- 4
Outage tickets merged
Merge the duplicates into one ticket per customer and answer the rest with an outage update canned response.
- 5
Events to your stack
Webhooks send ticket.created and ticket.closed to your own code, and the API opens tickets from your monitoring.
Example
A login bug, start to finish
Raj writes from inside the app that his login code never arrives. The ticket arrives with his user id and plan from the form's hidden fields.
Theo mentions Priya, an engineer, in a note. She finds his mail server is rejecting the codes and notes it. Theo sends the "Bug logged, we'll update you" canned response, which sets the ticket On hold and tags it bug. Two days later the fix ships, Theo tells Raj it's fixed, closes the ticket, and Raj rates it Great.
Everything here is part of Office Desk, on every plan. See how other kinds of business use Desk.
Features they use
- Private notes and collaboratorsTalk about a ticket on the ticket, and bring in anyone in the company to read and leave notes without paying for an agent seat.
- Ticket forms you can embedBuild a support form from your ticket fields, put it on your site, and every submission becomes a ticket with the right group and tags.
- API and webhooksRead and change tickets from your own code, and get a signed webhook whenever something happens.
- Canned responsesAnswer the questions you get every week in two clicks, with the customer's name filled in and the ticket updated in the same step.
- Merge tickets and customersFold duplicate tickets into one conversation, and combine customers who wrote in from two addresses.
Templates to start from
- Bug acknowledged replyThanks the customer for the report, confirms what you reproduced, and says when they'll hear back, without inventing a ship date.
- Outage update emailFor the hour when 40 people write in about the same outage. Plain about what's broken, clear about what still works, and specific about the next update.
Other businesses
- For agenciesGive each client its own support address, keep every client's tickets together by company, and let clients follow their own requests in a branded portal.
- For small office itStaff report laptop, access and software problems by email or a form. Priorities with deadlines, categories for every request, and a view per technician.
- For property managersTenants report maintenance problems through a form with their unit filled in. Leaks jump the queue, staff add notes on site, tenants check status online.
Try Office Desk with your whole team
7-day trial with every feature. Cancel from the billing page whenever you like.