The answer to the can't-provide question has a shape that works in every customer-facing job: acknowledge what they want, say clearly once what you cannot do and why, offer what you can, escalate when the request is worth more than your authority, and leave them feeling heard either way. Interviewers ask it in retail, hospitality, support and B2B roles because the wrong instincts, a flat no or a promise you cannot keep, both lose customers. It is a cousin of what does good customer service mean to you, overlaps with a time you handled a difficult customer, and uses the same muscle as a time you had to say no. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.
What the interviewer is asking
Whether you can say no without being cold or vague, whether you look for the nearest yes, whether you know the limits of your authority and when to escalate, and whether you keep the relationship. They also listen for honesty: candidates who would promise and hope are a liability. The strong answer has the five steps and one example in which the customer left satisfied without getting what they first asked for.
A structure that works
- Acknowledge the request and the reason behind it.
- Say no once, clearly, with the reason; do not negotiate against policy.
- Offer what you can: the nearest alternative, a partial, a referral.
- Escalate when the customer's value or the situation warrants an exception; then follow through.
Three sample answers
Retail
A customer wanted to return a product outside the window without a receipt, which the system would not allow. I said I understood it was frustrating, explained once what the policy allowed and why, and then looked for what I could do: a store credit was possible with ID, and I offered to check whether the item was still in the catalogue for an exchange. She took the credit. If she had been a regular with a long history, I would have called the manager for an exception rather than saying no twice.
Support
When a customer asks for a feature we do not have, I never say 'we don't do that' and stop. I ask what they are trying to accomplish, because often there is a way to get most of it with what exists. I log the request so product sees the demand. And I am honest about timelines: I do not promise a roadmap I cannot see. Customers can hear the difference between 'no, but here is what I can do today' and a brush-off; the first keeps them.
B2B
A client asked for a contract term our legal team would not accept. I acknowledged why they wanted it, explained plainly that we could not sign it as written, and asked what risk it was protecting them from. The answer was a specific scenario, and we found a narrower clause that covered it, which legal approved. Escalating to legal was the right call because the account was worth it; saying a flat no would have ended the deal.
Mistakes that sink the answer
- A flat no with no alternative.
- Promising something you cannot deliver to end the conversation.
- Negotiating against policy on the spot.
- Never escalating, even for a high-value customer.
- No example.
A ten-minute practice routine
- Write the five steps in your own words for the role you are interviewing for.
- Pick one example where the customer left satisfied without their original request.
- Say it aloud in under a minute; keep the tone warm.
- Answer it in the browser demo or a mock interview and compare with the structured answer.
- Prepare a sentence on when you would escalate for an exception.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
How do you answer 'what do you do when a customer asks for something you can't provide'?
Acknowledge the request, say no once with the reason, offer the nearest alternative, escalate when the customer or situation warrants an exception, and follow through.
Is it ever right to make an exception?
Through the proper channel, yes; say you would escalate for a high-value customer rather than bend policy yourself.
How do I avoid sounding like a brush-off?
Ask what they are trying to accomplish and offer what you can do today; log the request if it is a product gap.
How long should the answer be?
Forty-five to sixty seconds.
Rehearse the answer out loud
The browser demo runs 145 real interview questions across 10 tracks and shows a structured answer to compare with yours. Free, no signup.
Try a practice question