Tickets
Support inboxes, ticket stages, and customer email.
How-to guides 5
- Configure ticket stagesStages are the lifecycle steps a ticket moves through, from New to Closed. You can rename, reorder, recolor, and add stages.
- Embed the customer ticket widgetThe floating "Submit a ticket" widget lets visitors on your site create tickets without email. Configure it once and embed a single script tag.
- Forward email from Google Workspace (Gmail)Two ways to route mail from your Google Workspace support address into a Scrambl inbox — the easy 3-field method first, then the advanced Routing rule if you need it.
- Forward email from Microsoft 365 (Exchange)Use an Exchange mail-flow rule to redirect mail addressed to your support address into a Scrambl inbox.
- Set up a ticket inboxAn inbox is a unique Scrambl email address that turns inbound mail into tickets. Most orgs run one inbox per support address (support@, sales@, billing@).
Concepts 5
- Catch-all inboxesA catch-all inbox accepts mail to any address on a domain. Use it as a safety net or to consolidate variants of an address.
- How tickets work in ScramblTickets capture customer or internal support requests, route them through stages, and let your team reply over email or comment internally.
- Route multiple support addresses to different inboxesWhen your team uses several support addresses, create one forwarding rule per address. Each rule maps a single source address to a single Scrambl inbox.
- Suppressions: bounces, complaints, unsubscribesSuppressions are recipients Scrambl will not email — because their address bounced, they marked a previous reply as spam, or they unsubscribed.
- Ticket defaults: assignees, priority, stage, tagsDefaults apply when a ticket is created from an inbox, form, or widget. Setting them up well removes manual triage from every ticket.