When a client asks to remove the reject button: how agencies say no and keep the account
Every agency that ships consent work eventually gets the request. A client sees the reject button in the demo, winces, and asks: can we just take that off? The revenue team has a forecast, the marketing lead has a dashboard, and the banner is visibly in the way. How the agency answers decides both the compliance outcome and the relationship.
Why the request happens
Clients do not ask to remove the reject button because they want to break the law. They ask because nobody has connected the button to anything they care about. The opt-in rate looks like a cost, and the banner looks optional. The agency's first job is to make the trade visible before it becomes a negotiation.
The request also tends to arrive late: during QA, at launch, or after a stakeholder sees a competitor's site with a suspiciously cheerful banner. Late requests are harder because the client has already imagined the launch without the button. That is why the answer should be rehearsed long before it is needed.
The answer that keeps the account
Start with the rule, stated plainly and without a lecture. Refusing consent must be as easy as accepting it. That is not the agency's opinion; it is what regulators have said in decision after decision, and several have fined companies for asymmetric banners. The client is not asking for a design tweak. They are asking the agency to ship a known violation.
Then name the exposure in the client's language. A missing reject button is the kind of violation that shows up in automated scans, competitor complaints, and the evidence bundle of any future dispute. It is also the easiest thing for a regulator to screenshot. Unlike a subtle tracking configuration, a one-sided banner is visible to everyone, including the client's own legal team when they eventually look.
The design middle ground that actually works
Saying no to removing the button does not mean shipping an ugly banner. Most of the opt-in anxiety comes from banners that are designed badly, not banners that offer a real choice. A reject option can be a quiet text link next to the accept button, styled to match, requiring no extra click. That satisfies the symmetry requirement without turning the banner into a wall of buttons.
What does not work is the fake middle ground: a reject link that opens a second screen, a settings panel with everything pre-ticked, or a "manage preferences" link that resets on every visit. Regulators have seen all of these. Each one converts a design discussion into a dark-pattern finding.
Put the decision in writing
When a client pushes hard, document the recommendation and the client's decision. A short email works: we advised that removing the reject option would breach the requirement that refusing be as easy as accepting, and the client chose to proceed anyway. Agencies that keep this record protect themselves when the client's next agency, auditor, or regulator asks who made the call.
Better still, put consent decisions in the handover document for every client site: what was configured, what was recommended, what was declined. It turns a hallway argument into project documentation, and it is the first thing a serious agency hands over at launch.
The commercial upside of the hard no
Agencies worry that pushing back costs them the client. In practice, the opposite is more common. A client who hears "we cannot do that, and here is the compliant version that still looks good" learns that the agency knows things they do not. That is the beginning of a retainer, not the end of a project. The agencies that say yes to everything are interchangeable. The ones that say no with a reason are advisors.
The reject button stays. The agency's job is to make that answer boring: a settled question with a good design, documented once, and never argued about again.