Skip to the page

DocsSupport desk

DocsSupport desk

SLAs

Set first-response and resolution targets by priority, counted in business hours, with warnings and a report.

Business plan and aboveFor owners, admins and support agents

An SLA (service level agreement) says how quickly your team replies to a ticket and how quickly it’s resolved. You set targets for each priority, Projik times every ticket against them in business hours, and it warns the right person before a deadline is missed.

Owners and admins set the targets. Owners, admins and support agents see the deadlines and the report. Customers never see any of it.

The two clocks#

Every ticket has two clocks.

ClockStartsStopsPauses
First responseWhen the ticket is raisedAt your first public replyNever
ResolutionWhen the ticket is raisedWhen the ticket is Resolved or ClosedWhile it’s Waiting on customer or On hold
  • Internal notes don’t count as a first response. Sharing a note with the customer does.
  • If a resolved ticket reopens, its resolution clock carries on from where it stopped.
  • A ticket closed with no public reply after its first-response deadline passed counts as missed.

Business hours#

Both clocks count only business time: the hours in the SLA, on your workspace’s working days, in its time zone, skipping its public holidays. With a Monday-to-Friday week and hours of 09:00 to 17:00, a ticket raised at 6pm on Friday starts counting at 9am on Monday.

The hours belong to the SLA. The working week and time zone are set in Settings › General, and holidays in Settings › Public holidays. See Workspace settings. Hours must end after they start on the same day, so an overnight shift can’t be entered.

Set the workspace SLA#

  1. Open Settings › Support SLAs.
  2. Set Business hours from and to. They start at 09:00 to 17:00.
  3. For each priority, type the First response and Resolution targets in hours of business time. 0.5 is 30 minutes, and 16 is two 8-hour days. Leave a box empty for no target.
  4. Choose Turn on SLAs.

The form starts with suggested targets you can keep or change:

PriorityFirst responseResolution
Urgent1 hour8 hours
High4 hours16 hours
Normal8 hours40 hours
Low16 hours80 hours

A ticket takes the targets for its priority. The customer chooses the priority when they raise a ticket, and your team can change it on the ticket, which changes the targets too.

After that, change anything and choose Save changes. Saving re-times the open tickets the SLA covers and tells you how many. Resolved and closed tickets keep the targets they were measured against, so past results don’t move. Turn off removes the workspace SLA: open tickets on it then have nothing due.

A project’s own SLA#

A project can have its own targets and hours, which replace the workspace’s entirely for that project’s tickets.

  1. Open the project’s Settings › Support portal and scroll to Service levels.
  2. Choose Set this project’s own. The form starts from the workspace’s values.
  3. Change the hours and targets, then choose Use these targets.

To go back, choose Use the workspace SLA. The project’s open tickets are re-timed against the workspace’s targets.

When a ticket is moved to another project, it takes that project’s targets if it’s still open.

Where deadlines show#

  • The inbox has an SLA column with the next deadline: “Reply in 40m”, “Resolve in 3h”, “2h late”, “Paused”, and for finished tickets “Met” or “Missed”. Anything due within two hours is highlighted.
  • Each ticket has an SLA card with both targets and where each stands, such as when it’s due, “Met · replied in 45m” or “Paused · 3h left”.

A ticket with no target for its priority shows a dash in the inbox and has no SLA card.

Warnings#

Projik warns about a deadline twice: shortly before it, and once it’s missed.

  • Before: a quarter of the target ahead, but never less than 5 minutes or more than 2 hours. A 1-hour reply target warns 15 minutes ahead. A 40-hour resolution target warns 2 hours ahead.
  • Missed: as soon as the deadline passes.

The warning goes to the ticket’s assignee. If the ticket is unassigned, or assigned to an AI worker, it goes to the project’s triage owner instead. A missed deadline also goes to the triage owner when that’s someone else. The triage owner hears about other people’s tickets only if they’re an owner, admin or support agent.

Warnings arrive on My Work, in the bell and by email, and as a browser notification if you’ve turned those on. An email isn’t sent if the warning is no longer true, for example because the ticket was answered in the meantime. Each person can turn them off under SLA warnings in Your profile › Notifications. See Notifications.

The SLA report#

Open Support › SLA report. Choose Last 7 days, Last 30 days or Last 90 days, and under Projects tick as many projects as you like, or All projects. The report covers tickets that arrived in that period:

  • First response met and Resolution met: the share of measured tickets that met the target, with the median time taken.
  • Needs attention now: every open ticket that’s overdue or due within two hours, soonest first, whenever it arrived.
  • By priority, By project and By assignee.
  • Missed in this period: the tickets that missed a target, and which one.

Export CSV downloads the same numbers.

On a plan without SLAs#

SLAs are part of the Business plan. If your workspace moves to a plan without them, for example when a trial ends:

  • Your SLAs are kept, but can’t be changed. You can still turn one off.
  • Open tickets’ resolution clocks are frozen, and no warnings are sent.
  • When you return to Business, open tickets are re-timed and the time without SLAs isn’t counted on the resolution clock. First-response deadlines are still counted from when each ticket was raised.

See Plans and billing.

    Type to search every page. ↑ ↓ to move, Enter to open.