Skip to content
TicketingSystem
Tickets that know when the bug is fixed

Support and engineering, finally on the same page.

One place for the help desk and the issue tracker. Customers write in by email or your help center, agents answer under SLAs with automations doing the busywork, and when a ticket turns out to be a bug, it stays linked to the issue, so support knows the moment the fix ships.

Start your free trialSee how it works

14 days of Business free · No card needed · Free plan for small teams

One loop, not three tools

From the first email to the release note

Most teams glue a help desk to an issue tracker with copy and paste. Here a ticket and the issue it uncovered stay linked, so nobody retypes a bug report or forgets to tell the customer.

  1. Step 1
    Customer writes in
    Email, help center or API
  2. Step 2
    SLA starts
    On your business hours
  3. Step 3
    Rules route it
    Right team, right priority
  4. Step 4
    Bug becomes an issue
    Linked, never retyped
  5. Step 5
    Fix ships
    Linked tickets get a note

SLAs

Promises you can actually keep

Set first-response and resolution targets for each priority, counted only in your business hours. Timers pause while you wait on the customer, warn before they run out, and escalate when they do.

  • Business hours and holidays in your time zone
  • First-response and resolution targets
  • Pauses while waiting on the customer
  • Warnings and breach escalation

Automations

Let rules do the routing

Build rules from triggers, conditions and actions, try them against past tickets before switching them on, and read a log of every run. Round robin spreads the load; time rules catch what goes quiet.

  • Triggers on create, update and time
  • Round-robin assignment by team
  • Dry runs against recent tickets
  • Signed, retried webhooks

Issue tracker

Bugs go to engineering without the copy and paste

Link a ticket to an issue in one click. Engineering plans it on a board with epics, a backlog and sprints; support sees its status on the ticket, and every linked ticket gets a note when it ships.

  • Projects, statuses and epics
  • Kanban board, backlog and sprints
  • Burndown from daily snapshots
  • “Shipped” notices to linked tickets

Help center

Answers before the ticket

Publish a searchable knowledge base under your workspace. Customers sign in to the portal with a one-time link, follow their requests, and get article suggestions while they type a new one.

  • Knowledge base with drafts and versions
  • Passwordless customer portal
  • Suggested articles on the request form
  • Search-engine friendly article pages

Reports and CSAT

Know how support is really doing

Customers rate a solved ticket from the email itself. The dashboard shows volume, reply and resolution times, SLA compliance, backlog age and CSAT, in your time zone, ready to export.

  • Surveys answered from the email
  • Medians, not misleading averages
  • SLA compliance and backlog age
  • Date ranges and CSV export

Security

Your customers trust you with their problems. We take that seriously.

Isolation the database enforces

Every tenant row carries its workspace, and Postgres row-level security filters every query. One workspace cannot read another's tickets, even through a bug in our code.

Two-factor sign-in

Authenticator apps with backup codes for everyone. Pro and Business workspaces can require it of every member.

Staff access is audited

If our staff ever view your workspace to help you, the view is read-only, ends after 30 minutes, and is written to your workspace's audit log as well as ours.

Your data leaves with you

Export a whole workspace or one customer's history, and erase a contact on request.

How we protect your data

For developers

An API for your tickets and issues

Tickets, messages, contacts, issues and published articles over a documented REST API, with workspace API keys on Pro and Business. Webhooks are signed and retried, so your systems hear about changes as they happen.

OpenAPI reference Signed webhooks
Read the API reference 
$ curl -X POST https://app.example/api/v1/tickets \    -H "Authorization: Bearer $API_KEY" \    -H "Content-Type: application/json" \    -d '{"subject": "Export drops a row",         "body": "Our monthly CSV stops one row short.",         "requester": {"email": "priya@example.com"}}' 201 Created  { "number": 1042, "status": "new", … }

Pricing

Simple per-seat pricing

Free for up to 3 agents. Pro is $15 and Business $39 per agent a month. Viewers never take a seat.

Compare plans

Answer faster. Ship the fix. Tell everyone who asked.

Every new workspace gets 14 days of Business, with no card needed. Keep the Free plan afterwards, or pick a paid plan when you are ready.

Start your free trialSee pricing