The customer journey does not stop at the hand-off

Somewhere in the UK this morning, a customer finished a difficult call about their debts. They were told, “we’ll pass this over to the creditor” or “our partner will be in touch”, and then they started waiting. They do not know, and should not need to know, that “passing it over” may mean a CSV dropped on an SFTP server, an email sent to a shared mailbox and a note added to a CRM the other organisation will never see. What matters to the customer is simple: the next person knows what is happening, the promised action gets done and they are not asked to start again.

That sounds obvious. Operationally, it is anything but. I have spent most of my career around regulated customer journeys, including debt advice, debt management plans and IVAs. These journeys only work when several teams, systems and partner organisations each do their part. The hand-off is where many of the most avoidable problems live. Context gets squeezed into a few fields. Ownership goes quiet. Everyone involved can show they completed their piece while the customer is still waiting. That is why I have stopped treating partner collaboration as a back-office integration problem. It is part of the customer experience, and it deserves to be designed and measured like one.

The gap sits between the systems

Most organisations can tell you a great deal about work while it sits inside their own walls: when the case opened, which queue it entered, which colleague handled it and when the task closed. Cross an organisational boundary and the picture degrades quickly. A referral is exported. An email goes to a shared mailbox. A spreadsheet is uploaded on Friday afternoon because it has always been uploaded on Friday afternoon. A status comes back days later, sometimes in a different format and usually without enough detail to understand what happened. When something stalls, the first task is rarely fixing it. The first task is working out who owns it.

The sector I work in makes this particularly visible. An adviser agrees a plan with a customer and needs a creditor to confirm balances, hold interest or accept an offer. The creditor may sell the account to a debt purchaser part-way through, which can send much of that conversation back to the start. An IVA referral passes from an advice provider to an insolvency practitioner. A Breathing Space notification may land with a dozen creditors at once, each of whom must identify the debt and apply the required protections inside its own systems. Every one of those steps crosses a boundary. At every boundary, each system can be operating exactly as designed while the customer’s journey quietly breaks.

The failure I see most often is not that a partner has done nothing. It is that the organisations involved are using different definitions of “done”. One has sent the work. Another has received a file. A third is waiting for missing information. Each local measure looks reasonable, yet nobody holds a reliable view of the end-to-end commitment made to the customer. That is the hand-off gap: activity is recorded, but shared responsibility is not.

Email is a communication tool, not an operating model

Email and spreadsheets persist because they are flexible, familiar and cheap. They are also remarkably good at hiding operational weakness. An inbox can prove a message was sent. It creates no structured ownership of the next action. A spreadsheet can move five hundred records in a minute, but it cannot tell you which version is authoritative, who changed a status, whether an exception was ever resolved or what the customer was told in the meantime.

Teams compensate, and they often compensate brilliantly. There are reconciliation exercises, shared mailboxes with colour-coded categories and a tracker that lives on one person’s desktop. There is always a colleague who knows exactly which contact at which creditor to chase when something goes missing. I have real respect for those people. I have also seen what happens to an operation in the week they are on leave. If a process depends on somebody noticing that yesterday’s return file contained 498 responses to 500 requests, the control is not the spreadsheet. The control is the person who spotted the missing two. Good people will bridge poor systems for a surprisingly long time. That does not make the systems safe. It makes the weakness harder to see.

Consumer Duty makes the boundary harder to ignore

The regulatory direction is not subtle. The FCA’s Consumer Duty is concerned with good outcomes across the distribution chain, not just within the slice of the journey one firm happens to operate. The FCA and ICO’s joint statement on vulnerability-related data, published in March 2026 and updated in July 2026, says manufacturers and distributors should work collaboratively and share relevant information where that is necessary to deliver good outcomes. It also recognises that, in some circumstances, an individual customer’s needs may have to pass between partners so appropriate support can continue.

None of that makes every firm responsible for every action of every other firm. It certainly does not licence moving unrestricted customer data around a partner network. What it does is close off a familiar excuse. An organisational boundary is no longer a reason to have no reliable view of a customer outcome that depends on the chain working as intended.

The FCA’s own work on vulnerable customers found gaps in data from distributors and third parties that limited firms’ understanding of outcomes across the chain. It also found that firms monitored third-party interactions less systematically than in-house work. Read that as a technologist and it is not a request for another dashboard. It is a requirement for traceability.

A controlled hand-off should answer five questions

Whenever work passes between organisations, the shared process should be able to answer five straightforward questions.

1. What has been handed over? The work item, required information and expected action should be explicit, with both parties working from the same reference. A file called “March referrals v2 FINAL” and an email subject line are not a shared understanding.
2. Who owns the next action? Ownership should move deliberately, not vanish somewhere between an outbound queue and an inbound mailbox. If an item is rejected or cannot progress, responsibility for resolving the exception needs to be just as clear as responsibility for the happy path.
3. What does completion mean? “Sent”, “received”, “opened” and “completed” are different states. In this sector, “creditor contacted” is not the same as “interest frozen”, and “referral made” is not the same as “advice given”. The agreed outcome should be defined in operational terms that both organisations use consistently.
4. What does the customer need while the work is moving? A customer may need an update, a different contact channel, extra time or continuity of support needs they have already disclosed. They should not have to repeat those needs simply because a different organisation now owns the task.
5. Can the journey be reconstructed afterwards? There should be an auditable history of allocation, access, status changes, exceptions and completion. When a complaint arrives or a case is escalated, the answer should not depend on assembling four inboxes and asking colleagues what they remember.

These questions are deliberately unglamorous. If the technology cannot answer them, adding more automation will simply move unclear work around faster.

Share what is needed, not everything available

Better continuity does not mean creating a shared pool of unrestricted customer data. The FCA and ICO statement is genuinely useful here. It describes data protection law as an enabler of responsible data sharing, while reinforcing purpose limitation, accuracy, minimisation, transparency and security. In practice, organisations need to know why information is being shared, whether it is necessary, who can see it, how long it will be kept and what the customer has been told.

This matters most where the information touches health, vulnerability or other sensitive circumstances. The receiving partner may need to know the support requirement without needing the customer’s full history. “Please communicate in writing and allow additional time” may be operationally necessary. The medical detail behind that request may not be. Good partner technology should make that distinction the easy option. Access should follow roles and permissions. Required fields should relate to the purpose of the hand-off. Changes should be recorded, and access removed when a user or partner no longer needs it.

Data minimisation is sometimes presented as the reason systems cannot share useful context. I see it the other way round: it is the design requirement that forces us to share the right context deliberately.

A notification is not accountability

One of the easiest mistakes in workflow design is confusing telling somebody with making sure something happens. Notifications have their place. They can tell a partner that work is waiting or alert a team to an exception. But a notification without a visible queue, an owner, an expected action and an escalation route is just another message competing for attention in an inbox that already holds several hundred. The control is the state of the work item, not the number of emails generated about it.

This is why I prefer shared queues and explicit statuses to chains of free-text updates. They create a common operating language and make the exceptions visible: unallocated work, rejected records, overdue actions, incomplete responses and changes awaiting review. The objective is not to remove conversation between partners. It is to stop the operation depending on that conversation being remembered and manually translated back into several systems.

Measure the customer outcome, not just partner throughput

Partner performance is usually measured through volumes and turnaround times. Those numbers matter, but they are not the outcome. A fast hand-off can still be a poor one if the information is incomplete. A case can close within target while the customer receives conflicting letters from two organisations. A partner can clear its queue by rejecting work that then sits unresolved somewhere else. That may satisfy a local measure, but it is practically useless to the customer.

Alongside throughput, I want the measures that expose friction across the chain: how often work is returned, how many items need manual reconciliation, whether customers are repeating information, whether promised actions were completed, how long exceptions sit unowned and whether different customer groups experience different results. That changes the conversation with partners. Instead of asking only, “did you meet the target?”, both organisations can ask what happened to the customer, where the journey weakened and what they should change together. Shared evidence is a much healthier basis for a partnership than periodic blame.

A partner portal should be an operating system, not a file drop

This thinking sits behind Partner Connect at WellTech-UK. We designed it as a secure, UK-hosted workspace where debt-advice providers and creditor organisations can allocate work, manage shared queues, exchange bulk data, govern user access and keep a complete audit history. The point was never to digitise the existing file-transfer routine. It was to make the state, ownership and history of partner work visible to the people responsible for it.

The distinction matters. A portal that only uploads and downloads files may be more secure than email, but the operation has barely improved. The value comes from connecting the transfer to allocation, notification, access control, exception handling and completion.

Partner Connect also sits within a wider view of customer outcomes. ScoreCoach examines evidence across customer interactions. InsolVatrack brings structure to casework. Partner Connect preserves control when the next action sits outside your own organisation. The products do different jobs, but the principle is the same: the customer journey should remain understandable and accountable from end to end.

My test for partner technology: If a customer asked, “what happened after you passed my case to your partner?”, could both organisations give the same answer from the same evidence? If the honest response starts with checking a mailbox, hunting for the latest spreadsheet or asking who normally deals with that partner, the process is still relying on people to compensate for missing control.

The customer journey does not stop at the hand-off. The technology, accountability and evidence should not stop there either.