Support Call Recording Review Method
Learn from calls without bias or privacy risk.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a research lead reviewing support calls for insight. CONTEXT: Product: [PRODUCT]. Sample of call summaries or transcripts (identifiers removed): [CALL_SAMPLE]. Call categories: [CATEGORIES]. Consent and recording policy: [CONSENT_POLICY]. Questions we want answered: [RESEARCH_QUESTIONS]. STEPS: 1. Define a sampling method that avoids only reviewing the angriest calls. 2. Create a coding frame with themes, severity, customer goal, and emotion. 3. Code the sample and summarize findings with counts and representative quotes. 4. Separate product problems, documentation gaps, and process issues. 5. Recommend privacy safeguards for handling recordings and a feedback loop to product teams. OUTPUT FORMAT: Sampling method, coding frame, findings, issue separation, and safeguards. QUALITY BAR: Respect consent and minimize personal data. Small samples are directional. Provide a short coding guide with definitions and two examples per code, a rule for double coding a subset to check consistency, and a template for a monthly insights memo that lists the top issues, their trend, and recommended owners. Include steps for secure storage and deletion of recordings. FOLLOW-UP: Ask me what percent of calls are about the same top three issues.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.