Prompt
I'm building a team workflow for PMs and support to answer product usage questions
Latest observation
Here’s a solid way to design a team workflow for PMs and support to answer product usage questions without turning every question into ad hoc Slack threads.
1) Define the question types
Start by separating requests into buckets:
- How-to / product usage: “How do I do X?”
- Troubleshooting: “Why isn’t X working?”
- Account-specific questions: “Why does my org not see feature Y?”
- Product behavior / policy: “Is this expected?”
- Feature gaps / feedback: “Can the product do X?”
This helps decide:
- who should answer,
- what source of truth to use,
- when to escalate.
2) Create a single intake path
Use one entry point for all usage questions:
- Support ticket form
- Slack channel with a structured template
- Internal request form
Include fields like:
- customer/org
- product area
- question
- screenshots/logs
- urgency
- whether it’s blocking revenue / live customer conversation
3) Set ownership rules
A simple ownership model works well:
- Support owns first response
- Triage
- answer from docs/macros if possible
- gather missing info
- PMs own product interpretation
- clarify intended behavior
- answer ambiguous product logic
- decide if there’s a gap or bug
- Escalate to Eng/Design only when needed
- bug
- unclear implementation
- product change request
A good rule:
Support answers “how to use it”; PM answers “how it works and why”; Engineering answers “is it broken?”
4) Build a knowledge source hierarchy
To keep answers consistent, define where people should check first:
- Help center / docs
- Internal FAQ / decision log
- Support macros / canned responses
- PM notes on edge cases
- Engineering bug tracker / release notes
If the same question comes up repeatedly, convert it into a doc or macro.
5) Use a decision tree for escalation
Example:
- Can support answer from docs?
- Yes → reply
- No → check internal FAQ/macros
- Is it about expected behavior or product policy?
- Yes → PM confirms
- Does it appear broken or inconsistent?
- Yes → escalate to Eng
- Is it a recurring gap?
- Yes → add to product feedback backlog
6) Define SLAs
Set expectations so nobody is waiting in limbo.
Example:
- Support initial reply: within 1 business hour
- PM review for escalations: within 1 business day
- Eng bug confirmation: within 2 business days
Even if the answer is “we’re investigating,” customers and internal teams benefit from predictability.
7) Create templates for answers
A standard response format saves time:
- Answer
- Why this happens
- Steps to resolve
- Workaround, if any
- Link to docs
- Escalation status, if needed
Example:
Yes — this is expected behavior. The dashboard only shows data after the first sync completes. If you just connected the source, please wait up to 30 minutes and refresh. Docs here: [link].
8) Maintain an internal “known answers” log
Track:
- recurring questions
- answer owner
- source of truth
- customer-facing wording
- last reviewed date
This becomes a living FAQ and reduces repeated PM interruptions.
9) Add a feedback loop
At the end of each week or month:
- review top questions
- identify missing documentation
- find confusing product flows
- spot bugs or UX issues
Then update:
- docs
- macros
- onboarding/training
- product backlog
10) Keep PM involvement focused
PMs should not be the default answer engine. Their role is best used for:
- ambiguous product behavior
- policy/edge cases
- strategic gaps
- high-value escalations
That keeps PM time protected while still giving support a clear escalation path.
A simple operating model
If you want a lightweight version:
- Support handles first-line questions
- PMs own product truth and edge cases
- One shared FAQ/macros doc
- One escalation channel
- Weekly review of repeat questions
If you want, I can turn this into one of these:
- a RACI chart for Support/PM/Eng
- a Slack + ticket workflow
- a one-page SOP
- a Notion/Confluence template for the team