An open draft is an answer that an agent started but did not send. At the end of a shift, those drafts can sit in a shared inbox with no owner. The next agent may send a half-finished reply or start over and duplicate the work. A simple handover rule keeps every draft visible, owned, and safe to finish. The rule should be short enough to use during the last fifteen minutes of a busy shift.

Name the open-draft problem

Drafts are easy to ignore because they do not appear in the queue count. They still hold customer context and sometimes a partial promise. A draft that says "we can refund" but was never sent can mislead the next agent. The team should treat open drafts as work in progress, not as private notes.

Count the drafts at the end of a shift for one week. Group them by queue, age, and owner. A small number may be normal, while a growing pile suggests the reply process is too slow. Use the count to decide whether the rule needs a strict cutoff.

Define a draft that must be handed over

Hand over any draft that contains customer-specific facts, a promise, or a decision. A draft that only holds a greeting can be deleted. The rule should name the fields that make a draft material, such as a refund amount or a callback time. That definition keeps the handover short and useful.

Exclude personal scratch notes from the shared inbox. Agents should keep private reminders in a separate tool that does not sync to the customer record. A shared draft should be safe for another agent to read. If it is not, it does not belong in the shared queue.

Write the handover note

Add a short note at the top of the draft with the owner, the next step, and the risk. Name the customer question in one line so the next agent does not have to reconstruct it. State whether the draft can be sent as written or needs a review. The note should be short enough to read in a few seconds.

Use the same note format for every queue. A consistent header makes the drafts scannable during a busy handover. Include the time the draft was last edited. That timestamp shows whether the context is still current.

Choose the cutoff time

Set a cutoff before the shift ends, not at the last minute. Agents need time to finish a draft, hand it over, or delete it. A cutoff of fifteen minutes before the handover gives the lead time to check the list. Publish the cutoff in the shift calendar.

Decide how the cutoff interacts with an active customer reply. An agent who is mid-send should finish, while an agent who is still researching should hand over. The rule should not force a half-written answer into the queue. A short exception for active sends keeps the process humane and accurate.

Assign an owner for every draft

The handover lead should review the draft list and assign each item to a named agent. An unassigned draft is the same as an abandoned case. The assignment should be visible in the inbox, not only in a chat message. The new owner should acknowledge the draft before the old shift leaves.

Give the new owner authority to delete a draft that is no longer needed. A draft that repeats an answer already sent should not be kept for appearance. Record the deletion reason in the case. That record shows the draft was handled rather than lost.

Close or delete stale drafts

Set an age limit for drafts that no one has claimed. A draft older than the response target should be reviewed by the lead. The lead can send it, merge it into a new reply, or close it with a note. Leaving it open hides the fact that the customer is still waiting.

Check for drafts that duplicate an open case. A customer may have written again and received a fresh reply while the old draft stayed open. Sending the old draft would confuse the thread. Merge the useful facts into the active case and close the stale draft.

Review draft counts weekly

Report the number of drafts at each handover and the number that crossed a shift. A stable count is a sign that the rule is working. A rising count may mean the cutoff is too late or the workload is too high. Compare the count with the response time to see which explanation fits.

Sample a few handovers for note quality. Check whether the next agent could act without asking a question. Share the best example with the team and repair the weakest one. Keep the review short so it does not become another queue.

A draft is a promise in progress, even when the customer has not seen it. The handover rule should define what counts, who owns it, and when it must be closed. The cutoff should leave enough time to finish or pass the work. That discipline keeps the shared inbox from hiding unfinished answers.