How to Say Something Is Not Available in App Feedback Reply English
When you need to tell a user that a feature, item, or service is not available in your app, the way you phrase it can make the difference between a frustrated user and a patient one. In app feedback reply English, saying something is unavailable requires clarity, politeness, and often a brief reason or alternative. This guide gives you the exact phrases, tone adjustments, and common pitfalls to avoid so you can write replies that are honest without sounding dismissive.
Quick Answer: The Best Phrases for Unavailability
If you need a direct, polite way to say something is not available, use these three go-to phrases:
- “This feature is not currently available.” – Neutral and clear for most situations.
- “I’m sorry, but that option is not available at this time.” – Softer and more apologetic.
- “We don’t have that available yet, but it’s on our roadmap.” – Honest and forward-looking.
Each of these works in written feedback replies, in-app messages, or email support. The key is to match the tone to the user’s frustration level and your brand voice.
Formal vs. Informal Tone for Unavailability
Your choice of words should depend on whether you are writing a formal support email or a casual in-app chat reply. Here is how the tone shifts:
Formal Tone (Email or Official Support)
Use complete sentences, polite apologies, and clear explanations. Avoid shortcuts or slang.
- “We regret to inform you that the requested feature is not available in the current version.”
- “Unfortunately, this service is not available in your region at this time.”
- “Please be advised that the item you are looking for is out of stock and will be restocked next month.”
Informal Tone (In-App Chat or Quick Replies)
Use shorter sentences, friendly language, and sometimes emojis if your brand allows.
- “Sorry, that option isn’t available right now.”
- “We don’t have this feature yet, but we’re working on it!”
- “This item is currently unavailable. Check back soon.”
Nuance to Watch For
In formal replies, avoid blaming the user or sounding robotic. In informal replies, avoid being too vague. A user who hears “not available” without any reason may assume the app is broken or poorly designed.
Comparison Table: Phrases for Different Unavailability Situations
| Situation | Formal Phrase | Informal Phrase | Best Context |
|---|---|---|---|
| Feature not yet built | “This feature is not yet implemented.” | “We haven’t added this yet, but it’s coming.” | Roadmap updates |
| Item out of stock | “The item is currently out of stock.” | “Sorry, it’s sold out for now.” | E-commerce or in-app purchases |
| Service not in user’s region | “This service is not available in your location.” | “This isn’t available where you are yet.” | Geo-restricted apps |
| Temporary downtime | “The service is temporarily unavailable.” | “We’re down for a bit – try again later.” | Maintenance or outages |
| User request for old version | “That version is no longer supported.” | “We don’t support that version anymore.” | App updates |
Natural Examples of Unavailability Replies
Here are realistic examples you can adapt for your own app feedback replies. Each example includes a user message and a reply.
Example 1: Feature Not Available Yet
User: “I want to export my data to a CSV file, but I can’t find the option.”
Reply: “Thank you for reaching out. The CSV export feature is not currently available, but it is on our development roadmap. We expect to release it in the next update. We appreciate your patience.”
Example 2: Item Out of Stock
User: “I tried to buy the premium theme, but it says unavailable.”
Reply: “Hi there, the premium theme you selected is temporarily out of stock. We expect more licenses to be available within 48 hours. Would you like us to notify you when it’s back?”
Example 3: Regional Restriction
User: “Why can’t I use the payment feature? I’m in Brazil.”
Reply: “Unfortunately, the payment feature is not available in Brazil at this time. We are working to expand to more regions. For now, you can use the free version with all other features.”
Example 4: Temporary Downtime
User: “The app keeps crashing when I try to upload a photo.”
Reply: “We apologize for the inconvenience. The upload service is temporarily unavailable due to maintenance. Please try again in 30 minutes. We are working to restore it as quickly as possible.”
Common Mistakes When Saying Something Is Not Available
Even experienced support writers make these errors. Avoid them to keep your replies professional and helpful.
Mistake 1: Being Too Vague
Wrong: “That’s not available.”
Why it’s bad: The user has no idea why or when it will be available.
Better: “That feature is not available in the current version, but we plan to add it in the next release.”
Mistake 2: Blaming the User
Wrong: “You can’t use this because you didn’t update the app.”
Why it’s bad: It sounds accusatory and defensive.
Better: “This feature requires the latest version of the app. Please update to access it.”
Mistake 3: Promising Without Certainty
Wrong: “We’ll add it soon.”
Why it’s bad: “Soon” is vague and can create false expectations.
Better: “We are currently working on this feature and expect to release it within the next two months.”
Mistake 4: Using Negative Language
Wrong: “We don’t have that and we don’t know when we will.”
Why it’s bad: It sounds dismissive and unhelpful.
Better: “This feature is not available yet, but we have noted your request and will consider it for future updates.”
Better Alternatives for Common Unavailability Phrases
Sometimes the first phrase that comes to mind is not the most effective. Here are better alternatives for common situations.
Instead of “It’s not available”
- “This option is currently unavailable.” – More formal and clear.
- “We don’t offer this at the moment.” – Honest and neutral.
- “This is not part of the current release.” – Specific to software updates.
Instead of “We don’t have it”
- “We do not currently support this feature.” – Professional and direct.
- “This item is not in our inventory right now.” – Best for physical products.
- “This service has not been launched in your area yet.” – Good for regional limits.
When to Use Each Alternative
- Use “currently unavailable” for temporary issues like maintenance or stockouts.
- Use “not yet implemented” for features that are planned but not built.
- Use “no longer supported” for old versions or retired features.
- Use “not available in your region” for geo-restrictions.
Mini Practice Section: Write Your Own Unavailability Reply
Try writing a reply for each situation below. Then check the suggested answers.
Question 1
A user says: “I can’t find the dark mode option in settings.” The feature is planned but not built yet. Write a polite reply.
Suggested answer: “Thank you for your interest in dark mode. This feature is not yet available, but it is on our development list. We will notify users once it is released.”
Question 2
A user says: “I want to buy the annual subscription, but the button is grayed out.” The subscription is temporarily unavailable due to a payment processor issue. Write a reply.
Suggested answer: “We apologize for the inconvenience. The annual subscription option is temporarily unavailable due to a payment system update. Please try again in a few hours, or contact us if the issue persists.”
Question 3
A user says: “Why can’t I use the voice recording feature? I’m in Japan.” The feature is only available in the US and Canada. Write a reply.
Suggested answer: “Thank you for your question. The voice recording feature is currently only available in the US and Canada. We are working to expand to more countries, including Japan, but do not have a specific timeline yet.”
Question 4
A user says: “I downloaded the app yesterday, but now it says the version is too old.” The user needs to update to the latest version. Write a reply.
Suggested answer: “It looks like you are using an older version of the app. Some features are not available in older versions. Please update to the latest version from your app store to access all features.”
Frequently Asked Questions About Saying Something Is Not Available
1. Should I always apologize when something is not available?
Not always. If the unavailability is expected or temporary, a brief apology is polite. For example, “I’m sorry, but this feature is not available yet.” However, if the user is asking for something that was never offered, a simple explanation without apology is fine, such as “This feature is not part of our current plan.” Over-apologizing can sound insincere.
2. How do I say something is not available without sounding rude?
Use polite softening words like “unfortunately,” “I’m sorry,” or “we appreciate your understanding.” Always give a reason or a next step. For example, “Unfortunately, this item is out of stock. We expect more in two weeks.” Avoid blunt statements like “No” or “We don’t have it.”
3. What if the user is angry about the unavailability?
Acknowledge their frustration first. Then explain the situation clearly and offer a solution or alternative. For example, “I understand this is frustrating. The feature you requested is not available yet, but we have added your vote to our feature request list. In the meantime, you can use the manual input option.”
4. Can I use emojis when saying something is not available?
Yes, but only in informal contexts like in-app chat or social media replies. A simple “😅” or “🙏” can soften the message. Avoid emojis in formal email support. For example, in a chat reply: “Sorry, that feature isn’t ready yet 🙏 We’re working on it!”
Final Tips for Writing Unavailability Replies
When you write a reply about something not being available, always include three elements: what is not available, why (if appropriate), and what the user can do next. This turns a negative message into a helpful one. For more guidance on structuring your replies, explore our App Feedback Reply Problem Explanations category. You can also practice with real scenarios in our App Feedback Reply Practice Replies section. If you have questions about our approach, visit our FAQ page or read our Editorial Policy.
