Support Ticket ID Generator

Support ticket numbers: anatomy, helpdesk standards and Brazilian SAC law

A support protocol number — also called ticket ID, case number or incident reference — is the unique identifier a customer-service system assigns to every interaction so it can be retrieved, audited and escalated. Typical shapes are SUPP-2024-12345, TICK-987654 or the long 14-20 digit strings used by Brazilian telecom carriers under Anatel rules. This generator returns mock IDs that look realistic enough for UX design, QA automation and agent training without polluting your production CRM.

Every ticket number serves three jobs: traceability (it points to a single record in the helpdesk database), communication shorthand (the customer quotes it back to skip re-explaining the issue), and legal compliance — in Brazil, telecom and health-insurance providers must emit a protocol for every customer contact.

Helpdesk platforms and their formats

There is no global standard. Each CRM picks its own scheme: Zendesk uses sequential integers (#12345), Freshdesk the same with a prefix, Intercom opaque ULIDs, Crisp short alphanumerics, Salesforce Service Cloud 8-digit numbers, HubSpot Service Hub long integers. Brazilian players such as Movidesk, Octadesk and Tomticket usually combine a year prefix with a sequence. Pick a format that humans can pronounce on the phone and a regex can validate.

• Year-sequence: 2024-000123 — readable, sortable, but leaks volume.
• Prefixed sequence: SUPP-12345 — clear context.
• Opaque ULID/UUID: hides volume, but hard to dictate by phone.
• Anatel-style: 14-20 digit string carriers must hand out for every call.

Brazilian SAC law: when a protocol is mandatory

Brazil’s Lei do SAC — Decreto 6.523/2008 — obliges telecom, banking, electricity, water, aviation, healthcare-plans and payTV companies to give the customer a protocol number on every contact. The newer SAC 4.0 (Decreto 11.034/2022) extends it to multichannel service: WhatsApp, e-mail, chat and phone must all generate a traceable ticket within five seconds of the request. ANS regulates health-insurance protocols, PROCON tracks consumer complaints under its own numbering, and Anatel audits telecom IDs every quarter.

Ticket lifecycle, SLAs and tiered escalation

A healthy workflow moves the ticket through Open → In Progress → Awaiting Customer → Resolved → Closed. Each transition starts or pauses an SLA timer — the Service Level Agreement that promises resolution within, say, 4 hours for priority P1, 24 h for P2, 5 days for P3. Triage usually follows Tier 1 (front-line script-driven), Tier 2 (specialist) and Tier 3 (engineering or product). AI chatbots powered by IBM Watson, Google Dialogflow or Microsoft Copilot increasingly handle Tier 0 deflection and only escalate to a human when intent confidence falls below threshold.

CSAT, NPS and what closes the loop

After a ticket closes, most CRMs trigger a CSAT (Customer Satisfaction) one-question survey and feed it into NPS (Net Promoter Score) dashboards. Integration with Salesforce, HubSpot or Microsoft Dynamics lets the protocol travel from helpdesk to sales pipeline, so a recurring complainer can be flagged before the next renewal.

FAQ

Can I use generated protocols in production? No. These are mock IDs for UI mockups, automated tests, training material and notification-flow previews — never feed them into a real CRM.

Is there a standard format across vendors? No. Zendesk, Freshdesk, Salesforce and Movidesk each pick their own scheme. Anatel mandates a minimum length for telecom (14+ digits) but not a shape.

Are companies obliged to give a protocol? In Brazil, yes for telecom, banking, electricity, water, paid TV, aviation and health-insurance under Decreto 6.523/2008 and the SAC 4.0 update of 2022.

How long must the company keep the record? Anatel requires telecom records for at least 6 months; ANS health-plan records for 5 years. Always check the sector regulator for the exact retention window.