How to write a Summary Resolution Communication without making the customer feel brushed off

Why can a quick complaint resolution still lead to an escalation?

A quick complaint resolution can still lead to an escalation when the customer doesn’t feel that the firm fully understood or investigated their concerns. Even where the review was reasonable, a brief explanation can leave the customer unclear about what was checked, why the decision was reached or whether their individual circumstances were properly considered.

Resolving a complaint within three business days can be brilliant customer service.

You’ve got a straightforward issue. You understand what’s gone wrong, the fix is clear, and the customer is happy with your response. There’s no sense in dragging the complaint through a longer process just for the sake of it.

Most customers want the issue understood, explained and sorted as quickly as possible.

The problem starts when your team turns a complaint around quickly, closes it through the Summary Resolution Communication (SRC) route and then receives a notification that the customer has gone to the Financial Ombudsman Service.

You may look at the file and struggle to understand why.

The complaint was reviewed. Your team reached a decision within three business days. The customer appeared to accept the response. The required communication was sent.

So what went wrong?

From the customer’s side, the complaint may feel as though it was closed before anyone properly investigated it.

Your response may tell them what you decided without showing what you understood, what you checked or why the information led to this outcome. Speed can then make the response feel rushed, even where your team carried out a reasonable review behind the scenes.

When the explanation is too thin, the time saved can quickly disappear through repeat contact, another review or a referral to FOS.

Giving the customer a little more clarity in the original correspondence can help prevent much more work later.

What is a Summary Resolution Communication?

A Summary Resolution Communication, usually shortened to SRC, is a written communication you send after resolving a complaint by close of business on the third business day following the day you received it.

For the complaint to be treated as resolved under this route, the customer must have indicated that they accept your response. Neither the response nor the customer’s acceptance has to be in writing, although your records should make it clear what was accepted and when.

An SRC isn’t the same as a standard final response letter.

It also isn’t a shortcut around properly investigating and assessing the complaint. Complaints resolved within three business days are still subject to the FCA’s wider complaint resolution rules.

The three business day route changes the communication process. It doesn’t lower the standard of complaint handling expected before you close the case.

When can you send a Summary Resolution Communication?

You can send an SRC when you’ve resolved the complaint by close of business on the third business day after the day it was received, and the customer has indicated acceptance of your response.

You can use this route for a complaint that you have:

• upheld

• partly upheld

• resolved through an explanation or practical action

• decided not to uphold, where the customer has still accepted your response

The final point needs care.

You may decide that you don’t agree with the customer’s complaint and still resolve it within three business days. The SRC route only applies, however, when the customer has indicated that they accept your response.

A calmer tone at the end of the call doesn’t necessarily mean the customer has accepted the complaint outcome. They might be happy with the practical fix while remaining unconvinced by your explanation, or simply ready to bring an uncomfortable conversation to an end.

Your complaint record should make clear what the customer accepted.

Reaching a decision within three business days doesn’t automatically mean the complaint has been resolved. If the customer is still unhappy and hasn’t accepted your response, you can’t close it using the Summary Resolution Communication route.

The complaint should remain open and continue through your usual complaint handling process. You should complete any further investigation needed and send the appropriate final response within the relevant DISP timeframe, including the required information about the customer’s right to refer the complaint to FOS.

Why do customers escalate a complaint after receiving a Summary Resolution Communication?

Customers often escalate a complaint after receiving an SRC because the speed, wording or limited explanation leaves them unconvinced that you properly understood or investigated the complaint.

Your decision may be right.

Your case handler may have checked the account, listened to a call, reviewed a document or spoken to another department. The difficulty is that the customer won’t know this unless your response shows enough of the work and reasoning behind the outcome.

Inside the business, you may be able to see:

• what was reviewed

• which records were checked

• what your case handler found

• why the complaint was upheld or rejected

• what action was offered

• what the customer said during the conversation

The customer may only receive a short letter saying that you reviewed the matter and now consider it resolved.

This creates a gap between the work your team completed and the explanation the customer received.

Your team thinks: “We dealt with this quickly and reached the right decision.”

The customer thinks: “You closed this in three days and haven’t shown me that you looked at it properly.”

Rather than assuming the customer is being unreasonable or has simply changed their mind, the more useful question is why their view changed. Once they’ve had time to think about the conversation, read the Summary Resolution Communication properly or discuss it with someone else, they may realise that they don’t fully understand the outcome or feel that important points haven’t been addressed. Often, the escalation comes back to communication rather than the decision itself.

This is why an SRC needs to do more than confirm that you’ve closed the case. If the complaint is later referred, FOS may ask you for the relevant records and evidence so it can understand what happened and assess whether the outcome was fair. Its guidance for businesses resolving complaints explains what firms should expect.

What must a Summary Resolution Communication include?

DISP 1.5.4 specifies the information that every Summary Resolution Communication must contain.

Your SRC must:

• refer to the customer’s complaint and state that you consider it resolved

• explain that the customer may be able to refer the complaint to FOS if they later become dissatisfied

• indicate whether your firm consents to waive the relevant FOS referral time limits, using the appropriate prescribed wording

• provide the FOS website address

• refer the customer to further information available from FOS

You should use your approved wording and internal compliance process to make sure these requirements are met.

This information should be clear, easy to understand, readily accessible and prominent within the communication.

What should a good Summary Resolution Communication explain?

A good SRC should explain what the firm understood the complaint to be, what it considered, why it reached its decision, the outcome and action agreed, and what the customer can do if they later remain unhappy.

Good complaint handling goes further than including the prescribed FCA wording.

The FCA complaint resolution rules require you to investigate complaints competently, diligently and impartially, assess them fairly, consistently and promptly, and explain your decision in a way that is fair, clear and not misleading.

Although DISP doesn’t prescribe a detailed account of the investigation within the SRC itself, a well-written communication should give the customer enough information to understand:

• what you believed the complaint was about

• what information you considered

• why you reached your decision

• whether you upheld, partly upheld or didn’t uphold the complaint

• what action you have or haven’t taken

• the complaint outcome and resolution agreed

• what the customer can do if they later remain unhappy

Your internal record should separately show what the customer accepted, how acceptance was obtained and when it happened.

This doesn’t mean turning every SRC into a long final response letter.

It means making the work behind your decision visible.

A concise response can still show that you properly understood and considered the complaint. A vague response can make a perfectly reasonable investigation look as though it never happened.

What should a Summary Resolution Communication explain when you don’t uphold the complaint?

When you don’t uphold the complaint, the SRC should clearly explain what you understood the customer’s concerns to be, what information you reviewed and why this led you to decide that the complaint shouldn’t be upheld. It should also make clear whether any action will still be taken and remind the customer what they can do if they remain unhappy.

You’ll usually need to put more thought into your SRC when you don’t agree with the customer.

When you uphold the complaint and give the customer the remedy they asked for, acceptance is often easier to understand. The customer can see what’s changed and why you consider the issue resolved.

A complaint you don’t uphold is different.

The customer has raised something they believe is wrong. You’ve looked at it quickly and reached a different view. Even if they accept your explanation during the conversation, the written communication still needs to make the reasoning clear enough for them to understand afterwards.

Where an apology is appropriate, it should acknowledge the customer’s experience rather than make their reaction sound like the problem.

There’s a big difference between:

“We’re sorry you feel this way.”

and:

“We’re sorry the delay left you feeling frustrated, and we understand why you asked us to look into what happened.”

The first can sound defensive and generic. It places the emphasis on the customer’s reaction rather than the experience that led to it.

The second acknowledges the effect on the customer without automatically accepting every part of the complaint.

You can apologise for the customer’s experience while still explaining why you haven’t agreed to the outcome they wanted.

We’ve written more about this in Why apologising to customers matters in complaint handling.

Your response should then explain the following.

What you understood

The customer should be able to recognise their complaint in your response. If they raised concerns about a delay, unclear information and the way someone spoke to them, your communication shouldn’t answer only the delay because this was the easiest part to check.

What you considered

You don’t need to list every internal step, but you should say enough for the customer to see that you reviewed the relevant information. This might include account records, call recordings, correspondence, policy terms, system notes or information provided by another party.

Why you reached your view

Your reasoning should connect directly to the customer’s complaint. Broad phrases such as “we followed our process” or “our records show no error” won’t always explain why you believe the outcome was fair. The customer needs to understand how the information led to your decision, even where they continue to disagree with it.

What you’ve done

Your SRC should make clear whether you’ve corrected an error, issued a refund, offered compensation or a goodwill payment, updated a record, explained why you aren’t taking further action, made a service improvement or agreed another practical next step.

What the customer accepted

Your internal record should show whether the customer accepted the practical resolution, your explanation, the complaint outcome, the redress offered or all parts of your response. This becomes particularly important if the customer later says they only agreed that you’d fixed the immediate problem.

The three business day route is designed to help you resolve straightforward complaints quickly. Your response doesn’t need to be long, but it should give the customer enough clarity to understand the outcome. This can reduce repeat contact, avoidable rework and the risk of a complaint being escalated because the customer didn’t feel the issue had been properly investigated.

When does an expression of dissatisfaction become an FCA complaint?

An expression of dissatisfaction generally becomes an FCA complaint when a customer communicates, orally or in writing, that they’re unhappy with the provision of, or failure to provide, a financial service and alleges that this has caused, or may cause, financial loss, material distress or material inconvenience. The words “I want to make a complaint” aren’t required, so the firm must consider the substance and context of what the customer is saying.

This is the first step in deciding whether the communication meets the FCA complaint definition, and it needs to happen before anyone starts thinking about an SRC.

Your complaint policy and internal compliance guidance should reflect the full definition and how it applies to your business.

In practice, your CX team will often hear the early signs first.

“I haven’t got time for this today.”

The customer may be annoyed, rushed or sharper in tone than usual. On its own, this doesn’t necessarily tell you that they’re making a complaint or are unhappy about your service or product.

“I’ve been waiting ages to get through, and I’ve now had to take another morning off work to sort this out.”

This is dissatisfaction with your service and describes a possible impact.

“The wording was so unclear that I didn’t understand I wasn’t covered, and I’m now facing a large bill.”

This describes dissatisfaction and a possible financial or material effect.

You need to consider the context. What happened? What is the customer unhappy about? How has it affected them, and what do they want you to do?

This distinction is important because your CX team often hears these comments before your complaint team becomes involved.

If one team hears frustration and tries to smooth it over quickly, while another would’ve recognised the same conversation as a complaint, you can end up with inconsistent complaint capture, weak records and unreliable complaint MI.

How should your CX and complaint teams manage complaints resolved within three business days?

Your CX and complaint teams should manage complaints resolved within three business days using the same complaint definition, acceptance standard, recording requirements, vulnerability prompts, handover criteria and root cause categories. This helps firms identify complaints consistently, keep reliable records and make sure a quick resolution doesn’t weaken oversight or customer protection.

A customer will often call, message or email because something has gone wrong, and your CX team quite rightly wants to sort it quickly.

In many cases, the customer just wants a fix they’re happy with, without being passed between departments or taken through a longer process.

The difficulty comes when separate teams or individual colleagues interpret your complaint rules differently.

One colleague may treat the contact as a customer service issue and walk the customer through the steps needed to resolve it. Another may recognise that the customer has expressed dissatisfaction, described an impact and should therefore have the matter recorded and handled as a complaint.

Your CX team may close the contact with a short CRM note. Your complaint team may later need to work out:

• what the customer said

• whether the issue met your complaint definition

• what was investigated

• what was offered

• whether vulnerability was considered

• what the customer accepted

• why an SRC was issued

By then, the colleague who had the conversation probably won’t remember the exact details.

The problem becomes harder to manage when CX and complaint information is stored in different places. The original contact may be held in a CRM, the complaint review in a spreadsheet, the customer’s acceptance in an email and the SRC in a shared folder.

Even where each person has completed their part, nobody has a reliable central record of the customer’s journey or the reason the complaint was closed. The complaint team may need to reconstruct what happened from several systems, messages and documents before it can check whether the complaint was recognised, investigated and resolved properly.

This weakens the handover between teams, makes quality checks slower and leaves complaint MI dependent on information being copied manually from one place to another.

Where a firm uses complaint management software, such as Complyr, the process can be much cleaner. The CX team can record the expression of dissatisfaction directly in the complaint system, including the original customer contact, the issue raised, any impact or vulnerability information and the action already taken.

The complaint team then receives the case with the original context intact, rather than relying on a short CRM note or asking someone to rekey the information later. The investigation, customer acceptance, SRC and root cause can all remain connected to the same complaint record.

Your CX team, complaint team, QA colleagues and compliance colleagues need an agreed approach with leadership oversight.

This should cover:

• how you recognise an expression of dissatisfaction

• how you apply the FCA complaint definition

• when an issue needs to move from a CX record into your complaint process

• who can decide that a complaint has been resolved

• how you confirm and record customer acceptance

• what must appear in an SRC

• when CX should hand the complaint over

• how complaints closed within three business days feed your MI

• how you record root causes

• what happens if the customer comes back

This isn’t about taking ownership away from CX.

It gives everyone the same working standard, so the customer gets a consistent response and you can rely on the complaint record later.

The same structure also protects your complaint reporting and MI, because complaints resolved quickly still need to feed a reliable view of customer dissatisfaction, root causes and outcomes.

How can vulnerability be missed during quick complaint resolution?

Vulnerability can be easier to miss during quick complaint resolution when the immediate focus is calming the conversation and fixing the practical issue.

Not every angry customer is vulnerable, and not every vulnerable customer will sound upset, confused or distressed.

Sometimes vulnerable needs show up as:

• impatience

• repeated contact

• a raised voice

• mistrust

• difficulty explaining the issue

• difficulty taking in information

• missed details

• a sudden change in behaviour

• agreeing quickly without appearing to have understood the explanation

Your CX team may have a lot going on. The customer is frustrated, calls are stacking up, and the colleague wants to find a solution.

They may resolve the practical issue while missing the support needed behind the frustration.

A customer who keeps repeating themselves may not be trying to be difficult. Your explanation may not have worked for them.

An angry customer may be under financial pressure, worried about the consequences of the issue or embarrassed that they’ve had to ask for help.

Someone who agrees with you very quickly may be overwhelmed and more interested in ending the conversation than understanding the outcome.

This is especially important when you send an SRC after a short telephone conversation. If your team didn’t consider the customer’s circumstances, the case note may make the closure look much cleaner than the conversation really was.

I’ve witnessed customers being given important information at such speed that they were never going to be able to process it properly. They agreed simply because they wanted the conversation to end, without fully understanding what had been explained or what they were accepting.

The aim isn’t to turn every complaint resolved within three business days into a lengthy investigation. But your team does need enough guidance to pause when the customer’s behaviour suggests there may be more going on than irritation.

Useful prompts include:

• Has the customer understood the explanation?

• Are they repeating the same concern because the explanation hasn’t worked for them?

• Have they mentioned financial pressure, bereavement, illness, stress, caring responsibilities or difficulty coping?

• Have they accepted the response clearly?

• Are they agreeing because they want the conversation to end?

• Does the complaint record show what support or communication adjustments were considered?

• Would another colleague understand why the case was closed?

We’ve covered this in more detail in our guide to embedding vulnerability into regulated complaint handling.

The key point is simple: someone who sounds angry or impatient shouldn’t automatically be labelled as difficult.

What prompt can help your team recognise vulnerability?

A simple prompt such as “What’s the customer really trying to tell you?” can help complaint teams pause, look beyond the immediate issue and consider whether the customer’s words, behaviour or circumstances indicate vulnerability or a need for additional support.

When I managed a team using manual processes, we noticed that the number of complaints categorised as involving vulnerability seemed low compared with the volume and types of cases we were handling.

We were also trying to contain a backlog and keep all the plates spinning, so there wasn’t always time to stop and reread lengthy guidance.

We introduced a simple screen saver prompt:

What’s the customer really trying to tell you?

It wasn’t fancy. It didn’t require a workshop, another policy document or a motivational poster that everyone stopped noticing after a week.

It helped because the question appeared at the point people were making decisions.

The same principle applies to complaints resolved within three business days.

If you expect your teams to recognise dissatisfaction, spot vulnerability, confirm acceptance, word an apology properly and capture useful MI, the prompts need to appear while they’re doing the work.

What are the common mistakes when closing complaints within three business days?

The most common mistakes are treating the deadline as the outcome, using boilerplate wording, giving a generic apology, recording customer acceptance too lightly, leaving the issue as a CX note, missing vulnerability, capturing weak MI, applying different standards across teams and failing to show the investigation in the communication.

Most of these problems start with good intentions.

Your teams are trying to help quickly while dealing with queues, call pressure, targets and customers who want answers now. The risk is that the immediate issue is fixed, but the customer or your business is left with another problem afterwards.

Treating the deadline as the outcome

Closing a complaint within three business days can be a positive result, but the timeframe should be the result of good complaint handling rather than the main reason for closing the case.

The complaint still needs to be understood, investigated and resolved, and the customer must have accepted your response.

Using boilerplate wording

Approved wording helps teams stay consistent, but it still needs to reflect the customer’s complaint and the checks you completed.

A generic response can miss the specific reason the complaint arose, lack empathy and leave the customer feeling that nobody properly read or investigated their concerns. Explaining the usual policy or process isn’t enough if you don’t also show how it applied to their individual case.

Giving a generic apology

Phrases such as “we’re sorry you feel this way” can make the customer’s reaction sound like the problem.

Where an apology is appropriate, it should acknowledge what the customer experienced and the effect this had on them, without accepting fault where your investigation doesn’t support this.

Recording acceptance too lightly

A customer becoming calmer or ending the call politely isn’t the same as clearly accepting your response.

Your record should show what they accepted, how you confirmed this and when acceptance was obtained.

Leaving the issue as a CX note

A quick service fix may still need to be recorded as a complaint.

If the issue remains as a short CRM note, the business can lose the complaint record, root cause and MI needed to identify whether the same problem is affecting other customers.

Missing vulnerability behind anger

A customer who sounds angry, impatient or difficult may need more time, a clearer explanation or a different communication approach.

Resolving the practical issue doesn’t always mean they understood or accepted the outcome.

Capturing weak MI

Broad categories such as “service issue” or “admin error” aren’t enough. They describe the symptom, but they don’t show what failed, why it happened or whether the same issue is affecting other customers.

When people are busy, it’s easier to choose a broad category and move on than to stop and think about where the root cause really sits. The data may look complete, but it gives leaders very little to act on.

Complaints resolved within three business days can still reveal communication failures, repeated handover problems, avoidable delays and gaps in the customer journey. FCA rules require firms to analyse complaints to identify root causes and recurring or systemic problems, so complaint categories need to show more than the surface issue.

Applying different standards across teams

Similar complaints can be handled differently depending on whether the customer speaks to CX or the complaint team first.

Shared definitions, recording standards and handover rules help prevent the route into the business from determining how the complaint is treated.

Failing to show the investigation in the communication

Your team may have completed the right checks, but the customer won’t know this unless the SRC explains enough of the investigation and reasoning.

A brief response can still be clear. A vague response can make a reasonable review look as though it never happened.

What does good complaint resolution within three business days look like?

Good three business day complaint resolution gives your team enough structure to reach a fair, consistent decision supported by clear evidence without dragging a straightforward issue through a longer process.

The customer should feel that you’ve understood what happened, checked the right information and explained the outcome clearly. Your business should also be left with a complaint record that shows why the case was closed and what the customer accepted.

A good closure usually has the following controls in place.

You’ve recognised and recorded the complaint properly

Your colleague understands whether the customer is generally frustrated or has expressed dissatisfaction that meets the applicable complaint definition.

This shouldn’t depend on the customer using the word “complaint”. The context, the impact on the customer and what they’re asking you to do all help determine how the issue should be handled.

Recognising the complaint properly at the start makes it much easier to apply the right process, capture the right information and avoid gaps later.

You’ve checked the relevant information

Your colleague has reviewed enough information to understand what happened and reach a fair decision.

This could include account records, correspondence, call recordings, system notes, policy terms or information held by another team or third party.

Quick resolution still requires a competent and diligent investigation. The fact that a complaint is straightforward shouldn’t mean the review is light. It should mean the relevant facts can be established without unnecessary delay.

You’ve considered vulnerability and support needs

Your colleague has considered whether the customer needed more time, clearer information, another communication format or additional support.

This doesn’t need to make the process longer or more complicated. It means pausing long enough to recognise when the standard approach may not be working for the person in front of you.

Any support offered, communication adjustment or relevant vulnerability indicator should be recorded clearly so the file reflects the full conversation.

The conversation doesn’t feel rushed

The customer has enough time to explain the issue, hear your response, ask questions and say whether they accept the outcome.

A confident conversation can still feel calm and considered. The customer shouldn’t come away feeling that the main aim was to close the call quickly.

This is especially important where the complaint isn’t upheld or is only partly upheld, because the customer may need more explanation before they feel comfortable accepting the response.

Acceptance is clear

Your complaint record shows what the customer accepted, when they accepted it and how you confirmed this.

This should be specific enough to distinguish between accepting a practical fix and accepting the full complaint outcome.

If the customer later comes back, your team should be able to see whether they agreed with the explanation, the redress, the action taken or simply that the immediate issue had been resolved.

The Summary Resolution Communication explains enough

Your response shows what you understood, what you considered and why you reached your view.

It doesn’t need to become a full final response, but it should give the customer confidence that you didn’t rush the decision.

A useful test is whether someone who wasn’t involved in the original conversation could read the SRC and understand the complaint, the checks completed and the reason for the outcome.

Where an apology is appropriate, it should acknowledge the customer’s experience without making their reaction sound like the problem.

The case record and MI remain useful

Your complaint manager, QA reviewer, compliance colleague or a FOS caseworker shouldn’t have to reconstruct what happened from a brief CRM note.

The record should show the issue raised, what was checked, the reasoning behind the decision, what was offered and what the customer accepted.

The complaint should also be categorised in a way that helps you understand what caused the dissatisfaction and whether the issue may be repeated elsewhere.

Complaints resolved within three business days can still reveal communication problems, unclear journeys, training gaps, customer effort, handover failures or repeated operational issues.

Good early resolution should feel simple to the customer and controlled by your business. The case has been handled quickly for the right reasons, the customer understands the outcome and the record gives you enough confidence to stand behind the decision later.

How can you build quick and fair resolution into your complaint process?

Three-business-day complaint resolution works best when you build the required controls into the way your teams handle the case.

Your colleagues often need to make decisions while the customer is waiting. They may not have time to search through policy documents, separate guidance notes and saved templates.

Complaint handling also involves judgement. Two customers can describe similar events but need different handling depending on the effect, context, evidence, expectations, vulnerability indicators and proposed resolution.

A manual process can work, but busy teams may find it harder to apply every step consistently.

Your process can start to depend on memory, judgement, saved templates, sticky notes and whoever picks up the case first.

Useful manual controls could include:

• a shared complaint identification decision tree

• agreed examples of customer acceptance

• approved SRC wording

• vulnerability prompts

• clear handover triggers between CX and complaint teams

• required complaint note fields

• defined MI and root cause categories

• QA sampling of complaints resolved within three business days

These controls need to be visible at the point your team makes the decision.

This links closely to the 5 Cs of complaint handling, because quick resolution still depends on capturing the right information, communicating clearly, considering the customer’s circumstances, closing the complaint properly and using what you learn afterwards.

Complaint case management software can make this easier when configurable complaint workflows build prompts, recording standards and handover points into the way your team already works.

A complaint case management system can help you:

• capture the complaint consistently

• calculate and track the three business day deadline

• record what was investigated

• confirm how acceptance was obtained

• prompt for vulnerability considerations

• generate approved correspondence

• retain the SRC with the case history

• capture root cause and MI data

• show why the complaint was considered resolved

• keep a clear, complete record if the customer later goes to FOS

The aim is a prompt resolution for the customer, a controlled process for the business and a clear record for anyone reviewing the complaint later.