Service Desk

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.

When someone emails your support address or submits a form, DevStride records them as a requester: the person on the other side of the conversation. Requesters can be grouped into companies, the customer organizations they belong to. Both are managed from the Service Desk module.

Requesters

Open Service Desk → Requesters for everyone who has contacted your team. Search by name or email, filter by status, and read the Name, Email, Status, and Company columns. A requester in more than one company shows their main company followed by +N; hover to see the rest.

Click a row to open the requester. There you can edit their Email, Name, and Phone, manage their Companies, and use Block / Unblock, Merge into…, Resend confirmation (while a changed address is unconfirmed), and Anonymize…. Editing needs the Manage Requesters permission. A requester linked to a DevStride account shows their email read-only, with This address follows the person's DevStride account.

Where requesters come from

You rarely add a requester by hand:

  • Someone emails your support address. They become the requester on the new ticket, including a colleague on your own team.
  • A colleague forwards a customer's email in. When the forward is clear enough to trust and the colleague holds Manage Requesters and Create Items and Workstreams, the customer is credited rather than the colleague. See when someone on your team emails or forwards a message in.
  • Someone submits a request form, from a public link or the portal.
  • You convert an existing work item into a ticket and pick or create the requester. See Working a Ticket.

Requester statuses

StatusMeaning
ActiveNormal. Their email creates and continues tickets.
Pending verificationSubmitted a form while the spam brake was on and hasn't confirmed their address yet.
BlockedUse for abusive or spammy senders. Their mail is held on the Held for review tab and their portal access ends immediately.
AnonymizedErased on request. The record is a tombstone and can't be edited.
MergedFolded into another requester.

Pending verification is a new requester who hasn't yet proved their address, and the Status filter uses that name. It is different from the orange Unverified mark beside an email address, which means someone on your team changed the address and the customer hasn't confirmed it yet. The mark appears in the Requesters list, the requester dialog, and the ticket's Requester card.

Correcting a requester's email

When a customer's address is wrong or has changed, correct it rather than creating a second requester:

  • From the requester: change the Email field in the requester dialog and save.
  • From a ticket: open the ⋯ menu on the ticket's Requester card and choose Edit email….

The new address takes effect at once, and DevStride emails the customer at it to confirm. Until they do, the requester shows Unverified beside the address (hover for Changed by staff; waiting for the customer to confirm). They confirm by clicking the link in that email, replying from the new address, or signing in to the portal. The link lasts seven days; to send a fresh one, choose Resend confirmation in the requester dialog or the Requester card's ⋯ menu.

In headless mode the confirmation goes to your webhook endpoint instead of the customer's inbox, and your own tool asks the customer to confirm. Unverified and Resend confirmation work exactly the same.

If another requester already uses the new address, DevStride doesn't save the change. It offers Merge into the existing contact… instead: this requester's tickets and replies move across, and the address stays with the existing requester. See Merging duplicate requesters.

The email can't be changed when:

  • the requester is linked to a DevStride account; their address follows the account;
  • the new address belongs to an active member of your organization, or the requester is a member's own and the change would move it off their address;
  • the requester is blocked or anonymized.

Changing an email and resending the confirmation need Manage Requesters.

Requesters linked to a DevStride account

When a requester's email is the confirmed email of a DevStride user, the requester is linked to that person's account. The link grants nothing: no access to your workspace, no role, no seat, no membership. It keeps the requester in step with the person:

  • Their email follows the account. Your team can't edit it.
  • A changed account email carries over. When the person changes their DevStride email and confirms it, their linked requester in every organization's desk changes to the new address. If a desk already has a requester at the new address, the two are merged. The one exception is a desk in an organization where the new address belongs to an active member, usually the person themselves when they work there: that desk's requester keeps its old address, because a member's address can't be given to a requester.

People invited into an organization that uses enterprise sign-in are a special case. If they sign in through the organization's identity provider with an address outside that provider's verified domains, they sign in and receive notifications as normal. They aren't linked to requesters at that address until they confirm it with DevStride.

A requester in more than one company

A consultant or agency may raise tickets for several of your customers. A requester has one main company and any number of other companies. In the requester's Companies list the main one is marked Main:

  • Add company… links them to more companies. They can then sign in to each company's portal and see that company's tickets there.
  • The × next to a company removes it, after confirmation. Their access to that company's portal ends on their next page load.
  • Removing the main company while others remain asks which company becomes the new main one.

Which company a ticket belongs to

Every ticket records the company it was raised for and keeps it. Moving, merging, or erasing the requester later doesn't change the company of tickets they already raised.

  • By email: the company whose email domain they wrote from, otherwise their main company.
  • Through a portal form: the company whose portal the form was sent from.
  • A follow-up to a closed ticket keeps the original ticket's company.
  • If a requester had no company when they raised a ticket, the first company they're linked to fills it in. Changing a ticket's requester moves the ticket to the new requester's company.

Merging duplicate requesters

The same person sometimes writes from two addresses, creating two requesters. Open the one you want to keep and choose Merge into…, then pick the duplicate. Their tickets, the tickets they are copied on, history, knowledge-base comments, spec drafts and their versions, companies, and any company sign-in combine under the surviving requester. One case is refused: when either address belongs to someone in your own organization. See When an address belongs to your own team.

Erasing a requester (privacy requests)

When a customer invokes their right to be forgotten, open the requester and choose Anonymize…. This permanently scrubs their name, email, phone, and other personal details, and reaches everywhere they were kept: the stored originals of the emails they sent, attachment files that never reached a ticket, their details inside notifications and activity history, and their portal sign-in, including a company sign-in. Portal access is revoked on the spot, and they are taken off every ticket they were copied on. Their knowledge-base comments lose their words and show as Deleted user. The titles and text they wrote in unpublished spec drafts, every saved version included, are replaced with Removed, and the draft's title is cleared from your team's notifications; articles already published keep their content. It also reaches copies their words were written into: the values an automation's Apply Template action filled in from their tickets, and the event deliveries kept in your webhooks delivery log (redacting a single comment removes that comment's deliveries too).

The tickets your team worked are kept but de-identified, so history and reporting stay intact. If the same person emails again later, DevStride won't quietly re-identify them. Anonymizing is refused when the address belongs to someone in your own organization.

When an address belongs to your own team

If a requester's email is also the address of a member of your organization, DevStride refuses to merge or anonymize that requester and says so.

A team member's address appears across other people's tickets: as the sender of replies, on messages they forwarded in, in activity history. Scrubbing or folding it would rewrite conversations that have nothing to do with this request.

For the same reason, a requester can't be given an address that belongs to an active member, and a member's own requester can't be moved off their address.

Removing the person from your organization lifts the refusal but does not make the erasure safe. The check looks at current membership; the shared records are still there and would be rewritten permanently. For a genuine privacy request covering a current or former team member's address, contact support, which is what the on-screen message tells you to do.

Companies

Open Service Desk → Companies to manage customer organizations. The table shows Name, Email domains, Access, Portal slug, and Shared. Click New company or a row to open the company dialog.

Auto-matching by email domain

Give a company one or more Email domains (press Enter, Tab, or click away to commit each one) and new requesters whose email matches are linked to it automatically. Adding a domain also gathers existing requesters on that domain who have no company yet, and fills in the company on their tickets. Email alone never moves a requester who already has a main company, and never grants them another company's portal. Domains are stored lowercase.

Per-company defaults

A company can override the channel address for its requests:

  • Default location: file this company's tickets under their own workstream or item. See the override rules.
  • Notify on new ticket: a default assignee, watchers, and watcher teams for this company, taking precedence over the channel address defaults.

Shared tickets

Turn on Shared tickets — members of this company can see each other's requests when a customer wants their whole team to follow one another's tickets. In their portal, each person then gets a Company requests tab alongside My requests, and can read and reply on colleagues' requests. Only the person who raised a request can mark it solved. Off by default.

Portal settings

The company record also configures that company's Customer Support Portal:

SettingWhat it does
Access modeOpen, Domain-restricted, or Invite only: who may sign in.
Portal slugThe portal's web address segment. Lowercase letters, digits, and hyphens, 3–63 characters, no leading or trailing hyphen, and not a reserved word like admin or api.
Portal brandingA Logo (upload up to 2 MB, or paste a hosted URL), an optional Dark mode logo shown instead to visitors using the portal in dark mode, a Primary color, Header text, and a Portal notice (a switch and up to 500 characters of plain text shown as a banner across that company's portal while on; see Posting a notice on a company's portal).
Portal default localeThe language shown to visitors whose browser doesn't say otherwise. English is the only option today.
Portal sign-inEmail (the emailed link or code), or Company sign-in beside email through one of your tested identity-provider connections. Needs Manage Portal SSO. See Company sign-in for your portal.

Use Preview portal in the dialog to open the company's portal in a new tab exactly as customers see it.