Customers say “What if the service goes down” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
The customer is thinking about their risk if something goes wrong: lost work, a delayed customer, blame. They want to know what you do, how quickly and what they can rely on. Answer with facts about your support, never with promises of perfection.
Typical in: Software and SaaS, Telecom and energy
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Show you heard it, then ask an open question before you respond.
“That is an important question. Let me tell you what we do when something goes wrong: how you report it, who responds and what you can expect. I will also tell you what we cannot control.” Use your company’s actual support terms.
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“I can show you our support process and what is written in the terms about service levels, so that you see what is committed and what is not.” Offer only documents that exist.
Ask what sits behind the objection, so you answer the real concern.
“What would be the worst moment for it to fail in your business? Then I can show you what we would do in exactly that case.”
After your response, ask:
How much downtime could you realistically live with, and at which times is it most critical?
Avoid: It never goes down.
A claim of perfection is not believed, and the first incident proves it wrong. It also avoids the question.
Reading is not the same as saying it. Talk to an AI customer who raises this kind of objection and see in the report which sentence helped.
Practise this objectionThe customer is thinking about their risk if something goes wrong: lost work, a delayed customer, blame. They want to know what you do, how quickly and what they can rely on. Answer with facts about your support, never with promises of perfection.
Acknowledge, then ask: “That is an important question. Let me tell you what we do when something goes wrong: how you report it, who responds and what you can expect. I will also tell you what we cannot control.” Use your company’s actual support terms. Offer proof: “I can show you our support process and what is written in the terms about service levels, so that you see what is committed and what is not.” Offer only documents that exist. Clarify before you answer: “What would be the worst moment for it to fail in your business? Then I can show you what we would do in exactly that case.”
How much downtime could you realistically live with, and at which times is it most critical?
Avoid “It never goes down.” A claim of perfection is not believed, and the first incident proves it wrong. It also avoids the question.
Educational conversation training. It is not legal or financial advice and it promises no results. Always follow your company’s rules, the terms of the product and a customer’s clear no.