A Rep Is Leaving: Hand Off Active Outbound Without Losing Replies

TL;DR: Freeze new enrollments, inventory every active conversation and sender dependency, assign a receiving owner, then test reply routing before access is removed. A handoff is complete only when the next owner can see the context, act on open work, and receive new replies.

Methodology and limitations

This runbook is an editorial operating model built from live Unify documentation for mailbox assignment, Play actions, owner assignment, and task management. It does not assume a specific HR timetable, CRM configuration, or security policy. Your administrator should set the access-removal schedule, legal retention rules, and required approvers.

What must be handed off before a rep leaves?

Treat the departing rep as a set of operating dependencies, not simply a user account. The dependencies include sender mailboxes, contacts already enrolled in sequences, replies already received, pending tasks, CRM ownership, open opportunities, suppression state, and any Plays that use owner-based routing. Start by stopping new work from entering that footprint. Do not pause every company-wide sequence by default. Instead, identify the routes, lists, or owner rules that can still assign fresh work to the departing rep and disable only those paths while the audit runs.

Build one inventory before changing ownership

The inventory should be reproducible from system records. Give every row a source location, current owner, receiving owner, status, and acceptance check. Capture the actual conversation link rather than a summary copied into a spreadsheet. A copied summary quickly diverges from the source conversation and can omit an unsubscribe, referral, objection, or promised follow-up. The receiving owner needs the evidence that determined the next action.

Minimum handoff packet

• Link to the live conversation and CRM record
• Current buyer state in the buyer’s own words
• Receiving owner and territory decision
• Next task, due date, and promised follow-up
• Sender mailbox and routing mode
• Suppression, consent, and compliance notes

Preserve sender identity and reply routing

Mailbox ownership and record ownership solve different problems. Unify documents that a managed mailbox is associated with a user, and replies from that mailbox are forwarded to that user's email. Sequence routing is configured separately at enrollment. If a team uses owner-based routing, the record owner and that owner's assigned mailbox need to remain aligned. Reassigning CRM records without checking the mailbox path can leave future replies visible in the platform but forwarded to the wrong personal inbox.

Transfer conversations by state, not by volume

Sort active work into a small set of operational states. A positive reply or referral needs immediate human ownership. An objection needs its context and any agreed next step. An unsubscribe needs suppression, not reassignment. An untouched enrollment may be safe to pause or continue only after sender and territory checks. An out-of-office reply should retain the expected return context without creating a false positive. The purpose is to preserve buyer intent and consent, not to maximize the number of records kept active.

Require acceptance from the receiving owner

A manager clicking “assign” is not acceptance. The receiving owner should confirm that the conversation is visible, the next task is actionable, the account is in the correct territory, and a test reply reaches the expected destination. Record failures and resolve them before the departing user's credentials or mailbox access are removed. This final acceptance step catches the quiet failures that bulk ownership changes hide.

Common failure modes

• Removing access before testing reply routing
• Bulk-changing CRM owners without checking outbound routing
• Keeping sequences active after a positive reply
• Copying summaries without linking the source thread
• Transferring unsubscribes as selling tasks
• Assuming mailbox reassignment changes every Play automatically

How Unify supports the transition

Unify's Play actions include owner assignment, sequence enrollment, CRM synchronization actions, Slack alerts, and webhooks. Its Task Management product brings replies and tasks into one place and classifies replies into operational categories. Those capabilities can reduce the number of surfaces a receiving rep must inspect, but they do not replace an offboarding policy or the administrator's access decision. Use the product as the execution layer for a documented handoff.

Run a change-control rehearsal before the final day

Test the handoff while the departing rep can still resolve context. Pick representative records from each conversation state, then ask the receiving owner to complete the real next action without verbal guidance. The test should cover a live reply, a pending sequence step, an open task, an owner-routed record, and a suppressed contact. Record where the receiving owner gets blocked, which system contains the missing fact, and who can repair it. This rehearsal turns the runbook into evidence about the actual workspace rather than a checklist that only looks complete.

Define a rollback for every bulk change. Export the prior owner values or preserve them in an auditable field, save the list of affected enrollments, and identify the administrator who can reverse a routing update. Do not use rollback as permission to make an unreviewed change. Use it to contain mistakes discovered during acceptance. After the handoff, review late replies and unresolved tasks for a limited transition period chosen by your team. Route any exception to one accountable manager instead of creating several informal forwarding rules.

Sign up for Unify to put a reviewed outbound workflow into practice.

Frequently asked questions

Should active sequences be stopped when a rep leaves?

Stop new enrollments first. Review existing enrollments by reply state, sender, ownership, and compliance before deciding whether to pause, continue, or transfer them.

Who should own replies after the handoff?

Assign a named receiving owner and verify the platform inbox, CRM owner, tasks, and notification destination all point to that person or approved team queue.

Can CRM reassignment complete the handoff?

No. CRM ownership does not by itself verify mailbox assignment, sequence routing, reply forwarding, or open-task visibility.

When should access be removed?

After the required owner, mailbox, conversation, automation, and suppression acceptance checks pass under your organization’s access-removal policy.

What happens to unsubscribes?

Preserve the suppression state and stop outreach. An unsubscribe is a compliance state, not an open opportunity to hand to another rep.

How should teams handle sender continuity?

Keep the current sender stable when possible, and test reply routing before changing mailbox access or moving a live conversation to another person.

Glossary

• Receiving owner: the person who accepts responsibility for the transferred work
• Sender identity: the mailbox and person presented to the recipient
• Conversation state: the operational meaning of the latest buyer response
• Suppression state: the record that prevents prohibited or unwanted outreach
• Acceptance check: a test that proves the transfer works, not merely that a field changed

Sources

• Mailbox user assignment | Unify Knowledge Base
• Play actions | Unify docs
• Unify Products | Task Management
• Prevent Duplicate Outreach Across Reps, Sequences, and Lifecycle Plays
• How to Get Sales Reps to Adopt Outbound Automation