All articles

Duty hours, Away and breaks

What it is for: duty hours tell the Slow replies report when each person is meant to answer customers. A customer's wait then counts against a person only while that person is on duty. A team that sets no shifts keeps the report exactly as before.

Where: Settings → Duty hours.

/settings/duty-hours

Weekly shifts:

  • For each person and each business, add one or more time ranges per day with the time pickers.
  • A range that ends at or before its start time runs past midnight. It ends the next day and belongs to the day it starts (for example 22:00–02:00 on Monday).
  • Times are in your team's time zone.
  • Changes apply from the moment you save.

Who is on duty, minute by minute:

  1. Someone Away is not on duty.
  2. Someone on a break is not on duty.
  3. Otherwise a person is on duty inside their own shifts.
  4. A person with no shifts is on duty whenever someone else in the business is.
  5. If nobody in a business has shifts, the report works as before for that business.

Signing in or being active never changes this.

Away (absence):

  • Set it in Settings → Notifications → Availability.
  • Every absence has an end: choose Rest of today, or A date range (which can start on a later day).
  • It ends by itself.
  • While you are Away, a customer who writes to one of your chats is handed back to the team, as before.

/settings/notifications

Breaks:

  • In the same place, start a break of 15, 30 or 60 minutes, or another length.
  • A break never lasts past the end of your shift, and it ends by itself.
  • A break does not hand your chats back.

Replying while Away or on a break: replying does not end it. Nashir offers to end it for you after you reply.

How the wait is counted:

  • Assigned to someone who is on duty: counts against them.
  • Assigned to someone who is off duty, Away or on a break: counts for the team as a whole.
  • Unassigned: counts for the team, and also against whoever replied, for the minutes they were on duty.
  • Arrived outside duty hours: nobody was on duty, so it counts against no one. It is shown in its own row.
  • Staff away or on a break: nobody was on duty only because the scheduled people were Away or on a break. It is shown in its own row.
  • Shift-start grace: a customer who wrote before someone's shift began counts as slow for that person only after the limit plus the grace. The owner chooses the grace; it defaults to the limit.
  • A chat closed without a reply is never a fast reply. It is counted separately.
  • Replies from the WhatsApp phone app stay in their own row.

The report shows:

  • The share of messages answered within the limit, and the median reply time while on duty.
  • The customer's real waiting time beside them.
  • Per person: hours on shift, absences, break time per day, and a note when no shifts are set.
  • Someone Away with no end date (set before end dates were required) is flagged. They are never on duty until they come back.

Who can do what:

  • Everyone edits their own shifts, Away and breaks. The owner can set Who can edit their own shifts to The owner only.
  • The owner, and a manager of the business, can edit a teammate's.
  • Only the owner can change the past. Use Correct the past with a reason, and the report is recalculated.
  • Every change is listed in the Change log.

Who sees whose figures: by default everyone sees every person's figures. The owner can choose Owners and managers only. Each person always sees their own figures.

Duty hours, Away and breaks — Nashir