Overview
A ticket is a single request that needs your team's attention. Tickets typically come in by email from a customer, from a public form on your site, or from another teammate who creates one manually. Every ticket has a subject, a requester, a stage, a priority, optional assignees, optional followers, and a thread of replies and internal comments.
Scrambl is built so the same record powers the customer-facing email conversation and your team's internal collaboration. Replies sent from the ticket go out as email to the requester and thread correctly in Gmail or Outlook. Internal comments are private to your team and never email the requester.
The lifecycle of a ticket
- Intake. The ticket is created — usually by an inbound email to one of your inboxes, sometimes by a form submission, sometimes manually.
- Triage. The ticket gets a stage (e.g. New), a priority, and is assigned to one or more teammates.
- Work. Assignees reply to the customer, leave internal comments, attach documents, and link related records (projects, deals, contacts, tasks).
- Resolution. The ticket moves through your configured stages until it reaches a terminal stage like Resolved or Closed.
Where to configure tickets
| Area | What lives there |
|---|---|
| Types & stages | Per-team ticket types, lifecycle stages, workflows, and stage colors. |
| Inboxes | The mailboxes that turn inbound email into tickets, plus per-inbox defaults. |
| Customer widget | The "Submit a ticket" widget you can embed on your site. |
| Suppressions | Recipients you should not email — bounces, complaints, unsubscribes. |
| Custom fields | Extra ticket-specific fields your team needs to capture. |
| Defaults | Module-wide defaults that apply when an inbox or form doesn't specify its own. |
Best practice: Set up at least one inbox and confirm a real test email creates a ticket before pointing customers at your support address.