Learning Objectives

Learning objectives allow you to define structured educational goals and detailed instructions that help agents improve their capabilities, learn new skills, and perform better over time.

---

What are Learning Objectives?

Learning objectives are structured learning plans that you assign to agents to enhance their abilities. Think of them as training modules that teach agents specific skills, behaviors, or knowledge areas.

Real-World Example

Scenario: You want your customer support agent to improve at handling complaints

Without learning objectives: The agent relies only on its base instructions and general training.

With learning objectives:

1. Create a "Customer Complaint Resolution" learning objective
2. Add detailed instructions on de-escalation techniques, empathy phrases, and solution frameworks
3. Assign it to your support agent
4. The agent applies these learned behaviors in every conversation

Key Benefits

Benefit	Impact
Enhanced Capabilities	Agents learn specialized skills beyond base training
Consistent Behavior	All agents with the same objective behave similarly
Evolving Knowledge	Update objectives to improve agent performance
Structured Training	Organized approach to agent development
Measurable Progress	Track how agents apply learned concepts

---

Viewing Learning Objectives

Navigate to Learning Objectives to see all your training modules.

List View

The main objectives page displays:

Column	Description
Name	Objective name and description
Instruction Length	How detailed the instructions are (character count)
Type	Comprehensive, Detailed, or Basic
Agents Assigned	How many agents are using this objective
Created	When this objective was created
Updated	Last modification date

Search

Search by objective name, description, or instruction content to find specific learning modules.

---

Creating a Learning Objective

Navigate to Learning Objectives → Create Learning Objective to define a new training module.

Basic Information

Objective Name (required)

• Clear, descriptive name for the learning goal
• Example: Customer Complaint Handling, Product Specification Expert, Empathy in Support Conversations

Description (optional but recommended)

• Brief summary of what this objective teaches
• Example: Teaches agents to handle customer complaints with empathy and effective problem-solving techniques

Instructions

Learning Instructions (required)

• The core content of the learning objective
• Detailed guidance on what the agent should learn and how to apply it
• Can include:
  • Specific behaviors to adopt
  • Knowledge to acquire
  • Techniques to practice
  • Examples of good responses
  • Common mistakes to avoid
  • Decision frameworks

Example instruction structure:

# Customer Complaint Resolution

## Objectives
- De-escalate upset customers
- Demonstrate empathy and understanding
- Provide clear solutions
- Follow up effectively

## Techniques

### Active Listening
1. Acknowledge the customer's frustration
2. Paraphrase their concern to show understanding
3. Ask clarifying questions

### De-escalation
- Use calm, professional language
- Avoid defensive responses
- Focus on solutions, not blame

### Solution Framework
1. Understand the specific issue
2. Offer 2-3 potential solutions
3. Get customer agreement on approach
4. Set clear expectations for resolution timeline

## Example Phrases
- "I completely understand your frustration..."
- "Let me make this right for you..."
- "Here's what I can do to help..."

## Avoid
- Making promises you can't keep
- Blaming other departments
- Using technical jargon
- Rushing to close the conversation

Instruction Complexity Levels

The system categorizes objectives based on instruction length:

Level	Character Count	Use For
Basic	Under 200	Simple behaviors, quick reminders
Detailed	200-500	Standard skills, moderate complexity
Comprehensive	500+	Advanced skills, complex procedures

---

Assigning Objectives to Agents

Single Agent Assignment

1. Go to Agents → [Your Agent] → Edit
2. Scroll to Learning & Development section
3. Click Assign Learning Objective
4. Select the objective from the list
5. Save the agent

Multiple Agent Assignment

From the Learning Objectives list:

1. Click Assign on any objective
2. Select multiple agents from the list
3. Click Assign to Selected Agents

All selected agents will now use this learning objective in their conversations.

---

How Learning Objectives Work

During Conversations

When an agent with learning objectives has a conversation:

1. Agent receives message - User asks a question or makes a statement
2. Objective is applied - Agent considers the learning objective instructions
3. Response is generated - Agent applies learned behaviors
4. Continuous application - Learning is applied throughout the entire conversation

Combining with Agent Instructions

Learning objectives complement (not replace) the agent's base instructions:

• Agent Instructions: Core purpose, role, general behavior
• Learning Objectives: Specialized skills, specific techniques, advanced behaviors

Example:

• Agent: "You are a customer support agent"
• Learning Objective: "Handle complaints using active listening and de-escalation techniques"
• Result: Support agent with specialized complaint-handling skills

Multiple Learning Objectives

Agents can have multiple learning objectives assigned:

• Customer Support Agent with:
  • "Complaint Resolution" objective
  • "Product Knowledge - Premium Tier" objective
  • "Upselling Techniques" objective

All objectives are applied simultaneously during conversations.

---

Editing Learning Objectives

Click on any objective to edit it.

What You Can Edit

Basic Info:

• Name and description

Instructions:

• Add more detail
• Refine techniques
• Update examples
• Correct mistakes

Important: Changes to learning objectives affect all agents currently using them. Updates are applied immediately.

---

Learning Sessions (Future Feature)

Learning sessions are conversation-specific applications of learning objectives. This feature tracks:

• Which objective was applied in which conversation
• How well the agent applied the learned skills
• Progress over time

Note: This feature is planned but not yet implemented. Currently, learning objectives are applied automatically without separate session tracking.

---

Best Practices

Objective Design

Focus on one skill area:

• ✅ "Handling Price Objections in Sales Conversations"
• ✅ "Technical Troubleshooting for Product X"
• ❌ "Everything About Sales and Support"

Be specific and actionable:

• ✅ Include concrete examples
• ✅ Provide decision frameworks
• ✅ List specific phrases to use/avoid
• ❌ Don't write vague generalities

Structure your instructions:

• Use headings and sections
• Number steps in procedures
• Bullet point key concepts
• Highlight examples

Instruction Writing

Good instruction example:

# Empathy in Support Conversations

## Core Principle
Always acknowledge the customer's feelings before solving the problem.

## Technique
1. Listen to the full concern
2. Identify the emotion (frustration, confusion, urgency)
3. Acknowledge it explicitly
4. Then address the issue

## Phrases
- "I can see why that would be frustrating..."
- "That must have been confusing..."
- "I understand the urgency..."

## Example
Customer: "I've been waiting 3 days for a response!"
Bad: "Let me check on that for you."
Good: "I'm sorry you've been waiting. I understand how frustrating that must be. Let me find out what happened and get this resolved right away."

Poor instruction example:

Be nice to customers and help them with their problems. Try to be understanding.

When to Use Learning Objectives

Good use cases:

• Teaching specialized skills (technical support, sales techniques)
• Enforcing company policies or procedures
• Improving consistency across multiple agents
• Addressing common mistakes or gaps

Not ideal for:

• Basic agent behavior (use agent instructions instead)
• One-time information (add to agent knowledge instead)
• Constantly changing information (use knowledge sources)

Naming Conventions

Clear and descriptive:

• ✅ "Product Feature Comparison - Enterprise vs. Pro"
• ✅ "Upselling Techniques - Services Add-ons"
• ✅ "Security Best Practices - Password Reset Flow"

Avoid generic names:

• ❌ "Training Module 1"
• ❌ "Instructions"
• ❌ "Learn This"

---

Measuring Effectiveness

Indicators of Effective Learning Objectives

How to know if an objective is working:

1. Agent behavior changes - Agents start using techniques you defined
2. Consistent responses - Multiple agents respond similarly to similar situations
3. Improved outcomes - Better customer satisfaction, more sales, fewer escalations
4. Fewer mistakes - Agents avoid the pitfalls you warned about

Monitoring Agent Performance

Track these metrics:

• Conversation quality (subjective review)
• Customer feedback
• Goal achievement (sales, resolutions)
• Use of specific phrases or techniques

Review conversations:

• Check if agents apply objective instructions
• Look for areas where agents still struggle
• Identify opportunities to refine objectives

---

Updating Objectives Based on Performance

Iterative Improvement

1. Deploy objective - Assign to agents
2. Monitor conversations - Watch how agents apply it
3. Identify gaps - What's working? What's not?
4. Update instructions - Refine, add examples, clarify
5. Repeat - Continuous improvement cycle

Common Updates

Adding examples:

• Agents aren't applying techniques correctly? Add more examples.

Refining techniques:

• Found a better approach? Update the instructions.

Addressing new scenarios:

• Encountered new customer issues? Add guidance for them.

Removing ineffective content:

• Something not helping? Cut it.

---

Troubleshooting

Agent Not Applying Objective

Check these:

1. Objective is assigned - Verify in agent settings
2. Instructions are clear - Vague instructions = inconsistent application
3. No conflicting instructions - Agent base instructions may override objective
4. Context is appropriate - Objective may not apply to every conversation

Objective Too Complex

Signs:

• Agents seem confused
• Inconsistent application
• Ignoring parts of the objective

Solution:

• Break into multiple simpler objectives
• Reduce instruction length
• Focus on fewer techniques
• Add more examples

Agents Not Improving

Possible causes:

• Instructions are too vague
• Techniques don't match the actual conversations
• Objective not relevant to agent's role
• Conflicting guidance from multiple objectives

Solutions:

• Review actual conversation transcripts
• Refine instructions based on real scenarios
• Remove conflicting objectives
• Simplify and focus on one skill at a time

---

API Integration

Learning objectives use these API endpoints:

List objectives:

GET /api/learning-objectives?sort_by=updated_at&sort_order=desc

Create objective:

POST /api/learning-objectives
{
  "name": "Customer Complaint Resolution",
  "description": "Teaches complaint handling with empathy",
  "instructions": "## Objectives\n- De-escalate upset customers\n..."
}

Update objective:

PUT /api/learning-objectives/{id}
{
  "name": "Updated Name",
  "instructions": "Updated instructions..."
}

Delete objective:

DELETE /api/learning-objectives/{id}

Assign to agent:

POST /api/agent-learning-objectives
{
  "agent_id": 123,
  "learning_objective_id": 456
}

Remove from agent:

DELETE /api/agent-learning-objectives/{id}

---

Examples

Sales Objection Handling

Name: Sales Objection Handling - Pricing

Description: Techniques for handling price objections in sales conversations

Instructions:

# Handling Price Objections

## Core Principle
Never immediately defend the price. First, understand the real concern.

## Framework: ACDR
1. **Acknowledge** - "I understand price is an important factor."
2. **Clarify** - "What specifically concerns you about the pricing?"
3. **Demonstrate** - Show value that justifies the price
4. **Resolve** - Offer solutions (payment plans, ROI calculations)

## Common Objections

### "It's too expensive"
1. Clarify budget range
2. Compare to competitor pricing
3. Calculate ROI over time
4. Offer tiered options

### "I need to think about it"
1. Ask what specifically they need to think about
2. Address those concerns directly
3. Create urgency (limited time offer, slots filling)
4. Schedule follow-up

## Avoid
- Immediately offering discounts
- Apologizing for the price
- Badmouthing competitors
- Pressuring the customer

Technical Support Escalation

Name: Technical Support - When to Escalate

Description: Decision framework for escalating technical issues to specialists

Instructions:

# Escalation Guidelines

## When to Escalate Immediately
- Security vulnerabilities reported
- System-wide outages
- Data loss or corruption
- Legal or compliance issues

## When to Escalate After Troubleshooting
- Issue persists after standard solutions (30+ minutes)
- Requires database access
- Needs code changes
- Affects multiple customers

## Before Escalating
1. Gather all relevant information:
   - Customer account details
   - Error messages (exact text)
   - Steps to reproduce
   - What was already tried

2. Set customer expectations:
   - Explain why escalating
   - Provide timeline estimate
   - Ensure customer knows next steps

## Escalation Template
"I've done some initial troubleshooting, and this issue requires our [specialist team/engineering team] to investigate. I'm going to escalate this to them right away. They'll reach out within [timeframe] with an update. In the meantime, [workaround if available]."

---

Related Features

• Agents - Assign learning objectives to enhance agent capabilities
• Sessions - Review how agents apply learned skills in conversations
• Knowledge - Combine learning objectives with knowledge sources for complete training