MELLORCATalk to Mellorca
Patterns

Customer Experience & Onboarding

The Hidden Cost of Asking Customers for the Same Information Twice

When sales, accounts and support each ask the customer for the same details, the customer notices a business that does not share what it knows. Here is the cost and how to stop it.

Mellorca Patterns2026-10-08

Observable condition

A customer fills in an online form with their company name, VAT number, delivery address and contact person. Two days later a different person from the same business phones to ask for the delivery address. A week after that, the accounts team emails to request the VAT number so they can raise an invoice. When the customer reports a fault, the support agent asks for the company name and the contact details before doing anything else.

The customer's patience wears thin, and it shows. "I already gave this to your sales rep" appears in emails and on calls. Some customers become curt. Others begin to send everything in a single reply with the subject line "Details, again".

An illustrative example: a Johannesburg training provider with about forty staff collects delegate details when a company books a course, again at invoicing, again for the certificate, and again when the venue asks for dietary needs. Each team has a legitimate reason and its own form. The customer sees four requests for overlapping information from the same business in three weeks.

Realisation

Asking twice does not feel like a decision. It is the result of each team doing its job with the tools it has. But from the customer's side, there is only one business. When they are asked for the same detail repeatedly, they conclude that the left hand does not know what the right hand is doing, and they draw conclusions about how the rest of the work will be handled.

There is also a duty here. South Africa's Protection of Personal Information Act requires that a responsible party take reasonably practicable steps to ensure personal information is complete, accurate, not misleading and updated where necessary. Section 16 of the Act sets out that principle of information quality. Collecting the same detail in several places and keeping it in several versions makes that harder to meet: which copy is the current one when the customer moves, changes their contact person or closes an account?

Realisation prompt: take one customer you onboarded recently. How many times were they asked for their address or contact person between the first enquiry and the first invoice?

Identification

This is a pattern of repeated information requests. The visible symptom is customer irritation and slower onboarding. The common assumption is that staff are disorganised or that customers should simply keep their details to hand. The structural cause is that each team captures information in its own tool for its own purpose, and there is no shared record that later teams can read before they ask.

The Pattern the hidden cost of re-entering the same information covers the internal side, the staff time spent typing the same data several times. This Pattern concentrates on the customer-facing side: what repeated requests cost in trust, goodwill and speed. The Impact page the pain of customers repeating information across disconnected records gives a financial view of the same condition.

Diagnosis

  • Each team has its own form. Sales, accounts, logistics and support each built a way to collect what they need, and none refers to the others.
  • No single customer record. Details live in the CRM, the accounting package, the service desk and a few spreadsheets. IBM's description of master data management explains why a single, consistent version of core business entities matters when many systems use the same information.
  • Staff cannot see what is already known. Even when the data exists, the person asking may lack access or may not know where to look, so asking the customer is quicker.
  • Handover loses the file. The salesperson holds the answers in email and notes. When the account moves to onboarding, the context does not travel.
  • Verification is mixed with collection. Teams re-ask not because they have no data but because they cannot tell if it is correct, particularly when old records are untrusted. This feeds a cycle where more asking produces more versions.
  • Forms are inherited. A field on the booking form might exist because of a problem three years ago, and nobody has checked whether the information is already held elsewhere.

Commercial impact

The commercial value at stake is customer experience, onboarding speed, retention and data quality.

Repetition erodes confidence early, when the customer is deciding how much to trust the business with. It also delays work: if an invoice cannot be raised until the VAT number arrives, then cash arrives later. A delivery that waits on a confirmed address misses its slot. Every wait is a cost, and the customer pays part of it in time.

The effect on service is subtler. Customers who feel they are doing the business's administration are less likely to bother with small complaints and more likely to leave quietly at renewal. The idea of failure demand, described on the Beyond Command and Control site as demand caused by failing to do something right for the customer, fits well: each repeated request is work created by an earlier gap.

Inconsistent records add risk. When a customer corrects their details in one place, the older versions elsewhere stay wrong. Invoices go to the old address, statements reach the former accountant and marketing messages to a person who has left the customer's business. The Pattern when sales, finance and support disagree about the same customer shows how this affects daily work.

Common misidentification

One response is to put every question on a single, very long form at the start. That raises abandonment, and it cannot anticipate what later teams will need. Another is to tell staff to "check before you ask", which fails when there is no place to check. A third is to buy a new CRM and expect it to solve the problem; unless other tools read and write the same record, the new system becomes one more place where details are kept.

It is also tempting to treat the repetition as a minor courtesy issue. Customers rarely complain about it directly, which makes it easy to underestimate. The complaint shows up later as slow payment, lukewarm reviews or a lost renewal.

Possibility

In a better state, the customer provides each piece of information once, at the most natural moment. It is stored against one customer record that every team can read. Later teams ask only for what is genuinely new, and they confirm rather than collect: "We have your delivery address as 12 Main Road. Is that still right?" Changes made in one place flow to the others, or are made at a single source that the others read.

Microsoft's documentation on data unification in Customer Insights describes this idea in tooling terms: bringing customer data from several sources together into a single profile. The principle also works at a modest scale, with a shared spreadsheet or a lightweight CRM, as long as everyone uses the same record and agrees which fields belong where.

Intervention

  1. List every request. Collect all forms, templates and scripts that ask customers for information, and note the fields on each.
  2. Find the overlaps. Mark the fields that appear more than once. Typical ones are legal name, contact person, address, VAT or registration number and payment terms.
  3. Choose the source. For each shared field, decide where it will be captured first and which system is the master. The Insight where customer information gets lost during onboarding highlights the usual drop-off points.
  4. Make it readable. Give every team who needs it read access to that record, with POPIA's purpose limitation in mind, and show the key fields on their screens.
  5. Change the questions. Replace "please provide your address" with confirmation prompts, and remove fields the business already holds.
  6. Track the complaint. Count how often staff note "customer already gave this" and review the number monthly. A falling count shows the change is working.

Diagnostic questions

  • How many separate forms or scripts ask customers for their basic details?
  • Can the finance team see what sales captured before they contact the customer?
  • Which system is the master record for a customer's contact person?
  • What happens to older copies when a customer changes their details?
  • How many times has a customer said "I already told you" this month?

Bottom line

Asking customers for the same information twice looks like a small courtesy lapse, but it exposes a business that does not share what it knows. Capturing each fact once, keeping it in one place that every team can read, and asking only for what is new saves time, speeds up cash and onboarding, supports POPIA obligations on accuracy, and shows customers that the business is one organisation.

Sources and further reading

Related Mellorca reading

Article summaryWhen sales, accounts and support each ask the customer for the same details, the customer notices a business that does not share what it knows. Here is the cost and how to stop it.
Explore our solutionsStart a conversation