customer-researchlisted

# /customer-research > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Multi-source research on a customer question, product topic, or account-related inquiry. Synthesizes findings from all available sources with clear attribution and confidence scoring. ## Usage ``` /customer-research <question or topic> ``` ## Workflow ### 1. Parse the Research Request Identify what type of research is needed: - **Customer question**: Something a customer has asked that needs an answer (e.g., "Does our product support SSO with Okta?") - **Issue investigation**: Background on a reported problem (e.g., "Has this bug been reported before? What's the known workaround?") - **Account context**: History with a specific customer (e.g., "What did we tell Acme Corp last time they asked about this?") - **Topic research**: General topic relevant to support work (e.g., "Best practices for webhook retry logic") Before searching, clarify what you're actually trying to find: - Is this a factual question with a definitive answer? - Is this a contextual question requiring multiple perspectives? - Is this an exploratory question where the scope is still being defined? - Who is the audience for the answer (internal team, customer, leadership)? ### 2. Search Available Sources Search systematically through the source tiers below, adapting to what is connected. Don't stop at the first result — cross-reference across sources. **Tie