A playbook is the basic building block of generative agents. A generative agent typically has many playbooks, where each playbook is defined to handle specific tasks. The playbook data is provided to the LLM, so it has the information it needs to answer questions and execute tasks. Each playbook can provide information, send queries to external services, or defer conversation handling to a flow or another playbook to handle sub-tasks.
Limitations
The following limitations apply:
- Agents that use playbooks don't support sending a call companion SMS from the Default Welcome Intent route in the Default Start Flow, but you can enable the call companion SMS option in standard flows.
Language support
Playbooks support the same languages as Gemini models.
Region support
Playbooks are supported in the following regions:
globalasia-south1asia-southeast1asia-northeast1australia-southeast1eu(multi-region)europe-west1europe-west2europe-west3northamerica-northeast1us(multi-region)us-central1us-east1us-west1
Playbook data
A playbook is composed of the following data:
- Playbook name: a concise name in natural language that helps developers and the LLM to understand what tasks the playbook handles
- Goals: high level description of what the playbook should accomplish
- Instructions: defines the process steps that should be taken to accomplish the goal
- Examples: sample conversations that are effectively few-shot prompt examples for the LLM
- Parameters: are used to store information about a conversation like user input, user system information, results of actions, and so on.
Default playbook
When you create a generative agent using Conversational Agents console, a Default Generative Playbook is created automatically.
The default playbook is the starting point for conversations, so it has some important distinctions from other playbooks:
- The default playbook doesn't receive a summary of preceding conversation turns.
- The default playbook can't define or receive input parameters.