Settingsbeginner

Common Conversation ID Formats

Four ready-to-copy conversation ID setups: simple sequential, date-stamped, random for privacy, and per-team prefixes — with exact field values.

3 min read

Common Conversation ID Formats

Pick one of these four proven setups, enter the field values below under Settings → Conversation ID, and click Save Settings — the Live Preview chip at the top of the page confirms the resulting shape before you save. Each recipe lists exact values for every relevant field.

Simple sequential — SUP-0001, SUP-0002

The default choice for most teams: predictable, easy to read aloud, looks like a “real” ticket number.

  • Numbering Strategy — Sequential
  • Start Number — 1
  • Include Date — off
  • Default Prefix — SUP
  • Prefix Separator — -

Date-stamped — TKT-251225-0001

Adds the creation date to every ID. The sequential counter does not reset each day — it keeps incrementing across days, the date just changes alongside.

  • Numbering Strategy — Sequential
  • Include Date — on
  • Date Format — YYMMDD
  • Date Separator — -
  • Default Prefix — TKT
  • Prefix Separator — -

Random for privacy — A7B3X9K2

Random IDs prevent anyone from reverse-engineering your conversation volume from the numbers.

  • Numbering Strategy — Random
  • Random ID Length — 8
  • Include Date — off
  • Default Prefix — (blank)

Per-team breakdown — SUP-0001 for support, SALES-0001 for sales

Gives each customer service team its own prefix while everything else uses the default.

  • Numbering Strategy — Sequential
  • Default Prefix — CONV
  • Prefix Override Mode — Team-Specific
  • Team override 1 — support team → SUP
  • Team override 2 — sales team → SALES

Add each override in the Team-Specific Prefixes card — pick the team, type the prefix, click +. Teams without an override fall back to CONV. Full walkthrough in Override the conversation ID prefix per channel or team.

See also

Tags

Recipe
Back to Settings