Configure the resolution timer

The resolution timer controls how long a Done conversation waits before it auto-archives. Tune it to match how your customers actually follow up.

Before you start

• An Owner or Admin role — this setting is workspace-wide, not per-team.
• A read of Conversation resolution so you know what the timer affects (Done → Archived flow, customer reopen window, CSAT firing).

Where to configure

1. Open Settings.
2. Choose Conversation Resolution.
3. The page shows the current resolution duration as Days, Hours, and Minutes.

The three fields combine into a single duration. Set 2 days, 0 hours, 0 minutes for a 48-hour window; set 0 days, 4 hours, 0 minutes for a 4-hour window.

The timer is business-hours aware — it consults your opening hours and any configured public holidays, so a conversation marked Done late on a Friday isn’t archived over the weekend before someone could see a customer reply.

Choosing a duration

Think about how long it typically takes a customer to follow up with “actually, one more thing”:

• Fast, transactional (chat-heavy, in-app) — 4–24 hours
• Standard mix (email + chat) — 1–3 days
• Slow, async (email-heavy, B2B) — 3–7 days
• Very slow (enterprise, contract-driven) — 7–14 days

Defaults skew toward the middle (1–3 days). Adjust if your team’s reality is different.

Don’t go too short

Common mistake: “we want a clean inbox, so let’s archive after 4 hours.” Effects:

• Customers who reply 6 hours later trigger a brand-new conversation with no context.
• Agents lose continuity on multi-step issues.
• Customer experience degrades because each reply feels like starting over.

If a clean inbox is the goal, look at filtering and saved filters first. Shrink the resolution window only if you can confidently say “customers don’t come back after X hours” for the majority of your traffic.

Don’t go too long

The other extreme — “we never want to lose context, archive after 30 days.” Effects:

• The Done tab balloons and becomes unmanageable.
• Reports lag because resolved-but-not-archived conversations skew the metrics.
• CSAT (if it fires at archive) takes forever to send — customers have moved on emotionally.
• Genuinely closed conversations clutter search.

A few days is usually plenty. Customers who genuinely need to come back later tend to reach out again anyway, which creates a fresh conversation linked to the archived one.

What if you want different windows for different channels?

There is no per-channel or per-tag resolution override on this page today. The timer is one workspace-wide value.

If you really need different rhythms for different cohorts (chat vs. email, VIP vs. standard), express that distinction with SLA policies — SLA assignments are channel- and tag-aware — and keep resolution as a single sensible default.

Testing your settings

After changing the resolution duration:

1. Mark a small batch of test conversations Done.
2. Watch them in the Done tab — confirm the auto-archive runs at roughly the time you set, accounting for opening hours.
3. Wait for the first auto-archive cycle and verify CSAT (if you fire it at archive) goes out correctly.
4. Check reporting metrics over the following days — Done counts should stabilize at a new equilibrium.

Verify it worked

• The setting saves without error.
• Done conversations marked after the change archive on the new schedule.
• A customer reply during the Done window still reopens the conversation to Active, regardless of the duration you picked.

Related: SLA timer pause

The resolution timer is independent of the SLA timer. Done conversations have their SLA timer paused; reopening from Done picks up where SLA left off.