Playbooks
Use Studio Playbooks as reusable instruction sets that tell agents when to act, what instructions to follow, and which tools, integrations, system tools, tables, or custom tools they can use.
Use this Studio state to connect the product UI to a real business operation: customer signal, agent behavior, workflow path, channel, CRM context, and review outcome.
Summary
Use Studio Playbooks as reusable instruction sets that tell agents when to act, what instructions to follow, and which tools, integrations, system tools, tables, or custom tools they can use.
Concepts covered
Step breakdown
- Open ResourcesStart in the Resources area and confirm what the real screen is showing.
- Inspect product behaviorUse screenshots and visible product states to understand what the screen does, why it exists, and how teams use it.
- Connect the platformSee how the screen connects to agents, workflows, records, activity, channels, integrations, or ownership.
Validated product behavior
The live Playbooks module opens inside Studio and currently shows an empty state: Agent Playbooks, Save proven instructions once and reuse them across agents, All, and Create playbook.
The Create Playbook panel exposes the fields that matter operationally: When to use, Instructions, Select tools, Integrations, System tools, Tables, Custom tools, an Enabled switch, and Save.
Why playbooks matter
A playbook is not another generic content page. It is a reusable operating instruction set that can be attached to agents so behavior stays consistent across repeated business moments.
Use Playbooks when the same job appears across customers, channels, or workflows: ticket creation, payment links, candidate sourcing, pipeline updates, presentations, bid monitoring, or location assistance.
System diagram
Business request -> When-to-use rule -> Playbook instructions -> Tool or table context -> Agent action -> Workflow or Max Activity
Operational setup loop
First write the When to use rule so the agent knows the exact situation. Then write instructions as a repeatable operating procedure. Finally attach the tool, table, integration, or custom action that lets the agent complete the job.
The Tools module validates the action side of this model: Create Custom Tool asks for Tool name, When to use, and Tool type. Tables validate the structured data side with existing Contacts, Subscribers, Qualified Leads, and Retargeting tables.
Operational playbook
Use Playbooks as part of the Frontline Studio Resources operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Playbooks teach?
Use Studio Playbooks as reusable instruction sets that tell agents when to act, what instructions to follow, and which tools, integrations, system tools, tables, or custom tools they can use.
How should teams use this lesson?
Use it as a product walkthrough: understand the real screen, the product behavior, the operational outcome, and how the area connects with the rest of Frontline.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.