Technique · Influence
Real reason on every ask
Attach a true, specific reason to each request a product makes: permissions, data fields, upgrades, review asks. People agree more often when a request comes with a reason, and once the stakes rise only real reasons keep working.
Plain label: reason-backed requestAlso known as: because effect, reason-giving, placebic reason, copier study, permission prompt copy
How it works
A request that carries a reason signals that a justification exists, which lets people accept it without weighing every detail. For trivial asks the form of a reason is often enough; for costly asks (payment, personal data, long commitments) only a substantive, checkable reason keeps working. A real reason also makes the ask feel less arbitrary, so fewer people revoke it later.
In the book. Chapter 1 opens with a line at a copier: a reason, even an empty one, sharply raised agreement to a small favor (Ch.1, pp.3-4). INF-T-FN-01 (Influence Ch.1, p.3)
In a product [S]. Every ask (permission, profile field, upgrade, review) gets one true, specific reason in plain words, placed next to the button. Where traffic allows, test three arms: no reason, real reason, filler reason. If the filler performs like the real reason, people are reacting to the form, and the ask is small enough that a real reason costs nothing.
Evidence Evidence grade B. Moderate evidence: solid studies with some limits.. Real reasons help reliably; empty ones help only on trivial requests.
Evidence warning
The empty-reason effect holds only for trivial asks, and later replications were partial; never rely on filler reasons for payment, data or long commitments.
What the research says
In the original copier study, 60% let a stranger cut in with no reason, 94% with a real reason and 93% with an empty one; the empty reason worked only because the favor was tiny.
Influence Ch.1, pp.3-4 (Langer, Blank & Chanowitz), 1978
In the same research, a larger request got no lift from an empty reason; only a real reason raised agreement. Expect the same split between a newsletter opt-in and a card or data ask.
Langer, Blank & Chanowitz, Journal of Personality and Social Psychology, 1978
How to build it
- Web
- Before the browser permission prompt, show one line that names the concrete benefit ("Allow alerts so we can tell you when your export is ready"). Where traffic allows, test no reason, real reason and a filler reason; keep the filler arm only as a diagnostic.
- Mobile
- Use a pre-permission screen at the moment the feature is needed ("Turn on location to see stores within 5 minutes of you") and fire the system prompt only after the user taps continue.
- Email and SMS
- In the sign-up form and preference center, say why each field or opt-in is asked ("Your birthday lets us send the yearly discount; we never share it").
- B2B
- Name the real trigger on an upgrade nudge, taken from the account's usage ("Upgrade because your team now runs 4 projects and this plan covers 3").
What can go wrong
- Generic reasons ("to improve your experience") read as filler and add nothing on high-stakes asks.
- A reason that turns out to be false costs trust for every later ask.
- Long explanations raise reading effort and can lower acceptance on mobile.
Pairs well with
- Pairs with permission asked right after first value (HK-TRG11): the reason lands best when the benefit was just felt.
- Pairs with in-t-ep-03: put the reason where an overloaded user will actually see it.
In practice
Where it shows up
Sources
Influence · Robert Cialdini
Ch.1, p.3
The mindlessness of ostensibly thoughtful action: the role of "placebic" information in interpersonal interaction · Journal of Personality and Social Psychology, 1978
Source IDs: INF-T-FN-01
Book content is paraphrased, never quoted at length. Last verified October 24, 2026.
Your product
Find the stage your product is stuck in
Gamify It reads your product, picks the one move that matters at its stage, and sizes the test to your traffic. Connecting is free; a Pro subscription starts it.