HeyKeyword

A feature wish is not always a buying requirement

A feature wish is not always a buying requirement
An editorial checklist illustration, not a product screen.

A public request for an integration may come from a paying customer, a casual visitor or someone comparing several products. Those situations need different responses. Keep the original wording and surrounding discussion before turning the request into a sales opportunity. A request alone does not establish a budget or permission to contact the writer privately.

A public request for an integration may come from a paying customer, a casual visitor or someone comparing several products. Those situations need different responses. Keep the original wording and surrounding discussion before turning the request into a sales opportunity. A request alone does not establish a budget or permission to contact the writer privately.

Read the decision behind the request

A public request for an integration may come from a paying customer, a casual visitor or someone comparing several products. Those situations need different responses. Keep the original wording and surrounding discussion before turning the request into a sales opportunity. A request alone does not establish a budget or permission to contact the writer privately.

Distinguish preference from a blocker

Compare two fictional statements: “A calendar would be nice” and “We cannot use this without a shared calendar.” The second describes a stronger constraint, but still needs context about the task and team. Label what is explicit, what you inferred and what remains unknown. Do not invent urgency from an enthusiastic phrase.

Answer the present capability

If you represent a product, explain what works now and what does not. A workaround should describe its cost and limitations. Do not promise a roadmap date to win a conversation. When you ask a follow-up, make it useful: which action cannot be completed, and what would a successful result look like?

Group needs without counting copies twice

Group independent requests by the underlying job, not just the feature name. A calendar request may concern reminders, approvals or a visual overview. Keep repeated copies of one source together and retain links to the originals. This is a manual research method, not a claim that any monitoring tool discovers every request.

[Review the intent of a public mention](/blog/brand-mention-question-versus-recommendation)