feedback and support
users can send feedback or ask for help when the product behaves unexpectedly. support should route the issue to the right feature instead of giving generic advice.
quick answer
when a user is stuck, capture the screen, feature, expected behavior, and what happened instead.
use this for
- support intake
- product feedback
- bug reports from app users
steps
- name the feature or page where the issue happened.
- describe what the user expected.
- describe what actually happened.
- include the document or profile context only when safe.
- send feedback through the support path or reply path provided.
details to know
- feedback can be about product behavior, unclear copy, missing docs, or bugs.
- support responses should link the relevant wiki page when there is one.
- a good report helps fix the product faster than a vague complaint.
limits and edge cases
- do not include provider keys, passwords, or private customer data in feedback.
- do not use account deletion as a support shortcut.
- urgent billing or access issues should be routed directly to the right product area.
ready to use the product instead of reading about it?
open app