The part of a merger nobody budgets for

Every merger plan has a line for the core conversion, the rebrand and the vote. Almost none have a line for the moment a frontline employee picks up the phone and doesn’t know the answer.

Once the deal goes public, that moment happens all day. Two teams, two sets of policies, two ways of doing things, and one set of customers and members asking the same question: what changes for me?

The questions hit both sides at once.

Most merger plans pour their energy into what to tell customers and members. Far less goes into whether the people doing the telling are ready. That gap is where service slips, wait times climb and good employees start updating their resumes.

Informed isn’t ready

A memo can tell your team the new fee schedule. It can’t make sure they can explain it to an upset caller at 4:45 on a Friday.

Getting two teams to serve as one takes four things:

Most merger tools stop at the first step. The other three are where a merger is actually won or lost on the frontline.

All four run on one platform and draw from the same knowledge. Update a policy once, and it shows up in the answer a rep looks up, the scenario they practice and what Voice Assistant tells a caller.

The four phases, and what each team needs

Readiness isn’t a conversion-week project. It starts while the deal is still quiet and runs for months after the systems combine.

Knowing the answer runs the whole way through. Practice starts before the news breaks, and proving it carries on long after the project team moves on.

1. The quiet months

The deal is in talks and the circle is small. This is the cheapest time to find out where your two teams disagree.

• Acquiring institution: Map where your policies and theirs differ. Get procedures into one place so there’s a single source of truth to build from.
• Acquired institution: Write down how your team actually handles the top questions today, including the workarounds that never made it into a procedure. That knowledge walks out the door if nobody captures it.

Camden National Bank had Voice Assistant in place long before its merger was announced, and it had already cut abandonment from 25% to 10%. Melodie Myers, who runs its contact center, says that head start changed everything:

“Having those previous friction points already resolved made that merger go much smoother than we ever could have anticipated.”

2. The announcement

Staff hear the news with everyone else, and the questions start before the answers exist.

• Acquiring institution: Give both teams one place to look things up, and update it as decisions land. Set Voice Assistant greetings and Digital Assistant messages so customers and members hear the same story in every channel. Better yet, reach them before they call: an outbound Posh Agent can welcome incoming customers and members by text, email or voice, spell out what’s changing and what isn’t, and tell them where to ask questions.
• Acquired institution: Let people practice the new policies before they need them on a live call. Confidence is what’s most at risk here, and practice is how you protect it.

3. Conversion

Systems combine and volume spikes: logins, cards, routing numbers, bill pay.

• Acquiring institution: Let AI take the routine questions so your people handle the hard ones. Voice Assistant completes banking transactions, not just answers, because it integrates with the core. Inbound Posh Agents finish common tasks end to end, like unlocking an account or servicing a card, so the most frequent conversion calls never need a person. Posh Answers keeps site search current on things like the new routing number. And consider separate queues for existing and incoming customers, so the people who weren’t part of the deal never feel it.
• Acquired institution: Start narrow. Train on the handful of topics incoming customers will call about most, like online banking and debit cards, then make sure your team can find everything else in the moment without waiting on a supervisor.

4. The long tail

The project team moves on. Old habits come back. Answers start to drift.

• Acquiring institution: Check what’s actually said on calls, not just what’s in the procedure. CoachQA reviews conversations against your merged policies and flags compliance issues as each one is analyzed, and it works with the systems you already have.
• Acquired institution: Turn the gaps CoachQA finds into new Posh Simulator scenarios, so coaching targets what people actually get wrong.

“Isn’t it too late once the deal is announced?”

That’s the common wisdom: once a merger goes public, bandwidth disappears and nobody can take on anything new. It’s true for projects that need months of build. It isn’t true for tools that start from what you already have.

Knowledge Assistant works from the documents you already have, so your team isn’t writing answers from scratch. FVCbank had Knowledge Assistant live in under 30 days, replacing 97 folders and 2 TB of documents.

That means the employee-facing tools can go in during integration, right when the need is loudest. Voice Assistant takes a bit longer to stand up, which is why the quiet months are the best time to start it.

Your merger readiness check (no software required)

Run these this week. They’ll show you where your two teams disagree before customers and members find out for you.

1. Ask five people from each team the same ten questions. Compare the answers side by side. Every mismatch is a call that will go two different ways.
2. Pull the top 25 call drivers from both institutions. Flag every one where the policies conflict.
3. List every place a procedure lives today. Shared drives, binders, intranet pages, the one inbox everyone forwards to. That’s how many places an answer can go stale.
4. Listen to ten calls from each team. Note every hesitation, hold and “let me check on that.”
5. Count how many calls actually get reviewed. At 4Front Credit Union, one top rep had taken 1,388 calls, and 5 had been scored.
6. Ask your newest hires what they still can’t find. They’ll tell you faster than any audit.

Doing this for ten calls is a great start. Doing it for every call is what CoachQA is for.

What it looks like in practice

Camden National Bank, a $7B bank in Camden, Maine, took on about 30,000 new customers in its merger. The team planned for four to six weeks of conversion disruption. It took two, with no added headcount.

Here’s what Melodie Myers, VP Customer Care Center Manager, and her team did:

• Kept existing customers out of it. A custom call flow sent current Camden customers to their usual queue and incoming customers to their own. Her goal was for existing customers not to even notice the merger, and there were no complaints from them during it.
• Trained the incoming team on just what mattered. The acquired call center learned the handful of things new customers would call about most, like online banking and debit cards, and worked the dedicated queue.
• Sent callers straight to the fix. New prompts routed people directly to debit card activation and online banking help. Many got there without an agent.
• Kept the numbers separate. Split queues let Melodie confirm the existing customer experience held steady month over month.

Posh Answers resolved hundreds of questions online along the way.

“We thought it was going to take four to six weeks to get all of the customers fully converted. After about two weeks, it was basically over. We all looked at each other like, is this really it?”

Melodie Myers, VP Customer Care Center Manager, Camden National Bank

Read the full Camden National Bank story

The readiness side shows up across Posh clients too:

• Practice: At Financial Partners Credit Union, the newest hire reached 90% accuracy by the third try in Posh Simulator, within an hour. Simulator plus Knowledge Assistant got new hires on calls within days.
• Know: Farmers Bank & Trust built Knowledge Assistant into onboarding and cut handle time 12%.
• Absorb: One Nevada Credit Union replaced its IVR with Voice Assistant after a Symitar core conversion. With Digital Assistant alongside it, the contact center closed on Sundays after an 80% drop.

Questions to ask any AI vendor during a merger

1. Can it work from our procedures as they stand today, before the merged policies are final?
2. Can our staff practice new policies, or only look them up?
3. Can you show us which employees are still giving the old answer?
4. When one policy changes, how many places do we have to update it?
5. Does it work with the systems we already have, or does something need to be ripped out first?
6. Who on your team has been through a bank or credit union merger, and what did you learn?

FAQ