New: meetings booked from every replySee how
Back to Blog
Unified Inbox • • 9 min read

How to Move Cold Email Reply Handling Into a Unified Inbox: A Migration Playbook

Switching reply handling from scattered sequencer inboxes to one unified inbox is mostly an operations project, not a software one. This playbook covers the inventory, the parallel run, the cutover, write-back checks and how to retire the old surfaces without dropping a single live conversation.

AW

Anirudh Walia

Founder & CEO

Small white trays scattered on a white floor, each with a green rail running into one larger tray holding a neat stack of cards topped by a green card, beside the headline "Move every reply into one inbox."

How to Move Cold Email Reply Handling Into a Unified Inbox: A Migration Playbook

Deciding you need a unified inbox is the easy part. Most teams get there the week someone misses a “can we talk Thursday” reply because it landed in the third sequencer workspace nobody had open. The hard part is the move itself: taking a reply operation that is spread across sending tools, LinkedIn accounts, Slack pings and personal habits, and putting it in one place without losing a live conversation on the way.

This playbook is about that move. It assumes you have already chosen a unified inbox (if you have not, start with how to evaluate one). What follows is the order of operations we recommend: inventory, rules, connection, a parallel run, the cutover, and then switching the old surfaces off properly.

Why migrations go wrong

Reply handling looks simple from the outside. A reply comes in, someone answers it. In practice, most teams have built a quiet web of workarounds around their sending tools:

  • An SDR who checks one client’s workspace first thing every morning because that client complains the most.
  • A Slack notification someone set up two years ago that only fires for one campaign.
  • A shared doc of “good answers” that lives in one person’s bookmarks.
  • A rule in one sequencer that pauses a lead on reply, and no equivalent rule in the others.

None of this is written down, and all of it does real work. A migration that only moves the mailboxes and ignores the habits will drop replies in the gaps. The goal of the playbook below is to make those habits visible first, then rebuild them deliberately in the new inbox.

Step 1: Inventory every reply surface

Before you connect anything, list every place a reply can arrive today. Be literal about it. For each surface, write down:

FieldWhat to capture
SourceSequencer workspace, LinkedIn tool, CRM inbox, personal mailbox
Client or teamWho the replies belong to
Sending identitiesWhich mailboxes or LinkedIn profiles send from it
Who checks it todayNamed person, and how often
AutomationsPause-on-reply, tagging, CRM sync, Slack alerts
QuirksAnything that “only works if you do it this way”

Expect the list to be longer than you think. The surfaces people forget are usually the ones that matter: a founder’s own mailbox used for a handful of high-value sends, a LinkedIn profile that belongs to a former employee, or a client who sends from their own platform and forwards replies by hand.

Ask every person who touches replies to add to the list. The goal is not a perfect spreadsheet. It is to make sure nothing is checked only out of habit.

Step 2: Write down the reply rules you actually use

Next, capture how replies are handled, not just where they arrive. Most of this lives in people’s heads. Sit with whoever handles replies today and write down:

  • Reply categories. Interested, pricing question, objection, wrong person, not now, unsubscribe, out of office. Use the ones your team already recognises, and keep the triage categories simple.
  • Who owns each category. The person who answers, and their backup.
  • Response targets. How quickly each category should get a reply during working hours, and what happens out of hours.
  • Hard rules. Opt-outs are honoured immediately everywhere. Pricing is never quoted without approval. Certain clients never get an automated reply.
  • Approved answers. The phrasing you already trust for common questions. If you do not have this written down, now is the time to start an approved answers library.

This step is where a migration pays for itself. Rules that were informal become explicit, and you will usually find at least one place where two people have been answering the same question in two different ways.

Step 3: Map identities and clients before connecting

A unified inbox is only safe if every reply goes back out from the right sender, under the right client, inside the right thread. Before connecting, decide:

  • Client partitions. Which mailboxes and LinkedIn profiles belong to which client or business unit. Nothing should be “shared” by accident.
  • Sender of record. Replies should leave from the same mailbox that sent the original message. If you are unsure why that matters, read this first.
  • Cross-channel matching. How a prospect who replies on LinkedIn and email will be recognised as the same person, so they do not get two different answers.
  • Calendars. Which calendar each client’s meetings go to, so a booked call never lands on the wrong team.

Write this mapping down as a table and keep it. It becomes the reference when a new client or new batch of mailboxes is added later.

Step 4: Connect one client first

Do not connect everything at once. Pick one client or one team and connect only their sources. A good first candidate is busy enough to test the setup properly but not so sensitive that a mistake would be serious.

Once connected, check the basics before any real reply is handled from the new inbox:

  1. Threading. Send a test reply to a few mailboxes and confirm each arrives in the right thread under the right client.
  2. Sending. Reply from the unified inbox and confirm the response leaves from the original mailbox, in the original thread. Look at the headers if you are not certain.
  3. LinkedIn. If the client runs LinkedIn outreach, confirm messages arrive and replies go back out from the right profile.
  4. Write-back. Mark a test reply as an opt-out and confirm the lead is suppressed in the sending tool. Mark one as a booked meeting and confirm the sequence pauses on every channel.

Write-back is the step teams skip most often, and it causes the most damage. An opt-out that is closed in the inbox but still active in the sequencer means the next scheduled email still goes out.

Step 5: Run in parallel, with approval on

For the first client, run the old surfaces and the new inbox side by side for a short, fixed period. During the parallel run:

  • Every reply is handled in the new inbox. The old surfaces are only for checking that nothing was missed.
  • Every AI-drafted reply goes to approval. With Underfive, inbox agents draft replies and send them to Slack, where a person approves, edits or rejects them before anything is sent. During a migration, keep every category on approval. You are checking the setup, not testing your appetite for automation.
  • One person reconciles daily. At the end of each day, compare what arrived in the old surfaces with what arrived in the new inbox. Every reply should appear in both. Anything that appears in only one place is a connection or threading problem, and you fix it before moving on.
  • Reviewers note every edit. When an approver changes a draft, they note why. Those notes become better rules and better approved answers.

Keep the parallel run short and decide its length in advance. A parallel run with no end date tends to become two permanent systems.

Step 6: Cut over, then roll out by client

When the daily reconciliation has been clean for several days in a row and approvers are editing drafts less often, cut that client over. In practice, cutover means:

  • The new inbox is the only place replies are handled. Say so in writing to everyone involved.
  • Old notifications are switched off. Leftover Slack alerts and email forwards from the old setup cause double handling.
  • Response targets are measured from the new inbox. You now have one place to see time to first reply across channels, so start tracking it.

Then repeat steps 4 to 6 for the next client or team. Each one should go faster, because the rules and identity mapping you wrote down in steps 2 and 3 carry over. Leave the most complicated or most sensitive client until last, when the process is well practised.

Step 7: Retire the old surfaces properly

Old reply surfaces do not disappear on their own. Once every client is cut over:

  • Remove reply-checking duties from people’s routines and calendars, so nobody keeps opening the old tabs out of habit.
  • Keep the sending tools sending. Migrating reply handling does not mean changing how you send. The sequencers keep running campaigns. They just stop being where replies wait.
  • Check old automations. Any pause-on-reply or tagging rule that used to run in a sequencer should now be handled through write-back. Turn off duplicates so the two systems do not fight.
  • Archive, do not delete. Keep the old conversation history accessible for a while in case a client asks what was said before the switch.

What to measure after the move

The point of the migration is faster, more consistent replies. Track a few simple measures from the new inbox, per client:

  • Median time to first reply, split by working hours and out of hours.
  • Share of drafts approved without edits, by category. This tells you where the agents are ready for more autonomy and where they are not.
  • Replies that needed a human decision, such as pricing or objections, and how long they waited.
  • Meetings booked from replies, so the move is judged on outcomes, not activity.

Review these after the first few weeks. When a reply category is consistently approved without edits, you can consider moving it to a lighter-touch setting. Do that one category at a time, and keep reviewing a sample. Our guide to AI inbox agent autonomy levels covers how to decide.

Common mistakes

Connecting every client on day one. One threading or identity problem then affects everyone at once, and it is hard to tell where it came from.

Skipping the write-back test. It is the only step where a mistake reaches prospects directly, through emails that should have stopped.

Letting the parallel run drift. Two systems handling the same replies is how prospects get two answers.

Moving tools but not rules. If the reply rules were never written down, the new inbox inherits the same inconsistency as the old ones.

Turning on auto-send during the migration. Change one thing at a time. Move the replies first, then adjust automation once the setup is proven.

Where Underfive fits

Underfive is a unified inbox for outbound replies across email and LinkedIn, with AI inbox agents that draft replies and send them to Slack for approval. Teams use it to bring replies from their existing sending tools into one place without changing how they send. If you are planning a move and want help mapping your current setup, book a demo and we will walk through it with you.

The bottom line

A reply migration is an operations project. Inventory every surface, write down the rules you actually use, map identities before connecting, start with one client, run in parallel with approval on, cut over deliberately, and retire the old surfaces properly. Do it in that order and the move makes replies faster without a single live conversation going missing along the way.

unified inbox unibox cold email reply management migration ai inbox agents reply desk operations

Share this article

AW

Written by

Anirudh Walia

Founder & CEO

Ready to reply faster?

Underfive responds to your leads in under 5 minutes, 24/7. Start converting more leads today.

Book a Demo