Documentation/AI Agents

    AI Agents

    Automate your workflow with AI-powered assistants that extract data, generate summaries, enforce processes, and provide continuous intelligence from your conversations.

    Why Automate?

    Meetric's automations transform your conversations from raw recordings into structured, actionable intelligence. Instead of manually reviewing hours of calls, let AI do the heavy lifting while you focus on high-value activities.

    Save Time

    Reduce manual data entry and review time by 80%

    Increase Consistency

    Apply the same analysis to every conversation

    Scale Intelligence

    Analyze 100s of conversations as easily as one

    Automation Types#

    Meetric offers six types of automations, each designed for different use cases:

    AI Employees

    Advanced

    Autonomous AI that works continuously, generating reports and insights on a schedule

    Best for: Ongoing analysis and reporting

    AI Fields

    Simple-Intermediate

    Extract specific data points from conversations into structured fields

    Best for: CRM sync, data extraction

    AI Summaries

    Simple

    Generate custom-formatted summaries based on your prompts

    Best for: Quick meeting recaps, custom formats

    AI Playbooks

    Intermediate

    Score conversations against your defined process and methodology

    Best for: Coaching, process adherence

    Advanced AI Agents

    Advanced

    Multi-step agents that use tools and complex logic

    Best for: Custom workflows, complex analysis

    Keyword Trackers

    Simple

    Track specific keywords or concepts across conversations

    Best for: Topic tracking, competitor mentions

    AI Employees#

    AI Employees are autonomous assistants that continuously analyze your conversations and deliver scheduled reports and insights.

    Available AI Employees#

    Sales Analyst AI Employee

    Analyzes sales pipeline, conversion patterns, and team performance

    Department: B2B Sales
    Outputs:
    • • Weekly performance reports
    • • Pipeline insights
    • • Conversion trends
    • • Coaching opportunities

    Data Analyst AI Employee

    Coming Soon

    Analyzes KPIs, conversation trends, and department performance

    Department: All
    Outputs:
    • • Weekly KPI reports
    • • Trend analysis
    • • Department insights
    • • Action recommendations

    Sales Coach AI Employee

    Coming Soon

    Reviews sales conversations and provides personalized coaching feedback

    Department: B2B Sales
    Outputs:
    • • Call reviews
    • • Coaching insights
    • • Best practices
    • • Manager reports

    Setting Up an AI Employee#

    1. Navigate to AI Agents in the left sidebar
    2. Click "AI Employees" category
    3. Select the employee type you want to create
    4. Click "Create" and follow the setup wizard:
      • Name: Give your employee a descriptive name
      • Department: Select which department to analyze (pre-set based on employee type)
      • Schedule: Choose when reports are generated (daily, weekly, monthly)
      • Recipients: Select who receives the reports
      • Focus Areas: Choose specific metrics or topics to emphasize
    5. Review configuration and click "Activate"
    AI Employee Setup Wizard with multi-step configuration form
    Configure your AI Employee with department, schedule, and reporting settings

    Tip

    Start with weekly schedules to avoid report fatigue. You can always increase frequency once you establish value.

    Example: Weekly Sales Report#

    Real-world example of a Sales Analyst AI Employee configuration:

    Sales Analyst Configuration
    Name: "Q1 Sales Performance Analyst"
    Department: B2B Sales
    Schedule: Every Monday at 8 AM
    Recipients: [email protected], [email protected]
    
    Focus Areas:
    ✓ Pipeline velocity
    ✓ Conversion rates by stage
    ✓ Average deal size trends
    ✓ Top objections encountered
    ✓ Win/loss patterns
    ✓ Individual rep performance
    
    Output Format:
    - Executive summary (3-5 key insights)
    - Pipeline metrics table
    - Conversion funnel visualization
    - Top coaching opportunities
    - Recommended actions for coming week

    Result: Sales managers receive actionable insights every Monday morning, identifying coaching opportunities and pipeline risks before weekly team meetings.

    Tips & Tricks#

    • Be specific with focus areas: The more targeted your configuration, the more actionable the insights
    • Align schedule with meetings: Send reports before key meetings (e.g., Monday morning before sales standup)
    • Start narrow, expand later: Begin with one department, then add more as you see value
    • Use consistent naming: Name employees by their purpose (e.g., "Enterprise Sales Q1 Analyst")
    • Review first reports: Check initial outputs and adjust focus areas if needed

    Warning

    AI Employees vs AI Agents: Employees run on a schedule and generate reports. Agents run on each conversation in real-time. Use Employees for periodic analysis, Agents for immediate data extraction.

    AI Fields#

    AI Fields extract specific pieces of information from conversations into structured, filterable, CRM-syncable fields.

    Field Types#

    Number Field

    Extract numeric values like budget, deal size, or quantities

    Examples: Budget range: $50,000 | Team size: 25 users | Contract length: 12 months

    Text Field

    Capture free-form text like next steps or pain points

    Examples: Next steps: Send proposal | Main concern: Integration complexity

    Date Field

    Extract mentioned dates and timelines

    Examples: Decision date: Q1 2024 | Implementation: March 15 | Renewal: 2024-06-30

    List Field

    Capture multiple items like stakeholders or requirements

    Examples: Stakeholders: [CEO, CTO, VP Sales] | Integrations: [Salesforce, Slack, HubSpot]

    Multiple Choice

    Classify into predefined categories

    Examples: Pain point: [Performance, Cost, Integration] | Urgency: [High, Medium, Low]

    Setting Up AI Fields#

    1. Go to AI Agents → AI Fields
    2. Click "Create Field"
    3. Choose field type and configure:
      • Field Name: What you're extracting (e.g., "Budget Range")
      • Description: Help AI understand what to look for
      • Extraction Prompt: Instructions for the AI
      • Validation Rules: Format requirements or constraints
      • Default Value: What to use if nothing is found
    4. Configure CRM sync (optional):
      • Map to CRM field (Salesforce, HubSpot, Pipedrive)
      • Set sync direction (one-way or two-way)
      • Choose sync frequency (real-time or daily)
    5. Test on sample conversations
    6. Activate for all conversations
    AI Field configuration interface
    Create custom fields with extraction prompts, validation rules, and CRM mapping

    Common AI Field Examples#

    Budget Range Extractor

    Number Field
    Prompt:

    "Extract any budget amounts, price ranges, or financial figures mentioned in the conversation. Include both the low and high end if a range is given."

    Example Output:$50,000 - $100,000
    Use Case: Sales qualification and deal sizing

    Decision Timeline

    Date Field
    Prompt:

    "Extract when the customer expects to make a purchase decision. Look for mentions of timelines, deadlines, fiscal periods, or decision dates."

    Example Output:Q1 2024 (March 31)
    Use Case: Sales forecasting and follow-up timing

    Competitor Mentions

    List Field
    Prompt:

    "List all competitor names or alternative solutions mentioned during the conversation. Include both direct competitors and indirect alternatives being considered."

    Example Output:[Competitor A, Competitor B, Build in-house]
    Use Case: Competitive intelligence and positioning

    Pain Points

    Multiple Choice
    Prompt:

    "Categorize the primary business challenge discussed. Options: Performance Issues, High Costs, Integration Complexity, Scalability, User Adoption, Security Concerns, Other"

    Example Output:Integration Complexity, User Adoption
    Use Case: Product prioritization and messaging

    Writing Effective Extraction Prompts#

    The quality of your extraction prompt directly impacts accuracy:

    DO:

    Be specific about what to extract

    DON'T:

    Use vague instructions

    DO: 'Extract the specific dollar amount or range mentioned for annual budget'
    DON'T: 'Get budget info'
    DO:

    Provide context and examples

    DON'T:

    Assume AI knows your terminology

    DO: 'Extract decision maker titles (e.g., VP, Director, C-level) and their departments'
    DON'T: 'Get decision makers'
    DO:

    Handle edge cases

    DON'T:

    Only think about the happy path

    DO: 'If no budget is mentioned, return "Not Discussed". If they say "flexible", note that.'
    DON'T: 'Extract budget'
    DO:

    Specify output format

    DON'T:

    Leave format ambiguous

    DO: 'Return dates in YYYY-MM-DD format. If only a month is mentioned, use the last day of that month.'
    DON'T: 'Extract dates'

    Tip

    Test your field on 10-15 past conversations before activating it for all conversations. This helps you catch edge cases and refine your prompt.

    AI Summaries#

    Generate custom-formatted summaries tailored to your specific needs and workflows.

    Summary Types#

    Executive Summary

    High-level overview for busy executives

    Includes:
    • • Key decisions made
    • • Critical action items
    • • Strategic insights
    • • Risk factors

    Typical length: 3-5 bullet points

    Sales Call Summary

    Focused on deal progression and next steps

    Includes:
    • • Deal stage update
    • • Objections raised
    • • Stakeholders identified
    • • Next actions

    Typical length: Structured format with sections

    Support Ticket Summary

    Technical details and resolution path

    Includes:
    • • Issue description
    • • Steps taken
    • • Resolution status
    • • Follow-up required

    Typical length: Detailed, technical

    Custom Summary

    Your own format and focus areas

    Includes:
    • • Whatever you specify in your prompt

    Typical length: Your choice

    Creating Custom Summaries#

    1. Navigate to AI Agents → AI Summaries
    2. Click "Create Custom Summary"
    3. Configure summary:
      • Summary Name: Descriptive name (e.g., "Enterprise Sales Summary")
      • Template: Start from template or create from scratch
      • Prompt: Define what to include and how to format
      • Length: Specify desired length (brief, moderate, detailed)
      • Format: Choose output style (bullets, paragraphs, sections)
    4. Preview on sample conversations
    5. Adjust prompt based on results
    6. Activate for department or all conversations
    Example Custom Summary Prompt
    Create a sales call summary with these sections:
    
    ## Deal Status
    - Current stage in pipeline
    - Changes from last conversation
    - Overall deal health (Green/Yellow/Red)
    
    ## Key Discussion Points
    - Top 3 topics discussed
    - Customer sentiment on each
    
    ## Stakeholders
    - Who participated
    - New stakeholders identified
    - Decision-making authority
    
    ## Objections & Concerns
    - Any objections raised
    - How they were addressed
    - Remaining concerns
    
    ## Next Steps
    - Agreed action items with owners
    - Timeline for follow-up
    - Success criteria for next meeting
    
    Keep each section concise (2-3 sentences). Highlight any red flags in bold.

    Summary Best Practices#

    • Balance detail and brevity: More detail isn't always better - focus on actionable insights
    • Use consistent formatting: Structured summaries are easier to scan than paragraphs
    • Include context clues: Dates, participant names, and call type help orientation
    • Highlight urgency: Use formatting (bold, caps) to call out time-sensitive items
    • Test with diverse calls: Ensure your prompt works for short and long calls, positive and negative outcomes
    • Version your prompts: Keep track of what changes improve quality

    Note

    Summaries are generated automatically for all new conversations. For existing conversations, you can regenerate summaries from the conversation detail page.

    AI Playbooks#

    Playbooks measure how well conversations follow your defined methodology, providing coaching insights and process adherence scores.

    Available Playbooks#

    Sales Process Playbook

    1. 1Introduction & rapport
    2. 2Needs discovery
    3. 3Solution presentation
    4. 4Objection handling
    5. 5Close & next steps

    Discovery Call Playbook

    1. 1Qualification questions
    2. 2Pain point exploration
    3. 3Budget discussion
    4. 4Timeline identification
    5. 5Stakeholder mapping

    Support Playbook

    1. 1Issue understanding
    2. 2Troubleshooting steps
    3. 3Resolution confirmation
    4. 4Follow-up scheduling
    5. 5Satisfaction check

    Demo Playbook

    1. 1Recap needs
    2. 2Feature walkthrough
    3. 3Use case examples
    4. 4Q&A session
    5. 5Trial setup

    Creating a Playbook#

    1. Go to AI Agents → AI Playbooks
    2. Select "Create New Playbook" or choose template
    3. Define playbook structure:
      • Playbook Name: E.g., "Enterprise Discovery Methodology"
      • Department: Which team uses this playbook
      • Call Type: When this playbook applies
    4. Add playbook steps (minimum 3, maximum 15):
      • Step Name: What should happen (e.g., "Budget Discovery")
      • Description: Detailed explanation of the step
      • Success Criteria: What good execution looks like
      • Key Questions: Specific questions that should be asked
      • Required: Is this step mandatory or optional?
    5. Set scoring weights (optional - how important is each step)
    6. Test on past conversations
    7. Activate playbook
    Playbook Builder interface
    Build and customize playbooks with drag-and-drop steps and scoring criteria

    Understanding Playbook Scores#

    After each conversation, the playbook generates:

    Overall Score

    0-100% based on step completion and quality

    Interpretation: 90%+ = Excellent, 70-89% = Good, 50-69% = Needs Improvement, <50% = Poor

    Step Completion

    Which steps were covered vs. skipped

    Interpretation: Green = completed well, Yellow = partially covered, Red = missed

    Quality Indicators

    How thoroughly each step was executed

    Interpretation: Based on time spent, questions asked, depth of discussion

    Coaching Opportunities

    Specific suggestions for improvement

    Interpretation: AI identifies what could have been done better at each step

    Tip

    Use playbook scores for coaching, not punishment. Focus on trends over time and celebrate improvement, not just perfection.

    Playbook Design Tips#

    • Start with your best rep: Document what your top performers do consistently
    • Keep steps clear and actionable: "Ask about budget" not "Discuss financials"
    • Don't overcomplicate: 5-8 steps is ideal; more than 12 becomes unwieldy
    • Allow flexibility: Mark optional steps as such; not every call follows the same path
    • Update regularly: Review and refine based on what actually works
    • Use for onboarding: Playbooks are excellent training tools for new hires

    Advanced AI Agents#

    Advanced agents combine multiple AI capabilities, tools, and workflows for complex analysis and decision-making.

    Common Agent Types#

    Lead Qualification Agent

    Advanced

    Analyzes conversations to score lead quality using BANT or custom criteria

    Capabilities:
    • • Extract qualification data
    • • Score against criteria
    • • Update CRM
    • • Alert sales ops

    Sentiment Analysis Agent

    Intermediate

    Performs deep emotional analysis and satisfaction scoring

    Capabilities:
    • • Detect emotions
    • • Track sentiment shifts
    • • Identify escalation risk
    • • Generate alerts

    Deal Progression Agent

    Advanced

    Tracks deal stages and predicts close probability

    Capabilities:
    • • Stage detection
    • • Bottleneck identification
    • • Probability scoring
    • • Forecast updates

    Competitive Intelligence Agent

    Advanced

    Monitors competitor mentions and analyzes competitive positioning

    Capabilities:
    • • Track mentions
    • • Analyze positioning
    • • Price intelligence
    • • Market insights

    Creating Advanced Agents#

    Advanced agents require more configuration than simple fields:

    1. Navigate to AI Agents → Advanced AI Agents
    2. Choose agent template or start from scratch
    3. Configure agent workflow:
      • Input Sources: What data the agent analyzes
      • Processing Steps: Multi-step analysis workflow
      • Decision Logic: Rules and criteria for decisions
      • Tools & Integrations: External systems to access
      • Output Actions: What happens with results
    4. Define permissions and access
    5. Test thoroughly on historical data
    6. Monitor performance after activation

    Warning

    Advanced agents can modify data and trigger actions. Test extensively before deploying to production conversations.

    When to Use Agents vs. Fields#

    Use AI Fields When:

    • Extracting single data points
    • Output is a simple value
    • No complex logic needed
    • Syncing to CRM
    • Speed is critical

    Use Advanced Agents When:

    • Multi-step analysis required
    • Need to access external data
    • Complex decision logic
    • Triggering workflows
    • Combining multiple data sources

    Keyword Trackers#

    Track specific keywords, phrases, or concepts across all conversations for analytics and filtering.

    Tracker Levels#

    Level 1: Basic Keyword

    Simple

    Exact text matching for specific words or phrases

    Example: Track mentions of 'enterprise plan' or 'annual contract'

    Best for: Known phrases, product names, exact terminology

    Level 2: AI Keyword

    Intermediate

    Intent-based tracking that understands variations

    Example: Track concept of 'budget concerns' including 'too expensive', 'over budget', 'price is high'

    Best for: Concepts with many variations, intent-based tracking

    Level 3: Advanced Tracker

    Advanced

    AI prompts for complex pattern detection with sub-categorization

    Example: Track 'objections' and auto-categorize into Price, Features, Timeline, Competition

    Best for: Complex concepts requiring categorization

    Creating Keyword Trackers#

    For Basic Keyword Trackers:

    1. Go to AI Agents → Keyword Trackers
    2. Click "Basic Keyword Tracker"
    3. Enter keywords/phrases (one per line)
    4. Choose case-sensitive matching (optional)
    5. Save and activate

    For AI Keyword Trackers:

    1. Click "AI Keyword Tracker"
    2. Name your concept (e.g., "Budget Objections")
    3. Provide positive examples (phrases that match):
      • "That's outside our budget"
      • "We can't afford that right now"
      • "Price is a concern for us"
    4. Provide negative examples (similar phrases that shouldn't match):
      • "Our budget is flexible"
      • "Price isn't an issue"
    5. Train on past conversations
    6. Review accuracy and adjust examples
    7. Activate when satisfied

    Tip

    For AI trackers, provide 5-10 positive examples and 3-5 negative examples for best results.

    Using Tracker Data#

    Once activated, trackers provide:

    • Statistical Widgets: View mention frequency over time
    • Conversation Filtering: Find all conversations where keyword was mentioned
    • Trend Analysis: Track how often concepts come up week-over-week
    • Correlation Analysis: See which keywords appear together
    • Dashboard Integration: Add tracker widgets to Insights dashboard
    Keyword Tracker analytics dashboard
    Track keyword mentions over time with trend charts and conversation breakdown

    Common Tracker Use Cases#

    Competitor Intelligence

    Setup: Track competitor names + AI tracker for 'considering alternatives'

    Insight: Know when prospects are evaluating competitors

    Feature Requests

    Setup: Track specific feature names + 'wish' or 'would like to see'

    Insight: Prioritize product roadmap based on customer voice

    Objection Patterns

    Setup: AI tracker for common objections with sub-categories

    Insight: Train team on most frequent objections

    Compliance Monitoring

    Setup: Track required disclosures and regulatory terms

    Insight: Ensure all necessary topics are covered

    Managing AI Agents#

    Monitor performance, edit configurations, and maintain your AI agent library.

    Viewing Agent Status#

    From the AI Agents page, you can see:

    • Active Status: Running, paused, or inactive
    • Performance Metrics: Accuracy, usage, error rate
    • Processing Stats: How many conversations processed
    • Last Run: When the agent last executed
    • Resource Usage: Processing time and credits used

    Editing & Updating#

    To modify an automation:

    1. Click the automation name
    2. Click "Edit"
    3. Make your changes
    4. Choose update behavior:
      • Future Only: Apply changes to new conversations only
      • Reprocess All: Re-run automation on historical conversations
      • Reprocess Failed: Only retry previously failed conversations
    5. Save changes

    Warning

    Reprocessing all conversations can be time-consuming and may use significant credits. Use sparingly for major prompt improvements.

    Troubleshooting Common Issues#

    Low Accuracy / Wrong Results

    • • Review prompt clarity and specificity
    • • Add more examples for AI-based automations
    • • Check if edge cases are handled
    • • Validate on diverse conversation types

    Automation Not Running

    • • Verify automation is active (not paused)
    • • Check department filters match conversations
    • • Ensure sufficient credits available
    • • Review error logs for specific failures

    Slow Processing

    • • Simplify complex multi-step agents
    • • Reduce number of fields per conversation
    • • Use caching where possible
    • • Consider batch processing for non-urgent automations

    CRM Sync Issues

    • • Verify CRM integration is connected
    • • Check field mapping is correct
    • • Ensure field types match between systems
    • • Review CRM permissions

    Tips & Tricks#

    Combining Multiple Agent Types#

    Get more value by using AI agents together:

    Fields + Playbooks

    Extract data points (budget, timeline) and score process adherence

    Benefit: Complete picture of call quality and deal data

    Trackers + Employees

    Track competitor mentions with keywords, analyze patterns with AI Employee

    Benefit: Know what competitors are mentioned and how positioning is trending

    Summaries + Agents

    Generate custom summary format, use agent to auto-update CRM from summary

    Benefit: Human-readable summaries plus automated data sync

    Avoiding Automation Overload#

    • Start small: Begin with 2-3 high-impact automations, add more as you see value
    • Audit regularly: Review which automations are actually being used quarterly
    • Consolidate where possible: Use one well-configured field instead of three similar ones
    • Set clear owners: Assign someone to maintain each automation
    • Track ROI: Measure time saved vs. effort to maintain

    Success Patterns#

    Start with Pre-Sales

    Sales teams see fastest ROI from automations due to structured processes

    Example: Budget extraction + decision timeline + playbook scoring = complete qualification automation

    Template Your Winners

    Once you nail a configuration, save it as a template for other teams

    Example: Sales playbook becomes template for CS onboarding playbook

    Iterate Based on Data

    Review automation accuracy monthly and refine prompts

    Example: Track field accuracy, adjust prompts for consistently wrong fields

    Involve End Users

    Get feedback from reps who see results daily

    Example: Sales reps spot when competitive intelligence agent misses key mentions

    Common Mistakes to Avoid#

    Creating too many similar fields

    Why it's bad: Confuses users and adds maintenance burden

    Do instead: Consolidate into fewer, well-defined fields

    Overly complex prompts

    Why it's bad: Harder to debug and may reduce accuracy

    Do instead: Start simple, add complexity only when needed

    Not testing before deploying

    Why it's bad: Bad data is worse than no data

    Do instead: Test on 10-15 conversations, review results, iterate

    Set and forget

    Why it's bad: Conversation patterns change over time

    Do instead: Review performance quarterly, update as needed

    Ready to Automate?

    Start with one high-impact automation and expand from there: