Kibo.AgenticAdmin

Playbook Configuration

Overview

Playbooks are the heart of your agent’s conversational intelligence. They define how the agent responds to user inputs, what actions it can take, and how conversations flow from one topic to another.

Playbook Concepts

What is a Playbook?

A playbook is a structured set of instructions that guides the agent’s behavior in specific scenarios. Think of it as a conversational script with:

Playbook Components

┌─────────────────────────────────┐
│      PLAYBOOK STRUCTURE         │
├─────────────────────────────────┤
│ 1. Basic Information            │
│    - Display Name               │
│    - Goal Description           │
├─────────────────────────────────┤
│ 2. Instructions                 │
│    - Hierarchical Steps         │
│    - Conditional Logic          │
│    - Tool/Playbook References   │
├─────────────────────────────────┤
│ 3. Parameters                   │
│    - Input Parameters           │
│    - Output Parameters          │
├─────────────────────────────────┤
│ 4. References                   │
│    - Used Playbooks             │
│    - Required Tools             │
└─────────────────────────────────┘

Creating Playbooks

Playbook Editor

Step 1: Basic Information

Display Name

Goal

Example:

Goal: Guide customers through product discovery by understanding their 
needs, showing relevant products, and helping them add items to cart. 
Maintain a friendly, helpful tone while being efficient and accurate.

Step 2: Writing Instructions

Instructions use markdown-style hierarchical lists to define conversation flow.

Basic Structure

- Greet the user
- Ask what they're looking for
- If searching for products:
  - Use ${TOOL:Natural Language Search Tool}
  - Display results
  - Ask if they want more details
- If checking order:
  - Transfer to ${PLAYBOOK:Order Status Agent}
- Thank the user

Advanced Patterns

Conditional Logic

- Understand user intent
  - If product-related:
    - Ask for specific preferences
    - Search inventory
  - If order-related:
    - Get order number
    - Check status
  - If general question:
    - Provide helpful information
    - Offer to connect to support

Tool Integration

- Get user's search query
- Call ${TOOL:Product Search API} with query
- Process results:
  - If products found:
    - Display top 5 results
    - Use ${TOOL:Render Product Card Tool}
  - If no products:
    - Apologize
    - Suggest alternatives

Multi-step Flows

- Step 1: Collect Information
  - Get user name
  - Get email address
  - Confirm contact details
- Step 2: Process Request
  - Validate information
  - Create support ticket
  - Send confirmation
- Step 3: Follow Up
  - Provide ticket number
  - Explain next steps
  - Offer additional help

Step 3: Parameter Configuration

Input Parameters

Define data the playbook expects to receive:

Parameter Type Description Example
firstName string Customer’s first name “John”
email email Customer’s email “john@example.com”
orderId string Order number “ORD-12345”
searchQuery string Product search terms “blue running shoes”

Output Parameters

Define data the playbook will return:

Parameter Type Description Example
productIds array Selected product IDs [“P123”, “P456”]
nextAction string Recommended next step “checkout”
satisfaction number User satisfaction score 8.5

Step 4: Testing and Validation

  1. Save the playbook
  2. Test with various inputs
  3. Verify tool calls work correctly
  4. Check parameter passing
  5. Validate conditional logic

Playbook Management

List View Features

The playbook list provides comprehensive management capabilities:

Playbooks List

  1. Sorting and Filtering
    • Alphabetical order (default)
    • Token count (complexity)
    • Last modified date
    • Usage frequency
  2. Bulk Operations
    • Export multiple playbooks
    • Batch delete
    • Clone playbooks
  3. Quick Actions
    • Edit: Modify playbook
    • Delete: Remove playbook
    • Set Start: Make primary playbook

Start Playbook

One playbook must be designated as the “start” playbook:

Token Management

Token count indicates playbook complexity:

Tips for optimization:

Advanced Features

Dynamic References

Tool References

${TOOL:toolName}

Playbook References

${PLAYBOOK:playbookName}

Parameter Inheritance

When transferring between playbooks:

Error Handling

Built-in error handling patterns:

- Try to process request
  - If successful:
    - Continue with next step
  - If error:
    - Apologize to user
    - Offer alternatives
    - Log error for review

Best Practices

1. Playbook Design

Single Responsibility

Clear Naming

Modular Structure

2. Instruction Writing

Be Specific

User-Centric

Maintainable

3. Testing Strategy

Comprehensive Testing

Real-World Scenarios

Iterative Improvement

Common Patterns

Welcome Flow

- Greet user warmly
- Introduce yourself and capabilities
- Ask how you can help
- Route to appropriate playbook based on response

Search and Discovery

- Understand search intent
- Gather requirements
- Execute search
- Present results
- Offer refinement options

Transaction Flow

- Confirm user intent
- Collect required information
- Validate data
- Process transaction
- Provide confirmation

Support Flow

- Understand issue
- Gather relevant details
- Attempt resolution
- Escalate if needed
- Follow up

Troubleshooting

Common Issues

  1. Playbook Not Triggering
    • Check if set as start playbook
    • Verify references are correct
    • Test input parameters
  2. Tool Calls Failing
    • Verify tool exists and is active
    • Check parameter formatting
    • Review tool permissions
  3. Unexpected Behavior
    • Review instruction logic
    • Check conditional statements
    • Verify parameter passing

Debug Tips

  1. Use agent testing to trace execution
  2. Add logging steps for debugging
  3. Test individual components separately
  4. Review conversation history for patterns

Migration and Version Control

Exporting Playbooks

Importing Playbooks

Version Management