A channel address is the DevStride email address that support requests arrive at. You create one, then set your real support inbox (for example support@yourcompany.com) to forward to it. Customers keep writing to the address they know; DevStride turns what arrives into tickets and sends your replies back over email.
support@yourcompany.com, see Sending from your own domain.
| Field | What it does |
|---|---|
| Address (required) | The part before the @. DevStride appends its inbound domain, for example acme-support@in.devstride.com. Lowercase letters, numbers, dots, and hyphens. |
| Default location (required) | The workstream, folder, or item new tickets from this address are filed under. |
| Default work type (required) | The work type new tickets are created as. |
| Default request form | Applies a request form's field set to tickets from this address. Leave as No form to skip. |
| Notify on new ticket | A Default assignee, Default watchers, and Default watcher teams applied to every new ticket from this address. |
| Reply-From name | The sender name customers see on emails from this address, such as Acme Support Team. Use a team or inbox name rather than a person's name, which mail filters may flag. Blank means "{your organization} Support". |
| From address | The address customer emails are sent from. Leave it on Shared address (in.devstride.com) to send from the channel address itself, or pick a mailbox on one of your verified sending domains. Replies come back through in.devstride.com either way. |
support@in.devstride.com is almost certainly taken. Include something specific, like acme-support. DevStride checks availability as you type and suggests a free address.
Click the pencil on a row to change its defaults, Reply-From name or From address. The address itself is fixed once created, because mail is already routed to it. Changed defaults apply to future tickets only.
Every message to a channel address is checked, then handled one of three ways: it becomes a ticket, it joins an existing ticket, or it is held or turned away.
A new request creates a ticket, whoever sent it, including a member of your own organization:
People the customer copied on the email can join the ticket too (below).
Mail that is not a request is handled without opening a ticket:
Some senders get no automatic emails. Newsletters and mailing-list mail still become tickets, but DevStride skips the acknowledgement. The same goes for a no-reply address (noreply, donotreply, no-reply and similar): the ticket is created, but no acknowledgement, form confirmation, or status-change email is sent. A reply your team writes is still sent.
When a customer writes to the desk and copies other people from outside your organization, those people are copied on the ticket, so your replies reach them and their replies join the conversation. This works for a customer's new request and for their replies to it.
DevStride copies people from an email only when:
Even then, some addresses on the email are never copied:
Copying stops quietly once the ticket copies ten people. Someone new becomes a requester. The customer vouches only for their own address, so a known contact is copied exactly as they are and is never confirmed by the customer's email.
You don't manage threading. DevStride reads the email's threading headers and recognizes a reply to a ticket's email, so a customer who simply hits Reply lands on the right ticket. That also covers a conversation that never went through DevStride: when you and a customer reply-all with the channel address copied in, each reply joins the ticket the conversation started on.
When DevStride matches by these headers, only the ticket's requester, someone copied on it, or a member of your organization whose mail passes your domain's sender checks, can add to a ticket. Anyone else who replies this way gets a ticket of their own, unless their message also carries the ticket's reply address or subject tag. How email replies find their ticket lists every check in order.
When you send a Reply to customer from a ticket, it is emailed to the requester, with everyone copied on the ticket on Cc, and threaded so their next reply comes back to the same ticket. Quoted "On such-and-such date you wrote…" trails are stripped, so each comment shows only the new text.
Your own team's mail reaches the channel address too. Every such email opens or joins a ticket; what DevStride works out is who the request belongs to and what the customer should see.
A fresh email from a member of your organization creates a ticket like any other. The colleague is its requester, receives the acknowledgement, and the ticket queues in the Inbox. If it copies a client, it can open the ticket for that client instead (next section).
Write a new email to the channel address with a client on To or Cc, and DevStride opens the ticket for the client rather than for you:
The client is the first outside person on To, or, when nobody outside is on To, the first on Cc. So address the person the ticket is for and copy the rest.
DevStride does this only when all of these hold:
Otherwise the ticket is created as before, with you as its requester, and the client is not emailed. The same feature is in the Inbox as New ticket.
When you answer a customer from your own mailbox with the channel address in Cc, your email is added to the customer's ticket:
When a colleague who may open tickets for clients forwards a customer's message to the channel address, DevStride credits the ticket to the customer:
Forward a customer's reply into an existing ticket and the same split applies: the customer's words are published as a comment from them, and the covering note stays internal. Adding a reply to the customer's own ticket opens nothing new, so it needs no extra permission (see staff forwards). If that same email is already on the ticket and the ticket is still open, it is not published a second time: see the next section.
Two colleagues often forward the same customer email, or a colleague forwards something the customer also sent to the desk directly. The customer still gets one ticket and one acknowledgement. The later forward joins the ticket already open:
DevStride treats two emails as the same when they come from the same customer with the same subject and the same opening text. The forward joins only a ticket opened in the last 14 days that is not solved, closed or archived, and only if that forward is credited to the customer (below). Otherwise it follows the usual rules, which can mean a new ticket. An email with no text, such as an image on its own, never matches, and tickets opened before 9 November 2026 can't be matched.
Putting a stranger on your requester list and emailing them is worse than crediting nobody, so DevStride credits a forward to the original sender only when all of these hold:
If any check fails, the ticket is still created, but the forwarding colleague is the requester and the forwarded text is kept internal. Glance at the Requester pane before replying and change the requester if needed.
A shared address like support@yourcompany.com is often a Google Group, which rewrites the sender to "Dana Whitfield via Support" <support@yourcompany.com>. When a colleague forwards such a message in, DevStride credits the real person, using the list's own record of the original sender in the headers, or otherwise the one outside address in the forwarded text spelled from their name (for example dana.whitfield@…). Two or more candidates are ambiguous and none is used; the forwarder becomes the requester instead. The group's own address is never made the requester, so acknowledgements never go to a whole list.
Your support inbox, such as support@yourcompany.com, often writes to the desk as well as forwarding to it. List it so the desk treats it as your team and not as a customer. With nothing listed, nothing changes.
Open Settings → Email → Inbound addresses, go to Your team's own mailboxes, enter the full address and click Add. You need Manage Service Desk Settings. A listing counts for every channel address in your workspace, and training sandboxes don't copy the list.
You can list up to 20 mailboxes, one full address each; whole domains aren't accepted. The list refuses a channel address, a no-reply address, an address that can't receive email, a member's email, and anything already listed. A channel address's custom From address already counts as your own, so it doesn't need listing.
| The email | What DevStride does |
|---|---|
| A reply on an existing ticket | It joins the ticket like a colleague's reply, including a reply-all with the desk on copy. It's public when the customer is on the email, and the customer isn't sent it again. Otherwise it's internal, and anything unclear stays internal. |
| A forward carrying a customer's original | It opens a ticket in the customer's name. A repeat of a forward that already opened a ticket joins that ticket. |
| Anything else | It waits in Held for review as From your own mailbox, no customer found. No ticket opens and nobody is emailed. |
These rules apply only when the email positively passed DMARC and came straight from the mailbox. An email that fails that check, or that was delivered through a mailing list such as a Google Group, is treated as ordinary customer mail, so a forged address gains nothing.
Existing tickets stay as they are. If a mailbox was already recorded as the requester on older tickets, those tickets keep it, but its automatic email stops once it's listed. Removing a mailbox affects later mail and later events only.
Click the x on a row and confirm:
Remove ? Inbound email to this address will stop creating tickets. Existing tickets are unaffected.
The address's Default location is the baseline. Two things override it, in this order:
A ticket your team opens for a client, from New ticket or by email, follows the same rules, so it lands where that client's own email would.
If a company's location has since been archived or deleted, DevStride falls back to the channel address's default. A ticket is never dropped because a destination is missing.
Enabling Service Desk
Service Desk ships off. An administrator turns it on once for the organization. How to enable it, what it switches on, and what disabling does.
Requesters & Companies
Requesters are the customers who raise tickets; companies group them, carry per-customer defaults, and own the customer portal. How to manage both, merge duplicates, block senders, and handle erasure requests.