Why Customers Keep Being Asked for the Same Information

A customer applies for an account and fills in a form with their company name, registration number, delivery address and contact person. A week later, the accounts department emails to ask for the same details. When the first order arrives, the warehouse phones to confirm the delivery address. A month later, a support agent opens a query by asking for the customer's name and account number, again, and then asks for the order details that the customer sent in an email the day before.

No single person in this story did anything unreasonable. Each team asked for what it needed. Yet from the customer's side, the business looks disorganised, and every repetition is a small deduction from their confidence. Understanding why it happens is the first step to stopping it.

A customer should have to tell you something once. If they have to say it again, the failure is in how your business is joined together, not in how well your staff speak to people.

Cause one: each team holds its own copy

The most common cause is simply that the information lives in several unconnected places. Sales has the details in a CRM, finance has them in the accounting system, operations has a spreadsheet, and support works from an inbox. IBM describes this as data silos: information held in one part of an organisation that is not readily accessible to others. Unless someone deliberately copies a detail across, each team has to ask for it again. A single customer can therefore have four partially complete records and no complete one. The same pattern is examined from the cost side in the pain of customers repeating information across disconnected records.

Cause two: the information does not travel with the work

Even where systems are connected, the handoff itself may drop information. A sales representative agrees special delivery instructions on a call but records only the order. The onboarding team sees an order and no instructions. Nobody is careless. The form or the handoff note simply had no field for the detail, so it stayed in the representative's head. Our article on what information must move with the work explains how to decide what a handoff must carry, and where customer information gets lost during onboarding shows the most common leak points.

Cause three: forms are designed around departments

Each department creates the form it needs, usually at a different time. The result is three forms with overlapping fields: the credit application, the delivery set-up form and the support registration. None of them knows about the others. Because every form was built to serve one team, nobody was asked to look at the customer's whole journey and ask which fields already exist elsewhere.

Cause four: the customer cannot be recognised

Some repetition is not about missing data but about failing to find it. The customer's name is spelt differently in two systems, the account number was never recorded in the CRM, or there is no shared identifier linking an email address to an account. Staff cannot match the contact to a record, so they start from the beginning. Weak matching also produces duplicate records, which in turn multiply the number of times a customer is asked. The link to how duplicate data gets into business systems is direct.

Cause five: staff do not trust what they find

Sometimes the information is there, but nobody trusts it. A new contact number may have been entered once and never confirmed, so the agent asks again to be safe. This is a quality issue, not a laziness issue. Where records have no dates or sources, re-asking is a rational response. It becomes the default, and the customer pays for the business's uncertainty. A small amount of confirmation in the right place, such as showing the details already held and asking whether they are still correct, is better than asking from scratch.

Why this matters beyond politeness

Repetition costs time on both sides, increases the chance of inconsistent answers, and gives errors a second chance to enter the system. It is also a signal that is easy to dismiss and expensive to ignore. In South Africa it has a legal angle as well. Section 13 of the Protection of Personal Information Act says personal information must be collected for a specific, explicitly defined and lawful purpose, and section 18 deals with making the person aware of what is collected and why. A business that asks for the same personal details several times, through several unconnected channels, is also creating several places where that information must be protected, justified and kept accurate. Collecting once, and using what it already holds, is both better service and better practice.

How to reduce it

Trace one customer's journey. Take a recent customer and list every point at which they supplied or confirmed information. Count the repeats. The exercise usually surprises management.
Decide where each item is captured. For every data item, such as registered name, VAT number, delivery address and contact person, choose one place where it is entered and other systems read from it.
Combine the forms. Where a customer is passing through onboarding, capture everything needed by sales, finance and operations in one guided process, and route it internally. The wider design is covered in how to design a customer onboarding workflow that scales.
Prefill and confirm. When a customer returns, show what is already held and ask for corrections only. Pre-filled fields cut effort and expose out-of-date details.
Add the missing fields to the handoff. If staff keep asking a question, the handoff is missing a field. Make it mandatory at the stage that learns the answer.
Give staff a single view. Even a simple shared record showing contact details, open orders and recent communication prevents most of the re-asking at the support desk.

Internal chasing and customer repetition are often two faces of the same fault. When teams keep having to ask each other, customers are usually being asked too, as discussed in why your team keeps chasing information.

An illustrative example

The following is a hypothetical case. A Port Elizabeth fleet-maintenance company onboards a new transport customer. The customer gives vehicle registration numbers, contact people and site addresses on a sales form, gives the same details to the accounts team for a credit application, and then gives the vehicle list a third time to the workshop booking system. The workshop manager complains that the vehicle lists never match.

The company replaces the three forms with one onboarding form that captures the customer details, the fleet list and the site contacts once. The submission creates the customer in the accounting system, and the workshop system reads the fleet list from it. Customers are asked to confirm their details each year, and any change flows to all three teams. Within a quarter, calls from accounts and the workshop asking for details dropped away, and the vehicle lists agreed.

A final test

Next time a customer calls your business, listen for the question that begins "Can I just confirm your...". Count how many of those questions the business could have answered from its own records. The number is a fair measure of how well the business is joined together, and it is one of the few measures that the customer sees directly.

Sources and further reading

What Are Data Silos? - IBM (last verified 10 October 2026)
Section 13 Collection for specific purpose - POPIA (last verified 10 October 2026)
Section 18 Notification to data subject when collecting personal information - POPIA (last verified 10 October 2026)