Where defaults come from

A new ticket inherits values in the following order, with the first match winning:

  1. Per-inbox defaults. Set on each inbox under Tickets → Settings → Inboxes. Use these when different addresses need different behavior (e.g. billing@ defaults to your finance team).
  2. Per-form defaults. Forms that create tickets can override priority and stage in their own settings.
  3. Module defaults. Set under Tickets → Settings → Defaults. Used as a fallback when nothing more specific is configured.

What each default does

DefaultEffect
AssigneesUsers automatically added to the ticket. They're notified and the ticket appears in their queue.
PrioritySets Low / Medium / High / Urgent. Drives sort order, filtering, and SLA reporting.
StageThe stage the ticket lands in. Skip if you want tickets to start in your org-wide default stage.
TagsLabels applied to every ticket from this inbox. Useful for routing, filtering, and reporting.
Description templatePre-filled text added to the ticket body — handy for forms that need extra context.

Best practice: Set per-inbox defaults rather than module defaults whenever possible. Per-inbox defaults make routing decisions at intake — before a teammate has to triage.