SLAs set response targets for your threads and show which ones are about to miss them. They need the Scale plan or above, and live under Settings > Office hours & SLAs.
How it works
With SLAs on, every new thread is matched against your policies top to bottom, and the first match applies. Each policy sets up to three targets:
First response: how soon your team should send the first reply to a new thread.
Next response: how soon your team should reply after each later customer message. It resets with every new customer message.
Time to close: how soon the thread should be resolved.
You can type a duration into a target, such as 4 business days or 4bd. Productlane counts from the moment you pick the option, skips Saturdays and Sundays, and saves the result as a fixed length of time. Picked on a Thursday, 4 business days spans a weekend, so the target reads 6 days. That is how the count works, not a bug. Public holidays are not skipped, and the saved length stays the same afterward.
The clock pauses after a reply
The response clock runs only while your team owes a reply. When a teammate replies, the SLA badge disappears and no breach is recorded for that window. The clock starts again when the customer writes back.
A thread your team has answered shows no breach badge, even when the original deadline has passed.
The SLA breached inbox view lists only threads still waiting on your team.
When the customer follows up after an on-time reply, a new response window starts. The deadline your team already met stays met.
SLA statuses
Every thread with an active SLA shows a status badge:
On track: more than 60 minutes left.
At risk (yellow): 60 minutes or less left.
Breached (red): the deadline passed and your team has not replied.
Hover the badge for the exact deadline. SLA badges and deadlines are internal: they appear in your team's inbox and thread view, and customers do not see them.
The SLA badge and the clock next to a thread in the inbox list show the SLA deadline. Snoozing uses a separate clock in the thread header. A thread with an SLA clock is not snoozed, and it will not show up under Snoozed. See Snoozing.
Policies and conditions
A policy applies to all threads, or to threads that match its conditions. Conditions can match on:
Thread fields: priority, origin, and tag. Origin is Widget, Email, Slack, Portal, Live Chat, or API. The tag condition reads has or does not have, and you pick the tag from a list.
Company fields: name, size, revenue, tier, and status
Contact fields: email
Conditions support operators such as equals, not equals, contains, starts with, greater than, and less than. Combine several with ALL, where every condition must match, or ANY, where one is enough.
A thread that gets a tag later starts its SLA when the tag makes a policy match, unless the thread already has a deadline.
When you add, edit, reorder, or delete a policy, Productlane re-evaluates your open threads about 30 seconds after your last change. Each thread gets the deadline your current policies give it, and a thread that no policy matches any more loses its deadline. Closed threads, threads your team already answered, and threads where someone set or removed the deadline by hand keep what they have. A deadline that has already passed does not send an at risk or breach notification.
Default policies
Turning on SLAs for the first time creates four policies:
Policy | First response | Next response | Time to close |
|---|---|---|---|
High Priority | 1 hour | 4 hours | 1 day |
Medium Priority | 4 hours | 8 hours | 2 days |
Low Priority | 8 hours | 1 day | 1 week |
Default (all threads) | None | None | None |
Edit, reorder, add, or remove them at any time.
A thread that matches only the Default policy has no deadline, so it never shows as breached, however long it waits. To make those threads breach after 7 days, set First response and Next response on the Default policy to 7 days. First response covers a new thread, and Next response covers a thread where the customer wrote back. A thread that matches a policy higher in the list uses that policy's targets instead.
With Use office hours on, a target counts only time inside your office hours. A 7-day target then takes longer than 7 calendar days to run out, because nights, weekends, and holidays do not count.
Turn it on
Go to Settings > Office hours & SLAs.
Turn on Enable SLAs.
Turn on Use office hours to count only time inside your office hours. Nights, weekends, and holidays then don't count, and a deadline that would fall outside your hours moves to the start of the next window.
Add policies with Add Policy, or edit the defaults.
See Office hours to set your hours and timezone.
Manual overrides
You can set or remove the SLA deadline on any single thread. Productlane keeps your manual deadline and does not recalculate it.
