What does AI mean for customer service during an M&A integration?

When two customer-service organisations merge (after an acquisition or merger), the customer experience used to lag the integration by a year: two different support phone numbers, two different ticketing systems, customers transferred between them with no shared context. AI lets the customer-facing surface look unified while the back-ends integrate underneath. The trick is doing it cleanly enough that the customer cannot tell the integration is still in progress.

Two companies merge. Their CS teams use different tools, different policies, different SLAs. Customers from both sides keep calling. The integration of the two ticketing systems is a 9-to-18-month project. Customers are not going to wait. AI can sit in front of both back-ends and present a single experience while the integration completes.

What people in the field are saying

Blake Morgan's "Unifying the contact center, Salesforce's..." covers the platform-consolidation trend in CX, which is the same problem at a smaller scale: merging two stacks into one without breaking customer experience during the merge.

What does AI do here?

Sit at the front of the conversation. Identify which company's customer is contacting. Route to the right back-end. Translate between the two systems' policies where they differ. Maintain a unified case record that spans both back-ends. Present one experience even though the underlying systems are still separate.

Where do the two policies clash?

Refund thresholds, escalation rules, SLAs, channels supported. Two policies cannot both be the customer-facing policy. The merging company has to decide quickly which policy is the public one, then have the AI enforce it across both back-ends. Postponing this decision means the customer sees inconsistency, which is worse than picking the wrong policy.

What does it not solve?

The actual data merge. Customer records, history, billing accounts all eventually have to be reconciled in one system. AI hides the gap; it does not close it. The integration project is still real and still needed. The value of AI is in buying time for the integration to be done properly, not in skipping it.

Where does this go wrong?

The AI surfaces inconsistencies it cannot reconcile (the customer's record exists in one system but not the other, or shows different status). The two teams' agents follow different policies, undoing the unified front. The integration project loses urgency because AI made the gap less visible, and the back-end merge drags for years.

What is the practical pattern?

Decide the public policy on day one. Wire AI to enforce it across both back-ends. Keep the integration project on its original timeline; the AI is a bridge, not a substitute. Audit the customer experience monthly to confirm the AI is hiding the gap, not exposing it. When the integration completes, retire the bridge logic; otherwise, it becomes permanent and adds cost.