DocumentationWorkspaceTicketing System
v1.0
In-depth

Ticketing System

Track structured cases, enforce SLAs, and resolve issues with full audit trails. Built for teams who outgrow generic inboxes.

Quick start
Setup time
5–10 minutes
Prerequisites
  • Inbox conversations to convert, or an email channel to ingest tickets directly
  • SLA targets defined in Settings → SLA (or accept defaults)
  • Optional: priority and severity values that match your ops playbook
Outcomes
  • First ticket created with priority and SLA timer running
  • Internal notes and activity log producing a complete audit trail
  • Team aware of SLA breaches via in-app + email notifications

Step-by-step walkthrough

Numbered, real-world instructions you can follow today.

1
Open Tickets

Click Tickets in the sidebar. You'll land on the All Tickets list with filters for status, priority, assignee, and SLA state.

Live screenshot: Open Tickets
Live screenshot: Open Tickets
2
Create a ticket

Click + New ticket — fill in title, description, priority, severity, and assignee. Or, from Live Inbox, click ⋮ → Convert to ticket to lift the entire thread into a ticket.

3
Track SLA

Each ticket displays a live SLA countdown — green (healthy), amber (at risk), red (breached). The SLA pauses automatically when the ticket is set to On hold (waiting on customer).

4
Collaborate via notes

Use the Notes tab for internal-only discussion. Mention teammates with @, attach files, and reference other tickets with #.

5
Resolve and close

Move the ticket to Resolved when work is done; the customer is asked to confirm. Once confirmed (or after the auto-close window), the ticket is Closed.

Watch tutorial
Watch: SLA-driven ticketing in SyntrixOne
Video coming soon — bookmark this page or subscribe for the release.

Tips & best practices

Field-tested advice from teams shipping SyntrixOne in production.

  • Convert long inbox threads into tickets the moment they exceed 5 back-and-forths — SLA discipline kicks in immediately.
  • Use Tags ("billing", "bug", "feature-request") for trend analysis in Analytics → Tickets.
  • Pin a ticket to your dashboard if it's your top focus today — it appears in the top KPI strip.

Common issues & troubleshooting

What goes wrong, and exactly how to fix it.

Frequently asked questions

7 answers to the questions teams ask most.

Ready when you are

Create your first Ticket

Estimated setup time: 5–10 minutes.

Create your first Ticket

Related articles

Keep going — explore the next pieces of SyntrixOne.