What should you do if a customer asks about a feature that is not currently available?

What should you do if a customer asks about a feature that is not currently available?

• A. Promise it will be added next week without confirmation.
• B. Be honest about its absence, provide alternatives, and log the request for future consideration.
• C. Tell the customer to use a different product.
• D. Ignore the request and move on to other inquiries.

Answer: (B)

When a feature isn’t available, the right approach is transparent, practical help that keeps the customer moving forward. Start by acknowledging the limitation clearly and honestly about what the product can do today. If the feature isn’t ready, explain that it isn’t available at the moment and offer any existing alternatives or workarounds that could address their use case. Then take action by logging the request in your system so the product team can review it for future consideration. This shows the customer their input matters and helps convert their feedback into potential roadmap items. If possible, offer a realistic path for follow-up, such as a timeline for when they might hear back or when the request will be reviewed. This approach builds trust because you’re not overpromising, you provide value with what can be done now, and you show the customer their needs are being tracked. Avoid promising an unconfirmed roadmap, telling them to switch products, or ignoring the request, as those choices undermine trust and leave the customer without support.

When a feature isn’t available, the right approach is transparent, practical help that keeps the customer moving forward. Start by acknowledging the limitation clearly and honestly about what the product can do today. If the feature isn’t ready, explain that it isn’t available at the moment and offer any existing alternatives or workarounds that could address their use case.

Then take action by logging the request in your system so the product team can review it for future consideration. This shows the customer their input matters and helps convert their feedback into potential roadmap items. If possible, offer a realistic path for follow-up, such as a timeline for when they might hear back or when the request will be reviewed.

This approach builds trust because you’re not overpromising, you provide value with what can be done now, and you show the customer their needs are being tracked. Avoid promising an unconfirmed roadmap, telling them to switch products, or ignoring the request, as those choices undermine trust and leave the customer without support.