AI-powered system engineer that transforms your agent with intelligent prompt editing, parameter configuration, rich visual diagnostics, and comprehensive setup
Copilot is an advanced AI-powered system engineer integrated into the Advanced Editor. It goes far beyond simple prompt editing - Copilot can configure your entire agent system including input parameters, output settings, evaluations, audio expressiveness, and core configurations. Using sophisticated structured editing and intelligent analysis, Copilot transforms your agent based on natural language instructions and real call data.
Copilot has evolved from a prompt assistant to a complete system engineer - like having Data from Star Trek, but specifically designed for agent configuration. It can modify prompts, configure parameters, set up evaluations, update basic settings, adjust audio expressiveness tags, create and update tests from call history, and even suggest improvements - all through natural conversation and targeted operations. Beyond plain text, Copilot can also reply with rich visual blocks - stat panels, tables, charts, and cards - to make diagnostics and analysis instantly scannable.
Copilot now has a face: a gradient orb avatar that represents Meetzy across the entire chat experience, replacing the generic bot icon.
Idle State
Active State
A slow, ambient breathing animation while Copilot is waiting for your next message - a calm, always-present visual anchor in the empty state and next to every assistant reply.
When Copilot is thinking or streaming a response, the orb switches to a faster pulse with expanding rings, echoing the feeling of a call connecting - a subtle nod to Meetzy being a voice-agent copilot rather than a generic chat bot.
The orb appears in three places: the welcome screen hero, the avatar next to each assistant message, and the typing/thinking indicator - giving Copilot a consistent, recognizable identity throughout the conversation. Its state (idle or active) always reflects whether Copilot is waiting for you or actively working, so you always know at a glance whether it’s inactive or engaged.
When you first open Copilot, you’ll see a clean welcome screen led by the Copilot orb, followed by four quick action cards to get started immediately without typing a single word:
Quick Action Cards
One-Click Setup
Four color-coded cards for the most common engineering workflows:
🟣 Diagnose performance — analyzes real metrics, failed evaluations, and relevant calls, then shows the key findings visually (KPIs & call evidence)
🌹 Find recurring failures — scans failed evaluations across your call history and returns a table of recurring issues with real examples
🟢 Create a regression test — turns a real failed call into an automated regression test so the same bug never ships again
🟡 Improve and verify — updates the prompt based on the current diagnosis and suggests how to verify the change afterward
Instant analysis and fixes with a single click:
Click "Diagnose performance" → Runs a full performance diagnosis with visual KPIsClick "Find recurring failures" → Surfaces failure patterns in a table with call evidenceClick "Create a regression test" → Builds a regression test from a real failed callClick "Improve and verify" → Improves the prompt and proposes a verification plan
Each card pre-fills an optimized prompt and starts the conversation immediately - no typing required to get your first insight.
These quick actions are designed to close the loop: diagnose → find failures → fix with a regression test → improve and verify. Together they form a fast, guided workflow for continuously improving your agent.
Copilot’s replies are no longer limited to plain text. Depending on what you ask, Copilot decides the most effective format for its answer and can mix multiple output types in a single response:
Plain Text
Rich Content Blocks
Conversational explanations streamed in real time - used for reasoning, recommendations, step-by-step instructions, and any answer that reads best as natural language.
Structured visual components rendered inline with the chat - used whenever data is easier to scan than to read:
📊 Stat grids for KPIs and metrics
📋 Tables for lists of calls, failures, or test results
📈 Charts for trends and comparisons
🗂️ Cards for summaries, recommendations, and warnings
Rich blocks always render alongside supporting text, so Copilot explains what it found in words and shows the evidence visually in the same message.
Copilot doesn’t just reply with text anymore - when the situation calls for it, it renders rich, interactive blocks directly inside the chat, making diagnostics and analysis far easier to scan than a wall of text. These blocks stream in the same way as regular messages, so you see them appear live as Copilot builds its answer.
Stat Grids
Tables
Charts
Cards
At-a-glance KPI cards for quick diagnostics:
Compact grid of metric cards (e.g. success rate, average duration, failed evaluations)
Optional delta and trend indicators (up, down, flat) to show change over time
Color-coded tones (neutral, info, success, warning, danger) to highlight what needs attention
Optional hint text under each stat for extra context
Perfect for summarizing “Diagnose performance” results in a single scannable view.
Structured data views for lists of calls, failures, or test results:
Sticky header with clearly labeled columns
Automatic badge styling for common status values (Yes/No, Passed/Failed, Success/Error, Pending)
Scrollable, expandable body for long result sets without breaking the chat layout
Optional footnote for extra context or data source
Ideal for “Find recurring failures” results, showing each failure pattern with examples side by side.
Visual trend analysis rendered inline with the conversation:
Supports line, bar, pie, and doughnut chart types
Multiple datasets with automatic color palette
Dark mode aware styling for axes, legends, and gridlines
Great for visualizing performance trends over time or comparing metrics across segments.
Highlighted callouts for summaries, recommendations, or warnings:
Optional title, body text, and bullet list
Tone-based styling (neutral, info, success, warning, danger) to match the message
Used for wrapping up findings or proposing next steps after a diagnosis
Often appears after a stat grid or table to summarize “what this means” and “what to do next.”
Rich blocks stream in alongside regular text, so Copilot can explain a finding in natural language and immediately back it up with a stat grid, table, chart, or card - all within the same response. Look for these blocks whenever you ask Copilot to diagnose, compare, or summarize data - they turn a long paragraph into something you can scan in seconds.
Copilot uses a streamlined event system for real-time feedback across all system modifications:
Event Type
Description
Visual Indicator
Applies To
thinking
AI analyzing your request
⏱️ Timer with seconds counter
All operations
text
Streaming explanation content
📝 Real-time text appearing
All operations
edit
Structured prompt modification
✏️ Diff preview with operation details
Prompt changes
input_change
Input parameter modification
🔧 Parameter change card
Input parameters
output_change
Output setting update
📤 Output configuration card
Output settings
enrichment_set
Output enrichment update
⚡ Enrichment content preview
Output enrichment
evaluation_change
Evaluation criteria update
📊 Evaluation configuration
Evaluations
test_create
Automated test generation
🧪 Test scenario preview
Test creation
test_update
Existing test modification
🔁 Test diff preview
Test updates
agent_config
Basic settings update
⚙️ Configuration preview
Core settings
audio_tags_set
Expressive audio tag update
🎙️ Tag list preview
Audio expressiveness
rich_block
Rich UI block (stat grid, table, chart, card)
📊 Inline visual component
Diagnostics & analysis
complete
Operation finished
✅ Summary with next steps
All operations
error
Operation failed
❌ Error with suggested fixes
All operations
The rich_block event carries a blockType (stat_grid, table, chart, or card) plus a structured data payload. The frontend renders it as a native component inline with the rest of the streamed conversation, right next to any text events in the same response.
Copilot intelligently suggests changes across all agent configuration areas:
Input Parameter Operations
Output & Enrichment Configuration
Evaluation Criteria Setup
Basic Settings & Configuration
Audio Expressiveness Tags
Smart Parameter Suggestions based on comprehensive analysis:
1
Contextual Generation
Copilot analyzes your agent’s role and referenced calls to suggest relevant input parameters:
@call:abc123 The customer mentioned their budget repeatedly but we didn't capture it. Add budget tracking parameters.
Results in contextually relevant budget range and validation parameters.
2
Change Operations
Three types of parameter changes:
🟢 Add: New parameters with proper validation and descriptions
🟡 Modify: Updates to existing parameter configurations
🔴 Remove: Clean up outdated or redundant parameters
3
Visual Review System
Purple highlighting in Input Parameters panel shows pending changes with individual accept/reject controls.
Intelligent Output Field & Processing Setup:
The agent collected the customer's name and interest level but we're missing their preferred contact method. Add comprehensive output fields and enrichment instructions.
Copilot suggests:
Contextually relevant output parameters
Data enrichment instructions for processing captured information
Webhook configuration recommendations
Output validation and formatting rules
Performance Measurement Configuration based on agent goals:
Create evaluations to measure conversation quality, goal achievement, and customer satisfaction for this appointment scheduling agent.
Advanced Test Creation & Updates from Call History
One of Copilot’s most powerful features is generating - and maintaining - comprehensive test suites based on real call data:
Test Generation from Calls
Updating Existing Tests
Test Types Generated
Intelligent Test Structure
Transform Call History into Automated Tests:
@call:abc123 This call shows great objection handling. Create a test to ensure the agent maintains this quality.
Copilot automatically extracts:
Chat History: Complete conversation flow from the call
Success Conditions: What made this call successful
Success Examples: Specific agent responses that worked well
Failure Examples: Alternative responses to avoid
Dynamic Variables: Contextual information that can be varied in tests
Refine tests in place instead of duplicating them:
Update the "Objection handling - pricing" test to include the new discount policy and tighten the success condition.
Copilot can modify an existing test’s:
Name and description
Chat history to reflect updated conversation flows
Success condition as your requirements evolve
Success/failure examples to match current expectations
Dynamic variables to cover new scenarios
Test updates apply to the specific test referenced, so your test suite stays clean and versioned instead of accumulating near-duplicate tests over time.
Multiple Test Scenarios from single calls:
Scenario Tests: Complete conversation workflows
Simulation Tests: Realistic customer interactions
Regression Tests: Ensure quality doesn’t degrade
Edge Case Tests: Handle unusual customer behaviors
@call:abc123 The agent failed to capture the customer's budget and preferred contact method. Add the missing parameters and improve the data collection prompts.
System-wide operations for managing multiple configuration updates:
Accept All in Panel - Apply all suggestions within a specific configuration areaAccept All Changes - Apply all pending suggestions across the entire systemReject All in Panel - Dismiss suggestions within a specific areaReject All Changes - Dismiss all pending suggestions system-wide
System-wide bulk actions affect multiple configuration areas simultaneously. Review individual suggestions across all panels before using “Accept All Changes”.
@call:xyz789 The agent struggled with budget questions, didn't capture contact preferences, and we can't measure success. Set up a complete configuration for this sales agent.
Add comprehensive lead qualification for this real estate agent. Include budget tracking, timeline parameters, property preferences, qualification scoring, and success evaluations.
@call:call1 @call:call2 @call:call3 These calls show the agent needs better appointment scheduling process, missing confirmation parameters, and we can't track booking success rates.
Comprehensive system updates:
Analyzes patterns across multiple call transcripts
Updates prompts for consistent scheduling process
Adds confirmation and calendar integration parameters
Creates appointment booking success evaluations
Suggests test scenarios based on real conversation patterns
@call:perfect123 This was a perfect call where the agent handled all objections and booked the appointment. Create comprehensive tests to maintain this quality.
Intelligent test generation:
Extracts complete conversation flow
Identifies successful objection handling patterns
Creates multiple test scenarios with variations
Sets up quality benchmarks based on the successful call
Includes dynamic variables for different customer personalities
Build sophisticated system improvements through multi-turn conversations:
User: Set up lead qualification for this sales agentCopilot: [Creates input params, output fields, evaluations, and prompt updates]User: Good, but make the budget qualification less aggressiveCopilot: [Refines parameters and prompt approach across affected areas]User: Add follow-up scheduling and CRM integrationCopilot: [Adds scheduling params, webhook configs, and integration tests]User: @call:abc123 Create tests based on this successful callCopilot: [Generates comprehensive test scenarios from call history]User: Update the "Follow-up scheduling" test - we now offer same-day slotsCopilot: [Updates the existing test's chat history and success condition in place]
Copilot maintains conversation context across multiple system modification requests, allowing for iterative refinement of your entire agent configuration through natural dialogue.
Create a professional appointment scheduling agent named "Sarah" with comprehensive lead qualification, appointment booking parameters, success tracking evaluations, friendly but professional greetings,and test scenarios for quality assurance.
@call:abc123 @call:def456 Analyze these problematic calls and optimize the entire agent system - fix the prompts, add missing parameters, create better evaluations, set up proper testing,and generate quality assurance tests.
Set up this agent for CRM integration with Salesforce - add all necessary input and output parameters, webhook configurations, data enrichment instructions, integration success evaluations,and comprehensive test scenarios for the integration workflow.
Our conversion rate is low. Analyze the current setup and improve the qualification process, add better objection handling, create conversion tracking evaluations, optimize output data capture,and generate tests to maintain improved performance.
Test Suite Creation and Maintenance from Call History
@call:perfect1 @call:perfect2 @call:perfect3 These are our best calls.Create a comprehensive test suite based on these successful patterns,and update any existing tests that no longer match current policies.
Review the current audio tags for this customer support agent and adjust them so empathy comes through during complaints without sounding exaggerated anywhere else.
Use the welcome-screen cards for common workflows:
Start with “Diagnose performance” for a comprehensive health check
Use “Find recurring failures” to root-cause quality issues
Click “Create a regression test” to lock in a fix
Try “Improve and verify” to close the loop on a diagnosis
2
Use Comprehensive Natural Language
Describe complete system needs rather than isolated changes:Good: “Set up complete lead qualification with budget tracking, contact preferences, scoring system, success evaluations, and quality assurance tests”Limited: “Add a budget parameter”Comprehensive requests generate coordinated improvements across the entire system.
3
Leverage Real Call Data for System Design
Reference actual calls to drive system-wide improvements:
Use @call:ID syntax to provide specific examples of system gaps
Let Copilot analyze real conversation data across all configuration areas
Address actual problems with coordinated parameter, prompt, and evaluation updates
Generate tests from successful calls, and update existing ones as requirements change
4
Read the Rich Blocks Before Acting
Use stat grids, tables, and charts to validate assumptions:
Check trend indicators in stat grids before deciding what to prioritize
Scan failure tables for patterns rather than reacting to a single call
Use the closing card’s recommendations as your next prompt to Copilot
Ask Copilot directly for a chart or table if a text answer feels hard to scan
5
Review All Affected Configuration Areas
Check every panel with purple notification indicators:
Input Parameters for new data collection fields
Output Settings for enhanced data capture
Evaluations for performance measurement
Basic Settings for core configuration updates
Tests panel for newly generated or updated test scenarios
Prompt for updated audio expressiveness tags
Consider the impact across the entire agent system
6
Think in System Integration Terms
Consider how changes work together across the platform:
New input parameters should have matching output fields
Prompt changes need corresponding evaluation criteria
Output configurations should include proper enrichment instructions
Successful configurations should include test scenarios for quality assurance
Test comprehensive workflows after system-wide changes
7
Use Voice for Complex System Requests
Natural speech excels for describing comprehensive system needs:
“Set up complete sales qualification with lead scoring, CRM integration, and quality tests”
“Based on these three problem calls, optimize the entire agent system with comprehensive testing”
Let conversational input guide holistic system improvements
8
Keep Tests Current Instead of Duplicating Them
Update existing tests as your agent evolves:
Reference an existing test by name to update its conditions instead of creating a near-duplicate
Use test updates after prompt or policy changes to keep your suite accurate
Reserve new test creation for genuinely new scenarios or call patterns
9
Fine-Tune Audio Expressiveness Deliberately
Treat audio tags as part of the prompt, not an afterthought:
Ask Copilot to review tag usage periodically, not just when something sounds wrong
Balance expressiveness so it enhances key moments without becoming distracting
Verify changes by listening to a Playground call after tags are updated
10
Follow Cross-Panel Notification Cues
Purple indicators guide you to all affected system areas:
Check every panel with notification dots
Don’t miss configuration changes in different areas
Review generated or updated tests in the Tests panel
Use seamless navigation to review comprehensively
11
Test System Changes Comprehensively
Validate complete system modifications before deploying:
Test new parameters with real data in Playground
Verify evaluation criteria work with actual conversations
Validate output configurations and webhook integrations
Run generated or updated tests to ensure quality maintenance
Run regression tests across the entire conversation flow
12
Iterate on Complete System Understanding
Build comprehensive agent configurations through dialogue:
Start with high-level system requirements
Refine specific areas through follow-up conversations
Test and adjust system-wide configurations
Generate and refine tests based on real performance
Build understanding of how all components work together