Discuss service continuity during an acquisition

When two contact centers merge, the pressure to unify operations arrives before either side has settled how the combined business will actually run. Leaders on the buying side want one phone number, one case queue, one brand voice, right away. As an account executive, you are often the person in the room who has to slow that instinct down without sounding like you are stalling the deal. How you handle this conversation decides whether the client trusts your platform to guide the transition or starts treating you as an obstacle to it. DealSpeak built its acquisition scenario for Contact Centers practice conversations because this exact conversation trips up account executives more than almost any other.

Why this conversation goes wrong

During an acquisition, everyone above your contact is working against a clock they did not set. Integration leaders answer to a steering committee that wants a single operating model announced fast. That pressure lands on you as a question that sounds technical but is not. When someone asks whether your platform can merge both centers on day one, they are usually not asking about system capability. They are asking you to absorb their risk. Answer with a flat yes and you inherit every assumption buried in that yes, who owns the customer records, who approves changes, whether regulators need to sign off, none of which your platform controls. Answer with a flat no and you sound unhelpful at the exact moment the client needs a partner. The conversation goes wrong the moment either side treats an organizational decision as a technical fact waiting to be confirmed.

How to prepare

Before the call, separate two categories in your own head. One is what must not break for customers in the first few months. The other is what the combined company decides later about platforms, brands, and staffing. Write down the customer groups most likely to notice a change first, usually the highest value accounts or the ones already used to a specific phone number or support contact. Then list the roles that typically hold authority over communications, customer records, and change approval in a business this size, service leadership, a records owner, and whoever runs the integration office. You will not know the actual names before the call, but knowing the roles lets you ask precise questions instead of vague ones.

Think past the first assessment too. If the eventual plan puts agents from both centers onto one shared platform, their acceptance of the new tools is a separate risk from the technical merge, and it tends to show up later than people expect. Including agent acceptance in a contact center pilot explains why a pilot that looks successful on paper can still fail once agents are the ones using it every day. And if you have not sat with either team to see how their agents actually work, do that before you propose combining anything. Discover the agent desktop before proposing change covers why skipping that step produces proposals that do not match how the work actually happens.

What to say

Keep your opening short and put the decision back where it belongs, with the client's own owners, while still showing you have a path forward.

"We need one service operation as soon as the deal closes," says Priya, who is leading the integration. "Can your platform merge both centers on day one."

Marcus answers, "I can help you run the assessment that gets you there, but whether that happens on day one depends on which processes and systems your teams choose to combine first. Which customers would feel a change the fastest."

Priya thinks about it and names two groups, enterprise support callers and anyone contacting billing.

Marcus follows with, "Who owns the messages those customers receive right now, and who signs off on changes to how their accounts get handled."

Priya names the service vice president, the billing lead, and the integration office itself.

Marcus closes with, "Let us get those three in a room. We will map what has to keep working for those customers, who owns the records behind it, and what order the decisions need to happen in. That gives you a real sequence instead of a guess."

Notice what Marcus never did. He never promised a day one merge, and he never refused one either. He turned a pressure question into a short list of owners and facts, then made a concrete offer instead of a prediction.

Mistakes to avoid

The most common mistake is answering the technical question as if it were the whole question. A buyer asking about day one integration is really asking who owns the risk if something breaks, and jumping straight into platform capability skips past that. A second mistake is naming a timeline before you know who approves changes. Committing to weeks or months before you have identified the approver sets an expectation you cannot control and will likely miss. A third mistake is asking broad questions instead of specific ones. Asking someone to describe their target operating model tends to produce a vague answer full of hedging. Asking who owns the messages a customer receives produces a name you can act on. A fourth mistake is letting the whole conversation stay abstract. If you finish the call without a list of customer groups, an owner for each, and a next meeting on the calendar, you have had a pleasant conversation and made no real progress.

How to practice and score it

Write a short continuity brief for one imagined acquisition before you ever get on a real call. Name one customer group, the single process that must keep working for them, the person who owns their records, and the person who approves changes to how they are served. Doing this once forces you to notice how many blanks you cannot fill in from memory, which is exactly what happens on a live call when you have not prepared.

If you are a manager reviewing a recorded practice run, listen for a few specific things. Notice whether the account executive ever states an integration decision as settled fact instead of asking who owns it. Notice whether they name at least one customer group and one owner by role before the call ends. Notice whether they offer a concrete next step, a meeting with the actual owners, rather than a general promise to follow up later. A rep who does the first two well and skips the third has done good diagnostic work and then let it go nowhere.

Run the same scenario a few times with different personas, an anxious integration lead, a confident one who wants a fast answer, a skeptical one who has already been burned by a vendor promise. The core moves stay the same every time, separate urgent continuity from later platform decisions, ask for owners by name, and offer a concrete next step. What changes each time is how much pressure you have to absorb before you get there.

Handled well, this conversation builds trust instead of spending it. You are not the person who has to know every answer about the combined operation on day one. You are the person who asks the questions that get the client to a real answer faster than they would reach one alone.