parley
DocsPlatform
Resources
JournalIdeas on running AI supportCustomer storiesHow teams use ParleyGuidesStep-by-step playbooksChangelogWhat shipped, by versionHelp centerAnswers and support
CustomersPricing
LoginGet started
DocsPlatformCustomersPricingJournalCustomer storiesGuidesChangelogHelp center
Get startedLogin

Take charge of your AI customer experience

Get startedTalk to sales

Platform

Platform overviewChannelsPlaybooksIntegrationsAnalyticsPricing

Resources

DocumentationGuidesCustomer storiesJournalChangelogHelp center

Company

AboutCareersContact salesContact supportTerms of servicePrivacy

Security

Trust centerSOC 2ISO 27001GDPRHIPAAData processing
parley

© Parley. All rights reserved.

Docs home

Get started

Quickstart

Build your agent

PlaybooksChannelsKnowledgeActions

Developers

Parley CLICustom codeAPI keysWebhooks

Test and ship

TracesSplit testingSimulations
All docs
Docs home

Get started

Quickstart

Build your agent

PlaybooksChannelsKnowledgeActions

Developers

Parley CLICustom codeAPI keysWebhooks

Test and ship

TracesSplit testingSimulations
Docs/Build your agent

Playbooks

A playbook is a plain document that describes how one kind of conversation should go. Support leads write them; the agent follows them.

Anatomy of a playbook

  • Goal: one sentence on what a good outcome looks like.
  • Rules: things that must always or never happen, whatever the customer says.
  • Steps: the order your best people work in, with the actions they use.
  • Triggers: example messages that should start this playbook. Parley suggests more as conversations come in.

References

Type @ to reference a knowledge source or an action inline. References are checked every time you save, so a renamed action or a deleted policy shows up as an error before it reaches a customer.

Flows inside a playbook

Some moments need an exact path, like refunds over a threshold or identity checks. Insert a flow block and draw the branches; the agent follows the flow without improvising, then returns to the playbook when the flow ends.

text
flow refund_exception
  if order.total > 100 -> handoff(team: "Returns leads", note: true)
  else -> action(issue_refund, amount: order.total)

Working with Scout

Scout, the build assistant, reads your playbook alongside recent conversations and suggests clearer wording, missing steps and rules that conflict. Suggestions arrive as tracked changes you accept or reject.

Versions

Every save creates a version with an author and a note. Compare any two versions side by side, or push a version to a test environment with split testing.

PreviousQuickstartNextChannels

Something unclear?Contact supportor browse thehelp centerAll guides

On this page

Anatomy of a playbookReferencesFlows inside a playbookWorking with ScoutVersions