--- name: customer-research description: Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response. argument-hint: "" --- # /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 ``` ## 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. **Tier 1 — Official Internal Sources (highest confidence):** - ~~knowledge base (if connected): product docs, runbooks, FAQs, policy documents - ~~cloud storage: internal documents, specs, guides, past research - Product roadmap (internal-facing): feature timelines, priorities **Tier 2 — Organizational Context:** - ~~CRM notes: account notes, activity history, previous answers, opportunity details - ~~support platform (if connected): previous resolutions, known issues, workarounds - Meeting notes: previous discussions, decisions, commitments **Tier 3 — Team Communications:** - ~~chat: search for the topic in relevant channels; check if teammates have discussed or answered this before - ~~email: search for previous correspondence on this topic - Calendar notes: meeting agendas and post-meeting notes **Tier 4 — External Sources:** - Web search: official documentation, blog posts, community forums - Public knowledge bases, help centers, release notes - Third-party documentation: integration partners, complementary tools **Tier 5 — Inferred or Analogical (use when direct sources don't yield answers):** - Similar situations: how similar questions were handled before - Analogous customers: what worked for comparable accounts - General best practices: industry standards and norms ### 3. Synthesize Findings Compile results into a structured research brief: ``` ## Research: [Question/Topic] ### Answer [Clear, direct answer to the question — lead with the bottom line] **Confidence:** [High / Medium / Low] [Explain what drives the confidence level] ### Key Findings **From [Source 1]:** - [Finding with specific detail] - [Finding with specific detail] **From [Source 2]:** - [Finding with specific detail] ### Context & Nuance [Any caveats, edge cases, or additional context that matters] ### Sources 1. [Source name/link] — [what it contributed] 2. [Source name/link] — [what it contributed] 3. [Source name/link] — [what it contributed] ### Gaps & Unknowns - [What couldn't be confirmed] - [What might need verification from a subject matter expert] ### Recommended Next Steps - [Action if the answer needs to go to a customer] - [Action if further research is needed] - [Who to consult for verification if needed] ``` ### 4. Handle Insufficient Sources If no connected sources yield results: - Perform web research on the topic - Ask the user for internal context: - "I couldn't find this in connected sources. Do you have internal docs or knowledge base articles about this?" - "Has your team discussed this topic before? Any ~~chat channels I should check?" - "Is there a subject matter expert who would know the answer?" - Be transparent about limitations: - "This answer is based on web research only — please verify against your internal documentation before sharing with the customer." - "I found a possible answer but couldn't confirm it from an authoritative internal source." ### 5. Customer-Facing Considerations If the research is to answer a customer question: - Flag if the answer involves product roadmap, pricing, legal, or security topics that may need review - Note if the answer differs from what may have been communicated previously - Suggest appropriate caveats for the customer-facing response - Offer to draft the customer response: "Want me to draft a response to the customer based on these findings?" ### 6. Knowledge Capture After research is complete, suggest capturing the knowledge: - "Should I save these findings to your knowledge base for future reference?" - "Want me to create a FAQ entry based on this research?" - "This might be worth documenting — should I draft a runbook entry?" This helps build institutional knowledge and reduces duplicate research effort across the team. --- ## Source Prioritization and Confidence ### Confidence by Source Tier | Tier | Source Type | Confidence | Notes | |------|-------------|------------|-------| | 1 | Official internal docs, KB, policies | **High** | Trust unless clearly outdated — check dates | | 2 | CRM, support tickets, meeting notes | **Medium-High** | May be subjective or incomplete | | 3 | Chat, email, calendar notes | **Medium** | Informal, may be out of context or speculative | | 4 | Web, forums, third-party docs | **Low-Medium** | May not reflect your specific situation | | 5 | Inference, analogies, best practices | **Low** | Clearly flag as inference, not fact | ### Confidence Levels Always assign and communicate a confidence level: **High Confidence:** - Answer confirmed by official documentation or authoritative source - Multiple sources corroborate the same answer - Information is current (verified within a reasonable timeframe) - "I'm confident this is accurate based on [source]." **Medium Confidence:** - Answer found in informal sources (chat, email) but not official docs - Single source without corroboration - Information may be slightly outdated but likely still valid - "Based on [source], this appears to be the case, but I'd recommend confirming with [team/person]." **Low Confidence:** - Answer is inferred from related information - Sources are outdated or potentially unreliable - Contradictory information found across sources - "I wasn't able to find a definitive answer. Based on [context], my best assessment is [answer], but this should be verified before sharing with the customer." **Unable to Determine:** - No relevant information found in any source - Question requires specialized knowledge not available in sources - "I couldn't find information about this. I recommend reaching out to [suggested expert/team] for a definitive answer." ### Handling Contradictions When sources disagree: 1. Note the contradiction explicitly 2. Identify which source is more authoritative or more recent 3. Present both perspectives with context 4. Recommend how to resolve the discrepancy 5. If going to a customer: use the most conservative/cautious answer until resolved ## When to Escalate vs. Answer Directly ### Answer Directly When: - Official documentation clearly addresses the question - Multiple reliable sources corroborate the answer - The question is factual and non-sensitive - The answer doesn't involve commitments, timelines, or pricing - You've answered similar questions before with confirmed accuracy ### Escalate or Verify When: - The answer involves product roadmap commitments or timelines - Pricing, legal terms, or contract-specific questions - Security, compliance, or data handling questions - The answer could set a precedent or create expectations - You found contradictory information in sources - The question involves a specific customer's custom configuration - The answer requires specialized expertise you don't have - The customer is at risk and the wrong answer could exacerbate the situation ### Escalation Path: 1. **Subject matter expert**: For technical or domain-specific questions 2. **Product team**: For roadmap, feature, or capability questions 3. **Legal/compliance**: For terms, privacy, security, or regulatory questions 4. **Billing/finance**: For pricing, invoice, or payment-related questions 5. **Engineering**: For custom configurations, bugs, or technical root causes 6. **Leadership**: For strategic decisions, exceptions, or high-stakes situations ## Research Documentation for Team Knowledge Base After completing research, capture the knowledge for future use. ### When to Document: - Question has come up before or likely will again - Research took significant effort to compile - Answer required synthesizing multiple sources - Answer corrects a common misunderstanding - Answer involves nuance that's easy to get wrong ### Documentation Format: ``` ## [Question/Topic] **Last Verified:** [date] **Confidence:** [level] ### Answer [Clear, direct answer] ### Details [Supporting detail, context, and nuance] ### Sources [Where this information came from] ### Related Questions [Other questions this might help answer] ### Review Notes [When to re-verify, what might change this answer] ``` ### Knowledge Base Hygiene: - Date-stamp all entries - Flag entries that reference specific product versions or features - Review and update entries quarterly - Archive entries that are no longer relevant - Tag entries for searchability (by topic, product area, customer segment) --- Attribution added by YourAIKit. It is not part of the upstream file. - Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/customer-support/skills/customer-research - Credit: Anthropic, Knowledge Work Plugins (customer-support) - Upstream copy: anthropics/knowledge-work-plugins at commit 33d3dea41a341b341d4f5da2e8801ae0c89be2b8, customer-support/skills/customer-research/SKILL.md - Copyright: held by the upstream authors credited above - License: Apache-2.0. Full text: https://youraikit.com/licenses/anthropics-knowledge-work-plugins-customer-support/LICENSE - The full upstream license text (LICENSE) follows. License (LICENSE): ```text Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```