What to Say Instead of Unfortunately in Customer Service: Examples

What to say instead of unfortunately in customer service depends on the situation: lead with the useful fact, acknowledge the inconvenience, and explain what you can do next. These customer service phrases to use instead of unfortunately can help with delays, refusals, stockouts, and uncertain answers. For a delay, give the status and a realistic update. For a request you cannot approve, state the limit plainly and offer an available option. A different phrase helps only when the action behind it is real.

Why “unfortunately” can make a customer hear “no” before the explanation

“Unfortunately” can signal bad news before the customer hears the facts. Instead of opening with it, state the status or action first, then explain the limitation and what happens next. A phrase cannot change the outcome, but clear wording can make the answer easier to understand and act on.

For example, compare:

Unfortunately, your order is delayed.

with:

Your order has not shipped yet. I’m checking the latest status and will update you when I have a confirmed estimate.

The second version does not disguise the problem. It starts with the information the customer needs and makes the next step explicit. Use the second sentence only if you can actually check and follow up.

“Unfortunately” is not forbidden. Sometimes an apology or a direct expression of regret is appropriate. The point is not to replace it mechanically with a sunnier phrase. If the answer is still a flat refusal, wording such as “Here is what we can do instead” will ring hollow unless there really is another option.

A useful reply usually has a few parts: the relevant fact, an acknowledgment where one is warranted, the boundary or explanation, and a practical next step. Not every response needs all of them. A simple status update can be short; a disputed refund request may need a clear explanation and a choice.

Acknowledge the customer before explaining the limitation

Acknowledge the specific issue before giving a limitation. For more examples, see our customer service apology examples and email templates. Say what happened from the customer’s point of view, without claiming to know exactly how they feel. Then explain what you know and what you can do. This shows you have heard the concern without delaying the answer behind a long apology.

A customer says a parcel was expected by now. Rather than starting with “Unfortunately,” try:

I can see that your parcel has not arrived when you expected it. I’m sorry for the wait. I’ll check the delivery status and tell you what I find.

If the customer has already explained the issue, do not make them repeat it. Listen to the whole concern and reflect the important detail in plain language. “You received the wrong size, and you need to know whether it can be exchanged” is more useful than a generic “I understand how you feel.”

Empathy does not require guessing at the customer’s emotions. “That sounds frustrating” acknowledges the situation. “I know exactly how you feel” can sound presumptuous, especially when the customer is upset about a specific cost, missed event, or inconvenience you have not experienced.

Apologize when your business has caused a problem or when an apology is appropriate to the situation. Make it specific and connect it to action:

I’m sorry we sent the wrong item. I’ll check the available exchange options and explain what we can do.

Avoid an apology that takes the place of a resolution:

Sorry for the inconvenience.

That sentence may be polite, but on its own it tells the customer neither what happened nor what comes next. If you do not yet know the fix, say what you are checking and how you will keep the customer informed.

When you have to deny a request, state the boundary and offer what you can do

When you cannot grant a request, state the relevant limit directly and then offer an option that is genuinely available. Do not bury the answer in policy language or imply that an exception is likely if you cannot authorize one. A clear boundary is more helpful than a vague promise to “look into it.”

For a refund request outside your stated return period, an agent might write:

I understand that you’re asking for a refund. This purchase is outside our return period, so I can’t approve a refund under the current policy. I can check whether another option is available.

Use the final sentence only if there is something the agent can actually check. If the policy leaves no alternative, be clear about that rather than inventing one:

I understand you’re asking for a refund. This purchase is outside our return period, and I’m not able to approve a refund. I can explain how the policy applies to your order.

This answer is direct without making the customer feel that a policy document is speaking in place of a person. If there is a real option—such as an exchange, store credit, or a different service route—name it specifically. Do not list possibilities your business does not offer.

Ask a question when the customer has a choice to make:

I can’t change the delivery address after dispatch. Would you like me to check whether the carrier offers another option?

That question is appropriate only if checking with the carrier is part of your process. The action belongs to the agent who sends the message. Do not say “Let me take care of that” unless you are taking responsibility for a concrete next step.

A good refusal does not need to be cheerful. It needs to be understandable, respectful, and honest about the boundary. If an exception requires approval, say that you are requesting a review—not that the exception will be granted.

When an order or item is delayed, give a useful update instead of a vague apology

For a delay, tell the customer what is known, what is still being checked, and when you will update them. Thanking someone for waiting can be courteous, but it does not replace a status or a next step. Give an estimate only when you have a reasonable basis for it.

When you have a confirmed estimate:

Thanks for your patience. Your order is expected to ship on [confirmed date]. I’ll let you know if that changes.

When the date is not confirmed:

I don’t have a confirmed shipping date yet, and I don’t want to guess. I’m checking with our team and will update you when I have a reliable answer.

Use a date or update point only if you can meet it. If you cannot promise a precise time, explain what will trigger the next update—for example, receiving a supplier confirmation—then take responsibility for following up.

A vague reply such as “We’re working on it” can leave the customer wondering whether anyone owns the issue. Make the work visible:

I’ve asked our fulfilment team to check the shipment status. I’ll share their update when I have it.

That wording is useful only if the request has actually been sent. After making a commitment, record it in the conversation or the team’s workflow so another agent can see what the customer was told. If the original agent is unavailable, the customer should not have to start over.

Do not turn a hoped-for resolution into a guarantee. “We’ll get this fixed today” may sound reassuring, but it creates a promise the team may not control. Prefer a commitment to an action you own: “I’ll check the status and update you when I have a confirmed answer.”

When a product is unavailable, be direct and give the next best option

If an item is unavailable, say so plainly and offer only confirmed choices. A customer needs to know whether they can wait, choose another item, or cancel—not a soft opening that delays the fact. If no alternative is available, say that and let the customer decide what to do next.

For example:

The blue jacket is out of stock in your size. I can check whether another size is available, or you can tell me if you would like to cancel.

Use the options in that message only if they apply to the order and your store’s process. If you have a confirmed restock date, share it as an estimate you can support:

The item is expected back on [confirmed date]. Would you prefer to wait or look at another option?

If you do not have a confirmed date, do not invent one:

I don’t have a confirmed restock date. I can let you know when we receive an update, or help you look at an available alternative.

Be careful not to imply that an item is “in high demand” or will return soon unless you know that is true. A positive-sounding explanation that is not grounded in the inventory status can erode trust more than a direct answer.

When a customer has already paid, explain the choices that actually apply to their order and follow your store’s obligations. Do not make a refund or shipping commitment unless you are authorized and can carry it out. The customer should understand what they can choose and what will happen after they choose it.

What to say instead of unfortunately in a customer service email or chat

Short replies work when they still answer the customer’s question. Replace “unfortunately” with a phrase that fits the job: acknowledge the issue, explain the known fact, take ownership of an action, or set out a real option. A phrase by itself is not a resolution.

To acknowledge a problem:

I can see why the delay is frustrating.

You received the wrong item, and I’ll help check the next step.

Name the problem rather than relying on a generic “I understand.” Do not assume the customer’s feelings if they have not described them.

To take ownership:

I’ll check the order status and update you when I have an answer.

Let me look at the available exchange options.

These are commitments. Use them only if the agent can do the work or can pass it to someone who will. “Let me take care of that” sounds reassuring, but it should be followed by the action it promises.

To explain a limit:

I can’t change the address after the parcel has shipped. I can check whether another delivery option is available.

We’re not able to approve a refund for this order under the current return policy. I can explain how the policy applies.

Keep the boundary specific. “We can’t do that” may leave the customer unsure whether the limit concerns timing, policy, stock, or the agent’s authority.

When you are still checking:

I don’t have a confirmed answer yet. I’m checking with the team and will update you when I know more.

I’d rather not guess. I’ll share an update when the information is confirmed.

Do not promise a follow-up time unless you can meet it. If a customer asks for an update and you still do not know, acknowledge that plainly and give the next action. Silence after a promised update is often more damaging than an honest note that the answer is still pending.

Email can support a little more context; chat often benefits from shorter sentences. For ready-to-adapt wording, see these customer service replies and templates. In either channel, keep the same substance: the fact, the relevant limit, the action, and the next update. Avoid sending a polished paragraph that hides the answer the customer came for.

Choose wording that agents can say sincerely and support can follow through on

Train agents on scenarios rather than asking everyone to memorize one replacement for “unfortunately.” The right wording for an out-of-stock item differs from the right wording for a refund denial or a delay. In each case, the reply should match what the business can actually do.

A practical template can include. For more ways to structure a natural exchange, see our customer service conversation examples:

• Issue: What is the customer trying to resolve?
• Fact: What is confirmed?
• Limit: What cannot be done, if anything?
• Action and owner: Who will do what next?
• Update: When or under what condition will the customer hear more?

For example, a delay template might be:

Your order is [current status]. I’m [action and owner]. I’ll update you [confirmed follow-up point].

A refusal template might be:

I understand you’re asking for [request]. [Clear reason or boundary]. I can [available option], if you would like.

Treat the bracketed parts as prompts, not text to send without checking. Agents need to confirm the order, policy, and available options before choosing the words. A template should make a good answer easier; it should not encourage agents to guess.

Review whether the action and update promised in the message actually happened. If agents repeatedly send “I’m checking” without a clear owner, fix the handoff or workflow rather than adding a new phrase to the template. If one wording causes confusion, revise it against real customer questions and the limits agents can explain.

For teams handling repeated questions, momo can answer from the business’s own content and send uncertain questions to a human inbox. It retrieves relevant passages, checks its drafted answer against those sources, and includes citations when it is confident; when it is not, it says so and opens a ticket for the team. That can help with routine, documented answers, but it does not replace an agent’s judgment about empathy, exceptions, or what the team can promise.

Frequently asked questions

What is a better word for “unfortunately” in customer service? What can I say instead?

There is no single word that fits every situation, and no one-word replacement works in every customer service exchange. Try a specific acknowledgment such as “I can see why that’s frustrating,” a clear fact such as “The item is out of stock,” or an action such as “I’ll check the available options.” Choose wording that reflects what is true and what you can do.

How do I say no to a customer without sounding dismissive?

Acknowledge the request, state the boundary in plain language, and offer a real alternative if one exists. Explain how the limit applies to the customer’s situation instead of hiding behind a generic policy statement. Do not suggest that an exception is possible unless you have authority to pursue one.

What should I say when a customer asks for an update and I do not know the answer yet?

Say that you do not have a confirmed answer. Tell the customer what you are checking and when or under what condition you will update them. Do not guess at a date or send a vague “we’re working on it” without an owner and a next step.

Should customer service agents apologize when an item is out of stock?

An apology may be appropriate if the situation has caused an inconvenience, especially if the customer has already placed an order. Keep it brief and pair it with the confirmed status and available choices. Do not let the apology obscure whether the item is unavailable or what the customer can do.

How can I make customer service phrases sound less scripted?

Use templates as structures, not fixed speeches. Include the customer’s actual issue, the confirmed facts, and the next step that applies to their case. Let agents adapt the wording to the conversation, then check that they follow through on any action or update they promise.

Make the next step part of the reply

The most useful alternative to “unfortunately” is often not another phrase. It is a direct answer that names the customer’s problem, explains the real limit, and gives an action the team can deliver. If you are evaluating ways to handle repeated, documented questions, you can try momo free.