What is One Touch Switching?
One Touch Switching is the gaining-provider-led process for UK residential fixed broadband and landline switching. The customer starts with the new provider, called the gaining provider. The existing supplier of the customer's service is the losing provider. These providers need to exchange the right information and coordinate the change while retaining responsibility for their own services and customer relationships.
A new broadband business needs a way to identify the existing customer service, handle switching messages, arrange the replacement connection and keep the customer informed. Account and billing records must also be reviewed at the appropriate stages. This page explains the switching journey and the role of the systems used to coordinate it.
In a simple journey, the customer orders from a new provider, which supplies information to identify the existing account. A matching response helps the process move forward. The providers then manage the required messages and service arrangements, while the gaining provider coordinates delivery and customer updates. The account handover and relevant charges still need attention after the initial match.
Switching software and broadband provisioning perform different jobs. Switching coordinates provider information and progress; provisioning establishes the replacement service. A successful match does not install a connection or prove it is ready. The UK switching guide provides background on the process, while the service delivery plan must account for the actual supplier order and any installation dependencies.
How One Touch Switch works for broadband providers
Matching means using customer and service details to identify the intended existing account. Accurate names, addresses and service information matter, particularly where a customer has several connections. If the details do not produce a usable result, staff need to inspect the response and establish which information should be checked before continuing.
Customer onboarding should keep the switch reference associated with the new account and replacement order. Onboarding is the work of creating the customer record, agreeing the offer and collecting the information needed to deliver it. Avoid leaving the switch in an isolated spreadsheet when sales, provisioning and support all need to understand its progress.
Assign an owner to responses and exceptions. For example, an address difference may require checking customer information, while a delivery delay belongs to the new service-order workflow. Both affect the customer, but they are not the same problem. Keep the latest response and outstanding action visible so another colleague can take over without repeating the investigation.
The ISP operations guide explains the account and service responsibilities behind those handovers. Before launch, test a straightforward match, an unsuccessful match and a service order that needs follow-up. Staff should understand how each affects the next customer update rather than assuming one successful message completes the whole switch.
TOTSCo integration for gaining and losing providers
The One Touch Switching Company (TOTSCo) operates the messaging hub through which participating providers exchange switching information. The hub coordinates messages; it does not supply the customer's broadband connection. Providers need the appropriate identifiers, credentials and operating arrangements for their chosen connection route.
An Application Programming Interface (API) is a defined way for systems to send requests and receive responses. A TOTSCo integration uses the relevant interfaces and message processes to exchange switching information. A correlation reference is an identifier that ties a response to its request, helping staff trace the case even when several messages concern the same customer.
Assess gaining and losing workflows separately. The gaining provider needs to coordinate the incoming customer and new service; the losing provider needs to respond using its existing account and service records. Establish which system creates each message, where responses are reviewed and who investigates an unexpected result. Check the current process documentation and onboarding requirements for the intended arrangement.
When comparing integration software, ask for a traceable example from request to response and follow-up. A connection to the hub is only one part of an operational setup. Business-switching requirements are separate from the residential process described here and need their own review; the same integration label should not be taken as evidence that every switching journey is covered.
Managing One Touch Switching progress and customer updates
Useful progress tracking answers three questions: what has been received, what does it mean and who acts next? Retain message references and the latest response with the customer account. The operational notifications guide explains how context and ownership make exceptions manageable rather than merely adding another alert to a queue.
Customer communications should reflect both switch progress and replacement-service readiness. A customer may speak to sales, support and billing about the same move, so colleagues need the previous messages and agreed next steps. The customer communications guide covers that shared history. Avoid promising completion solely from a matching result or a requested installation date.
Billing and payments form another handover. Review the service evidence and commercial agreement when checking the new subscription or ending arrangements. A switching message does not automatically settle every final charge, refund or partial-period adjustment. Match receipts to amounts owed and keep charge disputes separate from failed collections.
For example, a customer may ask whether the new package has started while staff are still investigating a provider response. The answer requires checking delivery and the account record, not guessing from the number of messages exchanged. When choosing One Touch Switch software, demonstrate matching, an exception, the service handover and a customer enquiry so the workflow can be assessed as a whole.
How Axiom supports One Touch Switching
Axiom retains supported switching requests, responses and progress in the wider customer account workflow. Its configured TOTSCo integration handles gaining-provider requests and losing-provider matching and lifecycle responses. Letterbox messages, correlation references and feedback provide a traceable relationship between a request and the response staff need to review. This gives the team concrete records for investigation rather than relying on the customer's name or a separate list of cases.
Customer, service, communication and financial records provide context for coordinating the replacement connection and account handover. The integration does not itself establish that broadband installation has completed or determine every billing adjustment. Live workflows depend on the configured provider credentials, identifiers and service arrangements, and the described residential scope should not be taken as a claim of separate business-switching support or certification.
For an unsuccessful match, the retained request and provider feedback help staff identify which case needs investigation. Account communications provide context for checking details with the customer before deciding the next action.
Operational Intelligence adds recorded switching events, account notifications and communication history to help staff prioritise cases needing attention. Detailed provider responses and service records remain the evidence used to decide the next action. Bring a gaining-provider journey, a losing-provider response and an unsuccessful-match example to a demo, together with the intended customer and billing handovers. This tests how the supported workflows fit the operation and identifies which supplier, configuration and staff responsibilities must be agreed before launch.