Docs/Working hours5 min read

GUIDE

Working hours and enforcement.

Define when your team is on shift — at the workspace level and per agent — and decide what happens when an agent opens a conversation outside their hours.

§ 01How it works

Working hours are a weekly schedule with a timezone. The workspace sets a default; each agent can override specific days. Outside an agent’s hours, the app’s behaviour depends on the enforcement mode.

§ 02Enforcement modes

Each agent has one of three enforcement modes, gated by your plan.

  • Enforce — the composer is read-only off-shift
  • Advisory — a warning banner, but the agent can still reply
  • Log-only — no UI change; off-shift replies are simply recorded

§ 03The schedule shape

A schedule is per-day open/closed with from/until times in the workspace timezone. An empty day means closed.

JSONA workspace working-hours schedule
{
  "timezone": "Asia/Erbil",
  "schedule": {
    "sunday":    [{ "from": "09:00", "to": "18:00" }],
    "monday":    [{ "from": "09:00", "to": "18:00" }],
    "friday":    [],
    "saturday":  []
  }
}

§ 04Per-agent enforcement

Enforcement is set per agent and applied server-side when a message is sent, so it cannot be bypassed by a client.

  • Set the mode from Team → agent → working-hours enforcement
  • Starter gets log-only; Growth and Enterprise get all three modes

Was this guide useful?

Suggest an edit ↗