Customer service provider transition · UK
Switching your customer service provider
A short guide on making the switch to a new outsourcing partner as pain-free as possible
The phones don’t stop ringing just because you decide to change your outsourcing partner. Switching providers requires careful change management and coordination of internal stakeholders. Here are the things to look out for, from what to record beforehand to what to check after go-live. Choosing a provider and negotiating the new contract aren’t covered here.
Trusted by clients worldwide
30,000+
vetted freelancers
40+
languages
100+
operations experts
150+
clients worldwide
What to record and check before the switch
The first step is agreeing what will move, what needs to improve and what could delay the handover.
What the team handles
List the channels, languages and systems in scope, alongside opening hours, volumes and peaks. Include work that needs help from your specialists.
What needs to improve
Record waiting times, backlog and quality measures. Agree which problems the switch should solve and how you will judge progress.
What can delay the move
It’s worth checking notice periods, handover obligations and access to records, and confirming what the outgoing provider will finish.
Agree one handover brief with both providers before you set the final date. It should include callbacks, complaints, refunds and cases waiting on another department.
A provider change can fall under TUPE. Ask HR to check before confirming the staffing plan.
When TUPE may apply · Acas guidance
A change of service provider can fall under TUPE, the UK rules protecting employees when work transfers. Acas identifies conditions including a UK-based organised group of employees, the same client and work that stays mainly the same. Ask HR or an employment adviser to assess the arrangement before confirming the staffing plan.
Who is responsible for what
It helps to have one transition lead with direct contacts at both providers. Each unresolved task also needs an owner and a due date.
Customer service
Responsible for the policies, open cases, customer promises and what the new team is allowed to decide.
IT and systems
Responsible for access, integrations and contact routing, including the ability to restore a route.
Commercial, privacy and HR
Responsible for exit arrangements, the transfer of records, approvals and any staffing questions.
Agree who can approve or pause the switch, and put their name, contact details, deputy and availability in the shared plan. Separately, agree who runs the ongoing service and holds the SLA.
Handing over open cases and records
An agent taking over an open case needs its history, the outstanding promise, a next action and a named owner.
- Keep the history. Transfer the case ID, contact details, channel, notes, attachments and previous decisions together.
- Check the transfer. Compare case totals and statuses in both systems. Check sample records and capture updates made after the first export.
- Confirm ownership. Record the next action, deadline and receiving owner. Get acknowledgement before responsibility changes; agree where follow-up contacts will go.
Illustrative case · REF-024 · no customer data
Refund awaiting confirmation
History
Refund approved; payment confirmation outstanding.
Promise
Update the customer by 16:00 UK time.
Next action
Check payment status and contact the customer.
Owner
Named incoming billing handler; escalate to the client’s finance contact.
You’ll need to agree secure transfer, access and data return or deletion with your privacy team before records move.
UK data return and deletion requirements
Where your business is the data controller and the supplier processes personal data on your behalf, the processing contract must provide for its return or deletion at your choice when those services end. Existing copies must also be deleted unless domestic law requires storage. Put the decision, transfer method, retained records and removal of old access into the handover plan; have your privacy team confirm the arrangements.
UK GDPR, Article 28(3)(g) ↗ · ICO: end-of-contract provisions ↗
Test the new team before going live
Base the tests on realistic customer tasks in the systems the new team will work in.
A routine enquiry
Find the approved policy and complete the normal action.
An exception or complaint
Recognise the decision limit and reach the right specialist.
An existing open case
Find the history, follow up the outstanding promise and update the record.
The full contact route
Check phone and message routing, permissions, attachments, case updates and reporting.
When a test fails, record it, assign a fix and repeat the affected tests. Keep one approved version of policies, scripts and templates, with someone responsible for updates.
Checklist: transfer work once you’re sure the team is ready
Use this at the go-live review. Record who checked each item and what they tested.
Tick off each check as you review it. Selections are not saved.
Cases and contacts
Team and cover
Systems and approval
Switch and follow-up
Pause the affected transfer if an essential check fails. Resolve missing access, failed routing or unowned work before it moves.
Timing, staged transfers and UK bank holidays
Where the work can be separated, you may want to move one queue at a time. Shared routing or systems may need one coordinated switch. Follow the agreed order, capture cases changed during the move and check the first live contacts.
GOV.UK publishes different bank-holiday calendars for England and Wales, Scotland and Northern Ireland. Confirm which customer regions the service covers, then agree the rota and who will be available for escalations on those dates.
Have a backup ready
It’s worth agreeing in advance when to pause the move, who will take incoming work and how they will access the records.
- Set the trigger. Agree the response to failed routing, an unavailable system or urgent cases without an owner.
- Confirm the cover. Check what the outgoing provider, an authorised internal team or another agreed team can actually take on, with the route and access they need.
- Keep records together. Track work and customer promises created while backup cover is in use.
- Retest before restarting. Check the affected route and confirm who owns each case and next action.
Do not assume the old provider can take the work back. Their people or access may no longer be available. Walk through the backup plan with everyone involved.
UK government sourcing guidance for the public sector recommends linking the outgoing exit and incoming start plans.
What the Sourcing Playbook recommends
The UK government’s Sourcing Playbook recommends an exit plan that links the outgoing supplier’s exit with the incoming supplier’s mobilisation. Its plan contents include milestones, responsibilities, shared risks, dependencies and assets, plus time for knowledge transfer. This is public-sector sourcing guidance, rather than a universal rule for private contracts; the same planning questions are useful when you build your own handover.
What to monitor after go-live
Your pre-switch baseline is the yardstick for the new service. Tracking new enquiries and transferred cases separately stops a healthy new queue hiding an old backlog.
Check
Action
Contacts arriving
Check: Missed calls or messages, wrong queues and failed routes.
Action: Check routing and access; use the agreed backup if the route cannot serve customers.
Customer promises
Check: Overdue updates, callbacks, refunds and unowned cases.
Action: Assign the next action and contact the customer where needed.
Service levels
Check: Waiting times, abandoned contacts and backlog age against the baseline and agreed targets.
Action: Review staffing, demand and queues. Compare similar hours and days, allowing for peaks and bank holidays.
Resolution and quality
Check: Repeat contacts, complaints, quality findings and customer satisfaction where measured.
Action: Review the cases behind the figures. Fix knowledge or process gaps, coach where needed and test the change.
Each issue needs an owner and a review date. Agree when to return to normal reporting, close remaining handover tasks and remove old access.
FAQs
How long does switching a customer service provider take?
Timing depends on the work, systems and exit arrangements. Standard yoummday projects can go live in up to 14 days; a complex provider transfer needs its own agreed timetable.
Should the backlog move with the new work?
It depends on case type, skills and access. Either way, agree what each team will finish, name the next owner, action and deadline, and confirm where follow-up contacts will go.
Can we keep our current CRM or ticketing system?
yoummday’s platform can integrate with existing systems. It’s worth agreeing the configuration with your system owners, then testing that the team can read histories, use attachments, take action and update cases.
Who runs the service after the switch?
With Managed Service, yoummday runs the operation and holds the SLA. With Enabled Service, your team runs the operation and holds the SLA, supported by yoummday’s platform, Talent acquisition and a dedicated Customer Success Manager. Agree separately who approves the switch.
What should customers be told about the switch?
Customers mainly need to hear about changes they have to act on, such as a new contact route or different opening hours. Keep existing promises visible. Agree the wording and timing with the people responsible for the service and customer data.
What data protection checks should we complete?
Before records move, confirm how they will be transferred, who can access them, what will be kept and when old access ends. Where data is processed on your behalf, agree the required return or deletion arrangements. See the data requirements in the handover section and ask your privacy team to confirm the project arrangements.
Planning a switch to yoummday?
If you’d like to talk it through, tell us about your current service, the work you want to move and your target date. We’ll discuss the team, systems and handover for the move.
Prefer email? [email protected]