Service Desk

Working a Ticket

Triage from the Inbox, open a ticket for a client, reply to the customer by email, copy other people on the conversation, keep internal notes separate, fix the requester, merge duplicates, and understand what the customer sees as the ticket moves through your statuses.

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.

Triage from the Inbox

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.

  • Open a ticket to read the customer's description and reply.
  • Click New ticket to open a ticket for a client yourself.
  • Select several (click, ⌘/Ctrl-click, Shift-click) and use bulk edit to reassign, re-prioritize, set Customer Importance, or move them together.
  • Save your own views; see Finding & Filtering Tickets for the ticket columns and filters.
  • Collapsed the toolbar for more room? A Toolbar button and a small Search box stay above the list, as on Manage Items and My Work. Search tickets from there, or click Toolbar to bring the full toolbar back; the button shows how many filters, sorts and options are active.
  • When every ticket has reached an ending status, the empty Inbox celebrates: All caught up! Every ticket is wrapped up with a burst of confetti and a light-hearted line that changes each time. If open tickets exist but your filters hide them, it shows the plain No items found for the applied filters instead.

Opening a ticket for a client

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:

  • Client. Choose Existing client and search by name or email, or New client and enter their full name and email. Blocked requesters are not offered.
  • Title. The client sees it.
  • Desk address. The ticket is filed exactly where the client's own email to that address would be: through the address's request form when it has one, otherwise under the client company's default location, otherwise under the address's default location (see where a ticket actually lands). Replies to the client come from it. If the desk has no address yet, create one first; the dialog tells you whether the desk has no address, the list could not be loaded, or you don't have access to it.
  • Copy (optional). Other people who get the emails on this ticket, and can reply. Search your requesters by name or email, or type a full address and choose Copy address; up to ten people. They are copied on the ticket, so the opening email below goes to them too.
  • Note for staff (optional). It becomes the ticket's Internal description, which only your team sees.
  • Email client that this ticket is open (on by default when you hold Send Public Replies; without it the box is off and disabled, and you can still open the ticket). The message below it is sent as the ticket's first Reply to customer, in your organization's name from the desk address, and the client can answer it by email. It starts as a short note saying a support request was opened for them and that they can reply to add details; edit it as you like. Clear the box to tell the client nothing yet.

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.

Replying: customer replies vs. internal notes

Every ticket has one conversation, and every entry is one of two kinds. Choose in the composer before you send:

Reply to customerInternal note
Who sees itThe requester and everyone copied on the ticket. It's emailed to them and shown in their portal.Only your team, inside DevStride.
Use it forAnswers, questions, status updatesWorking notes, hand-offs, discussion
How it looksA normal message in the threadFlagged 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.

Seeing that a reply was emailed

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).

How the conversation flows

  1. A request arrives (email, form, or portal) and a ticket appears in the Inbox with the message as the Customer description.
  2. DevStride suggests a priority from the text (below), applies the channel's and company's default assignee and watchers, and starts any matching SLA clocks.
  3. You triage: confirm priority, set an owner, add internal notes, do the work.
  4. You send a Reply to customer. They receive it by email and simply reply. (How email replies find their ticket explains how DevStride matches the reply.)
  5. Their reply lands on the same ticket as a customer comment, with any attachments beside it. If they reply to a colleague directly, that colleague can forward it in and it still lands as the customer's own comment.
  6. You move the ticket to a Solved status. If the customer doesn't come back, the seeded auto-close automation closes it after four days and tells them.

Copying other people on a ticket

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:

  • Your public replies reach them. Each Reply to customer is one email, to the requester with everyone copied on Cc. Acknowledgements, confirmation requests and status-change emails still go to the requester only. An email that copies anyone carries no portal link, because the link is the requester's own.
  • Their replies join the conversation. A copied person's emailed reply lands on the ticket as a customer comment, like the requester's, and is passed on to everyone else in the conversation who wasn't on that email. The same goes for the requester's emailed replies. A message is never sent back to the person who wrote it.
  • They can follow it in the portal. A copied person who can sign in to your customer portal finds the ticket under My requests, reads its public conversation and replies there.

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).

Customer statuses

Your work types keep their own statuses. Customers see a simplified customer status in the portal, in emails, and in automations:

Customer statusWhat it means to the customerWhich of your statuses show it
OpenReceived, not yet picked upStatuses of type New, unless mapped otherwise
In progressBeing workedStatuses of type Custom, unless mapped otherwise or marked as terminal
Awaiting your replyThe ball is in the customer's courtOnly a status explicitly mapped to Awaiting your reply. A staff reply on its own no longer changes what the customer sees
SolvedDone, pending the customer's confirmationStatuses of type Done, and custom terminal statuses with outcome Completed, unless mapped otherwise
ClosedFinal; replies open a new ticketA 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.

Turning an existing item into a ticket

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:

  • The customer. Pick an existing requester or create one.
  • What the customer should see. Choose One unified description to share the item's existing description, or write a separate Customer-visible description so nothing internal leaks.

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.

Tickets from your own team, and forwarded mail

Every email to a channel address opens a ticket, whoever sent it. Three cases look different in the Inbox:

  • A colleague wrote in. They are the requester and received the acknowledgement. Work it as you would a customer's.
  • A colleague wrote in and copied one client. The client is the requester and was told a request was opened for them, the colleague is a watcher, and the colleague's email is the ticket's Internal description.
  • A colleague forwarded a customer's email. When the colleague holds Manage Requesters and Create Items and Workstreams, the customer is the requester, the title and Customer description are the customer's words, the colleague is a watcher, and their covering note is an internal note.

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.

Changing a ticket's requester

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.

  • Replies, the portal, and the ticket's company follow the new requester.
  • Only this ticket moves. To combine two records for the same person, merge the requesters instead.
  • Nobody is emailed, history stays, the change is logged in the activity feed, and SLA timers keep running.
  • If the previous requester writes to this ticket again, their email is added as an internal note rather than shared with the new customer.
  • If the new requester was copied on the ticket, they leave the Copied list. If the new requester belongs to a different company, everyone copied on the ticket is taken off it, because they came with the wrong customer; copy the right people again. A reply-all from someone taken off this way is kept as an internal note and never copies them back on.

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.

Merging duplicate tickets

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.

The two descriptions: Internal and Customer

A ticket's Description tab has a three-way control: Internal, Customer, and Unified.

  • Customer is what the requester wrote and what they see. The original email body lands here.
  • Internal is your team's working description, private to the organization.
  • Unified keeps one description shown to both. Choosing it needs Send Public Replies or Manage Requesters; anyone who can edit the item can switch back to the split.

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.

Sharing a file with the customer

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.

  • The share follows the file. A newer upload under the same name, or a restored earlier version, stays shared (or unshared) as the file was, so a shared file's new contents reach the customer straight away.
  • The switch shows only on a file's current version, not on earlier versions or description files, and only to members with Send Public Replies.
  • The ticket's Activity tab records who shared a file and who took it back.

Files the customer attached to the request form when they submitted it are always listed on their portal request; they need no switch.

Sharing new files by default

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.

  • It applies to files a member adds by hand: on the Assets tab, by drag and drop, or through the API or an agent connection.
  • It follows the same permission as the switch on the file. A file added by a member without Send Public Replies starts unshared, as before.
  • A newer upload under the same name keeps the file's own choice, so a file you switched off stays off.
  • Files the system adds start unshared: images in a description, attachments from email, and files on a copied ticket.
  • Files already on tickets do not change when you turn the setting on or off.

Automatic priority from incoming email

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.

Customer Importance and Customer Rank

Two fields record what the customer considers urgent, separately from your internal priority:

  • Importance: Critical, Important, or Nice to have (Clear removes it). Set it from the Importance column cell on any items table, or on several tickets at once via bulk edit's Customer Importance action.
  • Customer Rank: a manual ordering of a customer's tickets. A ranked ticket shows a Ranked marker; sort a table by Customer Rank to see and adjust the order.

Both are sortable columns and filters (see Finding & Filtering Tickets), and SLA policies can match on Importance.

Customer-visible custom fields

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.

When an email to the customer doesn't arrive

Each public reply that went out by email shows, under it in the Discussion, what happened to that email after it left DevStride:

  • Accepted by the customer's mail server, with the time. Hover it to read the mail server's own answer. From here, whether the email reaches the inbox or a junk folder is up to the customer's mail system.
  • Delivery delayed — the customer's mail server has not accepted it yet; still retrying, with the time. The email is still being retried; nothing needs doing yet.

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:

  • Rejected by the customer's mail server: usually a wrong or dead address. Check the requester's email.
  • A temporary problem, such as a full mailbox. Later emails may get through.
  • Marked as spam: their provider may now junk the desk's emails. Reach them another way if it matters.
  • Someone on the ticket marked it as spam: several people were on the email and their mail provider doesn't say which of them it was, so nobody's email is stopped and the reply still shows as delivered. If someone copied on the ticket shouldn't be on it, remove them.

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.

Linking a ticket to the roadmap work it asked for

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.

  • This link is separate from Related: the same ticket and item can be both, and it never counts as a dependency.
  • One end must be a Service Desk ticket and the other must be ordinary work; you cannot link two tickets this way, or two roadmap items.
  • The two sections show only while Service Desk is enabled.

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.

Who can do what

ActionPermission
Open tickets, add internal notesAccess Service Desk (plus ordinary item and comment permissions)
Send Reply to customer, choose a Unified descriptionSend 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 emailManage Requesters (a message to the client also needs Send Public Replies)
Copy people on a ticket, or stop copying themManage Requesters and edit rights on the item
Set Importance and Customer RankEdit rights on the item

See Permissions.