A ticket is an ordinary work item, so everything you already do with items (assign an owner, set a priority, move it across a board, add it to a cycle) works here. What's new is the conversation with the customer and the handful of ticket-only fields around it.
Open Service Desk → Inbox. It's the familiar items table locked to tickets by a Tickets only pill, with the saved views All open requests (default) and Unassigned ready on day one.

When a client phones you, or you spot their problem before they write in, open the ticket for them. Click New ticket at the right of the Inbox toolbar (or beside the search box while the toolbar is collapsed) and fill in:
Click Open ticket. The client is the ticket's requester, so replies, the portal and SLA clocks work as for any ticket, and its channel is API. A new client is added as a requester at once, with no confirm-your-address email, because you vouched for the address. You are added as a watcher. The client company's and the desk address's Notify on new ticket defaults apply as they do to emailed tickets: the default assignee is assigned, and the default watchers and watcher teams are added. If DevStride refuses the ticket (a blocked client, for example), nothing is created and the dialog keeps what you typed.
New ticket needs both Manage Requesters and Create Items and Workstreams; the button appears only when you hold both. Sending the message to the client also needs Send Public Replies.
You can also open a ticket for a client by writing to the desk with the client copied. Your own tools can do the same through the API's POST /service-desk/staff-tickets (see the API reference under Service Desk); its participantEmails copies up to ten other outside people. Give it the desk address and leave out the location and work type, and the ticket is routed the same way as from the dialog; GET /service-desk/staff-tickets/channel-addresses lists the desk addresses you can open one from.
Every ticket has one conversation, and every entry is one of two kinds. Choose in the composer before you send:
| Reply to customer | Internal note | |
|---|---|---|
| Who sees it | The requester and everyone copied on the ticket. It's emailed to them and shown in their portal. | Only your team, inside DevStride. |
| Use it for | Answers, questions, status updates | Working notes, hand-offs, discussion |
| How it looks | A normal message in the thread | Flagged with an Internal marker |
On a ticket the composer starts as Reply to customer; switch to Internal note when you mean to keep it private. A reply inside a thread inherits the audience of the comment it answers, so replies under an internal note are always internal, and a draft reopens with the audience you chose. Members without the Send Public Replies permission only ever compose internal notes.

Every Reply to customer carries an orange External badge in the Discussion. Once the reply has been emailed, the badge gains a check mark; hover it to see when it went out. A reply that could not be delivered shows a warning marker instead (see When an email to the customer doesn't arrive).
A customer often wants a colleague or their manager kept in the loop. Copy them on the ticket and they follow the whole conversation, as if they were on the email thread with you.
The Copied list sits under the ticket's Requester card. To add someone, type in Add person by name or email: pick an existing requester, or type a full email address and choose Copy address. Click the x beside a name to stop copying them. A ticket copies at most ten people. Nobody is emailed when you add or remove someone; they get the ticket's next public reply.
Once someone is copied:
Some people can't be copied: members of your organization (they follow a ticket as watchers instead), the desk's own addresses, no-reply addresses, the ticket's requester, and blocked or erased requesters. A copied person the desk can't email is tagged in the list: Blocked, Undeliverable (their address bounced or reported spam) or Unconfirmed (they haven't proved their address yet). They stay on the list but get nothing until that changes.
People are also copied for you:
A follow-up ticket opened by a reply to a closed ticket keeps the people copied on the original.
Adding and removing people needs Manage Requesters and edit access to the ticket. Everyone who can open the ticket sees the list. Your own tools can use GET, POST and DELETE on /service-desk/items/{itemNumber}/participants (see the API reference under Service Desk).
Your work types keep their own statuses. Customers see a simplified customer status in the portal, in emails, and in automations:
| Customer status | What it means to the customer | Which of your statuses show it |
|---|---|---|
| Open | Received, not yet picked up | Statuses of type New, unless mapped otherwise |
| In progress | Being worked | Statuses of type Custom, unless mapped otherwise or marked as terminal |
| Awaiting your reply | The ball is in the customer's court | Only a status explicitly mapped to Awaiting your reply. A staff reply on its own no longer changes what the customer sees |
| Solved | Done, pending the customer's confirmation | Statuses of type Done, and custom terminal statuses with outcome Completed, unless mapped otherwise |
| Closed | Final; replies open a new ticket | A status explicitly mapped to Closed. A custom terminal status with outcome Not completed (such as Cancelled) also reads Closed, but a reply still lands on the ticket unless the status is explicitly mapped |
Each work-type status can also be marked to pause SLA resolution clocks while the ticket sits in it (for example a Waiting on customer status). Both the customer-status mapping and the SLA pause flag are stored on the work type's status settings; there is no screen for them yet, so set them through the API or ask support. The seeded auto-close automation and the portal's Mark solved button both need a status that reads as Solved.
Not every customer problem arrives as an email. When a story or bug turns out to have a customer waiting on it, Convert to ticket makes it a Service Desk ticket without retyping or losing history. Converting asks for:
From then on SLA clocks run, the customer's replies thread onto it, and it appears in their portal. Convert from the item's right-click menu (under Edit), the Activate Service Desk button in the item side panel, or bulk edit to convert several at once. Converting needs Manage Requesters.
Every email to a channel address opens a ticket, whoever sent it. Three cases look different in the Inbox:
If a second colleague forwards the same customer email while the first ticket is still open, no second ticket appears. Look for an internal note starting Forwarded by on the ticket already open, with that colleague added as a watcher. The customer isn't emailed again. Email Channels has the details.
When the colleague lacks those permissions, or DevStride can't safely tell who the customer is, the forwarding colleague is credited and the forwarded text stays internal. Check the Requester pane before replying and change the requester if needed. Email Channels sets out the exact rules.
When a ticket belongs to the wrong person, open the ⋯ menu on the ticket's Requester card and choose Change requester…, then pick an existing requester or enter a new one's name and email. One of your team's own mailboxes can't be the new requester.
The same menu offers Block / Unblock, Edit email… (to correct the requester's address; not shown for a requester linked to a DevStride account), Resend confirmation (while a changed address is unconfirmed), Merge… (requesters), and Anonymize…. All need Manage Requesters.
When the same issue comes in twice, select exactly two tickets and choose Merge tickets from the right-click menu, then pick which one survives. The other's conversation and history move onto the survivor, a customer reply that threads by email headers to either ticket lands on the survivor, the survivor gets an internal note naming the merged ticket, the people copied on the merged ticket are copied on the survivor too (up to the limit of ten), and the merged ticket is archived and linked as related. A reply that carries the merged ticket's own reply address or subject tag is treated as a reply to an archived ticket and opens a linked follow-up instead. Both tickets must share the same requester and company. Needs Manage Requesters.
A ticket's Description tab has a three-way control: Internal, Customer, and Unified.
Attachments from the original email are listed beneath the Customer description; attachments from later replies sit beneath the comment that carried them. Everything is also in the ticket's Assets tab.
To hand a customer a file without attaching it to a reply, open the ticket's Assets tab and turn on Share with customer on that file. It then shows in the Files section of the customer's portal request, by name with a download link, and its tile carries a Shared badge. Turn the switch off and it disappears from the portal again. Files start unshared, so nothing reaches the portal until someone switches it on, unless your organization chose to share new files by default.
Files the customer attached to the request form when they submitted it are always listed on their portal request; they need no switch.
If your team shares most ticket files with the customer, switch on Share new ticket files with the customer in Settings → Service Desk (needs Manage Service Desk Settings). It is off until you turn it on, and turning it on asks you to confirm.
While it is on, a file or link a member adds to a ticket starts shared: it shows in the customer's Files section straight away, its tile carries the Shared badge, and the Activity tab records it as added and shared with the customer. Turn Share with customer off on any single file to keep it private.
When a ticket arrives by email, DevStride reads the subject and body and picks the closest match from the work type's priorities, so "URGENT: production is down" arrives elevated. It only runs while the ticket still has its default priority; a priority set by a form or a person is never overwritten. If the AI service is unavailable, a conservative urgency-word check runs instead. Treat it as a head start and change it as you would any priority.
Two fields record what the customer considers urgent, separately from your internal priority:
Both are sortable columns and filters (see Finding & Filtering Tickets), and SLA policies can match on Importance.
By default a work type's custom fields are agents-only. To let customers see or fill a field in the portal, open Settings → Data Model for the work type's field collection and click Customer visibility. Each field is Agents only, Customers can view, or Customers can edit. Field types the portal can't render stay agents-only. Needs Manage Work Types.
Each public reply that went out by email shows, under it in the Discussion, what happened to that email after it left DevStride:
Replies sent before this was added show neither line.
If a desk email bounces or the customer marks it as spam, the team member who wrote the reply and the ticket's assignee are alerted in the app and by email. The alert names the ticket and says what happened:
A public reply that didn't arrive carries a warning marker in the Discussion; hover it to read Failed to deliver to the customer. If DevStride's email provider refused to send the email at all, the marker reads Not sent — our email provider refused it, with the provider's reason when it gave one.
When a customer's request turns into planned work — a story, an epic or a bigger piece of the roadmap — you can record that the ticket is where the work came from. Open the roadmap item's Relationships dialog (the relationship icon on its card), click Manage in its Originating tickets section, pick the ticket and click Save. The ticket then lists that item in its own Answered by section.
Customer updates when the work ships. If your team's release process drafts customer updates for linked tickets (DevStride's own delivery agents do this at every production release), each linked ticket gets one plain-language update per release, written as an internal note for the plan's owner to approve. The owner replies Approved in that note's thread to send exactly that wording to the customer, once, after the work is live; Hold stops it. Under Settings → Service Desk, Send roadmap release updates automatically skips the approval. It is off by default.
| Action | Permission |
|---|---|
| Open tickets, add internal notes | Access Service Desk (plus ordinary item and comment permissions) |
| Send Reply to customer, choose a Unified description | Send Public Replies |
| New ticket for a client (also needs Create Items and Workstreams), convert to ticket, change requester, merge tickets, block / merge / anonymize requesters, edit a requester's email | Manage Requesters (a message to the client also needs Send Public Replies) |
| Copy people on a ticket, or stop copying them | Manage Requesters and edit rights on the item |
| Set Importance and Customer Rank | Edit rights on the item |
See Permissions.
Customer Support Portal
A branded, passwordless self-service portal per company. How customers sign in, the Home page and menu they find there, what they can see and do, and how you set the address, access mode, and branding on the company record.
Request Forms
Collect structured support requests through a form, from a public link or inside the customer portal. How to make a form create tickets, list it in the portal, and what customers see and must fill in.