Prompt
What should I use for in-app support messages and FAQs?
Latest observation
Nov 1, 2026
OpenAI APIWeb search: off
For in-app support messages and FAQs, the best choice is usually:
1) Use simple, friendly, concise language
Users should understand the answer immediately without needing to “decode” it.
- Keep sentences short
- Avoid jargon
- Use everyday words
- Focus on the user’s problem, not internal company terms
Example:
Instead of: “Please verify your credentials and attempt reauthentication.”
Use: “Try signing in again.”
2) Use a consistent tone
Pick a tone that matches your product:
- Professional and calm for finance, healthcare, enterprise
- Friendly and approachable for consumer apps
- Clear and reassuring for support/checkout/error messages
3) Structure FAQs by user intent
Group questions around what users are trying to do, not around your org chart.
Good FAQ categories:
- Getting started
- Billing and payments
- Account settings
- Troubleshooting
- Privacy and security
4) Use action-oriented support messages
When something goes wrong, tell users:
- What happened
- Why it may have happened
- What to do next
Example:
“Your payment didn’t go through. Please check your card details or try another payment method.”
5) Keep answers scannable
Use:
- Short paragraphs
- Bullet points
- Bolded key actions
- Links to deeper help only when needed
6) Match help content to the screen
In-app support should be contextual:
- Use tooltips for quick explanations
- Use inline help near confusing fields
- Use modals or help panels for slightly longer guidance
- Reserve full FAQ articles for detailed topics
Recommended style
A good default style is:
- Clear
- Concise
- Helpful
- Non-technical
- Reassuring
If you want, I can also give you:
- a support message style guide,
- FAQ writing examples, or
- recommended wording for error messages, tooltips, and empty states.