TSA Exit Acceleration
Every call answered from the first morning.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
TSA call center and telephony separation moves the carved-out entity's phone numbers, call routing, and contact-center platform off the seller's telephony onto its own before Day One. It is one of the few separation workstreams a customer experiences directly, so a slip is visible the moment someone calls. This is customer facing cutover work, which places it inside carve-out advisory. Mishandle it and the people the entity most needs reach silence.
Most separation workstreams are invisible to the outside world. Telephony is not. The phone numbers customers call, the routing that puts them in the right queue, and the contact center agents who answer are a direct, real time touchpoint with the people whose loyalty the standalone entity is trying to keep. When a ledger cutover goes slightly wrong, finance fixes it quietly; when a telephony cutover goes wrong, a customer calls the number on the invoice and gets dead air, and they notice instantly.
That visibility raises the stakes on the things that look mundane. A published customer service number that fails for even a few hours sends a clear signal that something is wrong with the company, exactly when the entity wants to project stability under new ownership. The same is true internally: if employees cannot make or receive calls on Day One, the business cannot operate, and the disruption is felt immediately across every customer facing team.
So the buyer treats telephony separation as a customer experience event, not just an IT task. The aim is that on Day One every published number still rings through to the right place, every agent can still take calls, and no caller can tell that anything changed behind the scenes. Achieving that invisibility is the measure of a good telephony cutover, and it takes far more planning than the simple act of moving a phone line suggests.
Phone numbers are the most sensitive asset in this workstream because they are printed on invoices, listed on websites, and saved in customers' phones. The entity usually wants to keep its existing numbers, which means porting them to its own carrier and platform. Number porting is a regulated, carrier driven process with its own timelines and rules, and it cannot be rushed on the day; it has to be scheduled, submitted, and confirmed well ahead, with each number tracked through the port.
Ownership complicates it. The numbers are often registered to the seller, so porting them to the entity requires the seller's cooperation and a clean authorisation, which is far easier to secure while the relationship is constructive than to chase later. The buyer establishes early which numbers the entity keeps, who currently holds them, and what the seller has to sign, so a number the customers rely on does not get stranded in a dispute over who owns it.
Timing the port is the delicate part. A number going through a port has a moment of transition, and the buyer schedules ports to avoid a window where calls fail, coordinating with the carriers so the handover is clean and, where possible, invisible to callers. Porting the highest volume customer numbers with the most care, and keeping a fallback such as temporary forwarding if a port slips, is how the entity avoids a public outage on its most visible numbers.
Behind the numbers sits the contact center platform, and it is more than a phone system. It holds the call flows that route a caller to the right team, the agent configuration, the recordings and quality data, and often integrations into the CRM so an agent sees the customer's history on screen. Inside the group this frequently ran on a shared platform serving several businesses, so the entity has to either stand up its own tenant on that platform or migrate to a new one, then rebuild the routing and integrations for the standalone business.
The call flows carry hidden complexity. Years of refinement go into how calls are routed by product, language, priority, and time of day, and that logic has to be reproduced rather than guessed at, because a routing gap sends callers to the wrong queue or a dead end. The buyer captures the existing flows in detail, rebuilds them on the entity's platform, and treats the routing as something to be tested exhaustively, since a flow that looks right on a diagram can still misroute real calls.
Historical data and integrations need deliberate handling too. Call recordings kept for compliance, interaction history, and the CRM screen pop all have to follow the entity or be accessible to it, and the platform's link to the customer record depends on the same clean data the rest of the separation relies on. This connects to the broader systems work, including the partner and customer records addressed in the master data management split.
The people and places that handle calls have to be ready alongside the platform. Agents need their accounts, their headsets, and their access on the new system, and they need to know how the new tools work before the first live call, so the buyer builds in agent setup and a short training window rather than expecting them to learn on the job while customers wait. An agent who cannot log in on Day One is as much an outage as a failed number.
The underlying network and carrier arrangements sit beneath it all. Contact center sites need the connectivity to carry voice reliably, the entity needs its own carrier contracts rather than riding on the seller's, and the call quality has to hold under real volume. These are the kind of arrangements that run on provider lead times, so the buyer starts the carrier and connectivity work early, in step with the rest of the standalone network, rather than discovering a capacity or contract gap close to Day One.
Sequencing keeps it coherent. The platform stands up, the agents are configured and trained, the network and carrier arrangements are in place, the routing is tested, and only then are the numbers ported into a system that is ready to answer them. Coordinating these dependent pieces so the cutover happens as one clean event, rather than a scramble of loose parts, is the kind of execution the TSA Exit Acceleration service runs.
The cutover is proven from the caller's side, not the engineer's. The buyer places real test calls to the published numbers and walks the routing as a customer would: dialling the main line, choosing the menu options, reaching each queue, and confirming an agent actually answers on the new platform. A configuration that looks complete can still drop a caller at the wrong menu or into a silent queue, and the only way to know is to call in and listen, which is exactly what a customer will do on Day One.
Volume and the hard cases get tested too. A single test call proves the path exists; the buyer also checks behaviour when calls queue, when an agent is busy, and at the volumes a real business day brings, because telephony problems often appear only under load. The agents run live calls in the new environment before Day One where possible, so the first real customer call is not also the first time the whole chain, number, routing, platform, and agent, has worked together.
Call center and telephony separation rewards the buyer that treats it as the customer touchpoint it is. Porting the numbers on the carrier's clock, rebuilding the platform and call flows, readying the agents and the network, and testing the cutover from the caller's seat lets the standalone entity answer every call from the first morning as if nothing changed. Treating telephony as a simple line move is how a carve-out's first impression on its own customers is a number that rings out unanswered.
It covers moving the entity's phone numbers, call routing, and contact-center platform off the seller's telephony onto its own, so that customers, employees, and partners reach the standalone business on Day One. It includes the published customer numbers, the contact-center software and its data, and the underlying carrier and network arrangements.
Often it can keep the numbers, but they have to be ported to the entity's own carrier and platform, which is a regulated process on the carrier's timeline. The numbers may also be registered to the seller, so porting requires the seller's cooperation and careful scheduling to avoid a window where calls fail.
Customers calling the published number and getting silence, a wrong company, or a dropped queue. Telephony is a direct customer touchpoint, so a botched cutover is immediately visible to the people the entity most needs to keep. The fix is careful number porting, tested routing, and a fallback if a port slips.
The entity needs its own contact-center platform, or its own tenant, with the call flows, agent setup, and historical interaction data it relies on. Inside the group this often ran on a shared platform, so the entity either stands up its own instance or migrates to a new one, and the routing and integrations are rebuilt for the standalone business.
Keeping customer and supplier documents flowing through Day One.
Read the article →The clean customer records the contact center reads from.
Read the article →Re-establishing the supplier connections behind operations.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
Stand up standalone IT before the TSA meter and the seller's dependencies compound against you.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →