Reply lock
From 1.20.20 the desk can make sure only one agent writes a ticket’s reply at a time. It builds on presence and collision warnings: those tell you who else is on a ticket; the reply lock stops two people answering the requester at once.
Switching it on
Section titled “Switching it on”Desk settings → Reply lock (search for “lock” or “collision”). It is off on desks that existed before 1.20.20 and on for brand-new desks. You can also set the idle time, from 1 to 15 minutes (2 by default), and see the replies being written right now.
How it works
Section titled “How it works”- The first agent to start a reply holds it. Typing, pasting, or inserting a macro, canned response, article, Claude draft or file takes the lock. Just opening a ticket doesn’t.
- Everyone else sees who. Their reply box is read-only with the holder’s avatar and “Sam Lee is replying”. Hover or focus the avatar for “Sam Lee · replying since 10:42”. The same avatar shows on the ticket’s row in the queue and in the ticket header.
- Internal notes are never locked. Anyone can still add one.
- It lets go by itself when the holder sends, empties the box, presses Let go, closes the ticket, or doesn’t touch the reply for the idle time. A lock is never held for more than 60 minutes without a send.
- Up to 3 at once. An agent holds at most three locks; starting a fourth reply releases their oldest.
- The pop-out. When you pop the reply out, the lock goes with it, and comes back with Bring back.
- Live. Others see a lock appear or clear within a couple of seconds.
Take over and release
Section titled “Take over and release”Managers and admins, and team leads in the teams they lead, see Take over and Release on a locked reply. A team lead can’t take over from a manager or an admin.
Taking over asks you to confirm, then moves the lock to you. The person who was writing sees “Priya took over this reply. Your text is kept as a draft.” with Copy my text, so nothing they typed is lost. Release frees the lock without taking it. Admins can release all of one person’s locks from Desk settings → Reply lock.
Who may take over is the Take over a reply capability in Desk roles, on for Team lead and Manager by default.
What is refused
Section titled “What is refused”While a reply is locked, a public reply from anyone but the holder is
refused, whichever way it is sent: the desk, the
API (409 with code: "reply_locked"),
macros, Claude, incident updates and approving a held
newbie reply. The message names the
holder and says you can still add an internal note.
- An agent replying by email while someone else holds the lock: the email is kept as an internal note on the ticket, so nothing is lost.
- Automations that an agent’s own action sets off meet the lock as that agent. Automations set off by the requester or the system, replies from requesters, and imports are not affected.
- Approving a held newbie reply after someone else has replied asks before sending.
In the audit log
Section titled “In the audit log”| Action | Shown as |
|---|---|
helpdesk.reply_lock.taken_over |
Took over a reply (with both people) |
helpdesk.reply_lock.released |
Released someone’s reply lock |
helpdesk.reply_lock.cap_released |
A reply lock released because the agent started a fourth |
