Make a support question easy to understand
When asking about the intake process, say which step you were on, what you expected to happen, and what happened instead. Include only non-sensitive context needed to understand the issue; do not post passwords, personal identifiers, or confidential request details in a general feedback message.
Prepare before you ask
A short, factual description helps the appropriate support route understand your question.
-
1
Identify the step
Name the intake stage or field where you had difficulty.
-
2
Describe expected and actual results
State what you thought would happen and what happened instead, without including sensitive information.
-
3
Check the process answer
Review the FAQ for answers about request context, clarification, and changed priorities.
-
4
Use the approved support route
Follow the support channel published by your organization. If the route is not shown in your local rollout materials, ask your manager or rollout coordinator which approved channel to use.
Choose the right next action
| Situation | What to include | Next action |
|---|---|---|
| Process question | The step you were taking and what was unclear. | Check the FAQ; if unresolved, use the approved support route. |
| Incomplete request | The request detail the reviewer needs and any relevant context. | Update the request through the approved intake process. |
| Workflow feedback | What happened, the impact on your work, and a practical suggestion if you have one. | Share it through the configured rollout feedback channel. |
| Access or routing difficulty | The affected step and what you can safely describe. | Use the organization’s approved support route; avoid sending credentials or sensitive data. |
Keep feedback actionable
A useful observation is specific: “I could not tell whether preferred timing meant a requested date or a general planning window.” This describes the point of confusion and gives the rollout team something concrete to review.