Service Desk

Overview

Service Desk turns customer email and form submissions into DevStride work items your team can triage, answer, and track. What it is, the five ideas behind it, and where to start.

Service Desk lets your team receive support requests from customers, reply to them, and track every conversation as ordinary DevStride work. An email arrives at your support address, it becomes a ticket, your team triages it, replies, and closes it out, with the whole back-and-forth captured on the item.

You'll find it as the Service Desk module (the headset icon) in the left sidebar once it's turned on.

Why it exists

Support work and product work usually live in two tools: a help desk for customer email and a tracker for what the team builds. Tickets get copied back and forth, context is lost, and customers are answered from a system that has no idea what the team is working on.

In DevStride a support ticket is a work item. A customer request sits next to the engineering work it depends on, rolls up into the same boards and reports, and is assigned, prioritized, and scheduled like anything else.

The five ideas

ConceptWhat it means
A ticket is a work itemA ticket is a normal item that has a requester. Boards, owners, priorities, custom fields, due dates all apply.
RequesterThe person who raised the request. Anyone who writes to your support address becomes the requester of the ticket it opens, including someone on your own team, unless a team member opens the ticket for a client. A requester is a contact record, not a membership: no role, no workspace sign-in, and never a paid seat.
CompanyAn optional grouping of requesters from the same customer organization, matched by email domain. Companies carry per-customer defaults and own the customer portal.
ChannelHow a request arrived: Email, Portal (a form submitted in the customer portal), or API (a staff-created or converted item). Tickets can be filtered, grouped, and SLA-matched by channel.
Reply to customer vs. Internal noteEvery ticket carries one conversation with two kinds of entry. A Reply to customer is emailed to the requester; an Internal note is visible only to your team. The line is enforced everywhere.

What Service Desk does

  • Receives email as tickets, filed where you choose, with replies threaded onto the same ticket. A customer email a colleague forwards in is credited to the customer, not the colleague, when that colleague may open tickets for clients.
  • Lets your team open a ticket for a client, from the Inbox's New ticket button or by emailing the desk with the client copied, and tell the client a request was opened for them.
  • Collects requests through forms, from a public link or inside the portal.
  • Keeps the conversation and your notes together: public replies go out by email; internal notes never leave DevStride.
  • Manages requesters and companies, including blocking, merging duplicates, and erasing a requester on request.
  • Holds suspicious mail on a Held for review tab and records every email that didn't become a ticket on Rejected mail.
  • Gives customers a branded self-service portal with passwordless sign-in, where a Home page shows what is waiting on them and they track requests, reply, submit new ones, work on specs, read your Help center, and see lists you share with them.
  • Tracks response-time promises with SLAs that count only your business hours.
  • Acts on elapsed time with time-based automations: auto-close solved tickets, escalate unanswered ones, nudge quiet customers.
  • Reports on volume, response and resolution times, SLA attainment, agent activity, and first-contact resolution.

In this section

Related: the Knowledge Base feeds the portal's Help center and suggests articles while a customer types a request.