
As of November 2026, the honest answer is no: the customer is not always right, and the saying never meant that. It means the customer always has rights: to be heard, to a resolution, to dignity. A fair number of the demands that land in an inbox have none of those. For anyone running accounts at ad agencies or digital agencies in Singapore, that difference decides whether a team keeps a demanding client for years or burns out on one.
HubSpot's Ramona Sukhraj reopened the question on 6 November 2026 and reached the same conclusion from a marketer's experience in a marketing agency. Her argument is worth using, but not copying: an account team needs a decision rule it can apply in the next tense call, not a slogan to remember. This article gives that rule, the evidence behind it, and the numbers to put in front of your own management when a client asks for something the team should refuse.
The phrase sounds like a licence to concede, and that is how many account teams treat it. The history is less accommodating. Quote Investigator traced a precursor to a legal text published in 1884, where "a client is always right" was already described as an old saying. The earliest close match using the word "customer" appeared in 1905, in newspaper articles about the retailer Marshall Field of Chicago.
Field's own wording, as reported in later accounts, was more careful: assume the customer is right until it is clearly proven otherwise. That is a working instruction about how to begin a conversation, not an order about how to end it. Read that way, the saying asks a team to start from the customer's account of the problem, verify it, and then act on what the facts support.
Sukhraj reduces the phrase to five customer entitlements: to be heard, to have the issue resolved, to feel in control of the purchase, to be treated with dignity, and to expect support that arrives when promised. Every one of those can be honoured while a specific request is still being declined. A client can be told no to a change of scope and still be heard, respected and informed of what will happen instead.
This is the split that makes the rule usable. The rights are non-negotiable. The requests are not.

The argument for conceding usually rests on protecting the relationship. The data points the other way once you count the people who deliver the service.
A survey of frontline workers by Perceptyx found that 53% of respondents had recently dealt with verbally abusive, threatening or unruly customers. Those frontline workers were 1.3 times as likely to be job hunting, and nearly two in three had asked a manager for help.
For an agency, frontline workers are account managers, community managers and the people answering WhatsApp at nine at night. Losing them costs more than a difficult retainer is worth. This is where the team-level cost of "always say yes" shows up: not in the client's happiness, but in the resignation letter.
The fear behind over-accommodation is that a refusal loses the client. The numbers suggest that a bad experience does that far faster than a fair no. HubSpot's customer service statistics round-up, records that 73% of consumers say they would leave a company after just one bad experience, and 43% said a poor customer service experience discouraged them from buying from a brand again.
The same collection notes that 75% of customers will spend more on brands that offer good customer experience. The pattern is consistent: customers pay for the experience, not for unlimited compliance. A clear explanation of why a request cannot be met is part of a good experience; silence, delay or a promise nobody can keep is not.
Julian Tan's test for an account team, drawn from the two questions above, is this: a request is granted when refusing it removes one of the five rights; it is declined when refusing it removes only convenience.
| Situation | What the customer is asking for | Right or request | The move |
|---|---|---|---|
| Report is late | The truth about what happened | Right | Explain, then give a new date |
| Strategy underperforms | A diagnosis and a plan | Right | Show the data, propose the change |
| Policy exception on a fixed package | A special price only for them | Request | Offer the published option |
| Scope change mid-campaign | Extra work outside the signed scope | Request | Quote it, or sequence it |
| Abusive message to the account team | A response to the content | The demand is not a right | Set the boundary, escalate |
The third and fourth rows are where most agencies lose margin without ever winning loyalty. A special price given once becomes the reference point for every renewal, and a free scope change becomes the baseline expectation for the next brief.
None of this is a reason to be hard to work with. It is the practical reading of the saying for an agency: a client at ad agencies or their digital peers is buying judgement, and judgement that can be overruled by every request is not worth paying for. Clients of digital agencies notice the difference within one campaign cycle: the accounts that say no cleanly are the ones with a plan at the end of quarter.

Searches for digital agencies and their traditional counterparts return lists of firms, rankings and job boards. Few explain what the buyer is hiring when they first engage one, which is the missing piece behind most early disputes.
An advertising agency, in the plain sense the term is used in agency-selection guides, is an outsourced team that runs a client’s advertising, from the plan through production to the media buy. A digital agency does the same work with digital channels as its medium: paid search, social, display, programmatic placement, landing pages and the measurement around them. What the buyer pays for is not a finished asset. It is judgement, production hours and buying skill, bought for a defined period.
That definition matters to the question at hand. When the deliverable is judgement and labour, every request that arrives is really a request for more of one or the other. Naming the resource is the calmest way to decline: "that work sits outside the monthly retainer; here is what it would cost, and here is what I would drop to fit it in." It converts a conflict about being right into a conversation about capacity, which is easier to resolve and harder to argue with.
Sukhraj's interviews with customer-centric practitioners produced one method smooth enough to use in a live call, the Acknowledge, Relate, Offer sequence. It works for agencies because it separates the emotional acknowledgement from the commercial decision.
The sequence is not a trick for softening a refusal; it is a format that proves the customer was heard before the answer arrived. For an agency, the fourth step is the written record: send the same version in an email so nobody is arguing about what was said.
Each boundary needs a home in a document the team can reach in under a minute.
Reviewing that last item monthly turns a feeling of unfairness into a trend the operations lead can act on.
Teams that work this way tend to report the same thing after a quarter: fewer late-night messages, because the response pattern is predictable, and fewer surprises at renewal, because nothing was promised that the scope did not cover. ad agencies that treat the boundary as a product feature rather than a defensive habit find it easier to sell the next retainer, since the client knows what the monthly fee actually buys.

Topkee Media, the group of ad and digital agencies behind this article's sponsor, runs its client-facing work on the second half of this argument. Speed and consistency go to the customer; structure and protection go to the team. Its YME system puts WhatsApp, Messenger and Live Chat on one structured surface. AI and human agents share the replies, covering more hours and other languages, and hand a ready lead to sales. The Care pre-sales assistant works a simpler version of the same sequence: it answers in the customer's language, collects the fields the merchant defined, then invites a human agent to take over. Both are attempts to make "always answer" operationally possible without asking a person to be on call all night.
The boundary side runs through standardisation rather than goodwill. The group's customer-service methodology documents auto-reply templates for simple and after-hours messages, a single script plus staff training for complex issues, and scripts rewritten from past high-converting chat logs. Retention work, including a free funnel-leak audit at the start of an engagement and a retention review alongside acquisition in each reporting cycle, sits in the same direction: keeping the right customers is treated as work with a method, not a promise to please everyone. Topkee Media is a Google Premier Partner and runs a Singapore company, opened in its international expansion.
Take the retainer or package you are running now and write the negotiable and non-negotiable list for it in one page. Then map the last twenty emails from the client against the table above: if more than a few sit in the "request" rows and were granted anyway, the account has a margin problem and a precedent problem at the same time. For teams that sell or buy media across these relationships, the Topkee guide on how to select the right agency for ADLG SEM initiatives sets out the questions to ask at the selection stage, before the first difficult request arrives. For a view of where paid placements now sit, see the analysis of how ad counts concentrate inside Google AI answers.
No. The phrase is a service principle, not a factual claim about every request. It means the customer has the right to be heard and taken seriously, and it does not mean the business must grant every demand or accept abuse. HubSpot's 2026 update reaches the same conclusion, and the phrase's history supports it: Marshall Field was reported as saying to assume the customer is right until it is clearly proven otherwise.
Name the resource rather than the fault. State that the work sits outside the agreed scope, give the price or the trade-off, and keep the rest of the relationship intact. A customer service experience survey cited in HubSpot's statistics round-up found 43% of customers would stop buying after a poor service experience, but a decline delivered clearly and on time is not a poor experience. A late, evasive answer is.
It does not. The right to be heard ends where the right of the staff to be treated with dignity begins. A survey of frontline workers found 53% had recently faced verbally abusive, threatening or unruly customers, which is why a written escalation path and the authority to end a conversation belong in every agency's client playbook.
Expectations have been trained by the channels they use. HubSpot's research found 82% of customers expect immediate problem resolution from service agents. That is a reason to build faster channels and cover the hours customers write in, not a reason to accept every request that arrives through them.
Nobody can prove it. The earliest close match in print appeared in 1905 newspaper articles about Field, and later accounts report his own wording as more measured. Harry Gordon Selfridge, John Wanamaker and the hotelier César Ritz are also associated with similar versions of the idea.

Article Author