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/Test and ship

Split testing

Split testing lets you ship a change to some customers first. Parley compares resolution, satisfaction and hand-offs between versions, then you promote the winner.

Environments

Every project starts with a main environment that serves customers. Create test environments from main, make changes there, and run simulations before any customer sees them.

Starting a split

Choose a test environment and the share of traffic it should receive. Start small, around 10%, and raise it as results come in. A customer stays on the same version for the whole conversation.

bash
parley split start returns-v2 --share 10 -p "$PROJECT"
parley split status -p "$PROJECT"

Reading results

The split view shows resolution rate, CSAT, hand-off rate and cost per conversation for each version, with how confident the difference is. Parley won't call a winner until there are enough conversations to be sure.

Promote or roll back

Promoting copies the test version into main for everyone. Rolling back sends all traffic to main straight away; nothing is lost and the test environment stays in place for another try.

PreviousTracesNextSimulations

Something unclear?Contact supportor browse thehelp centerAll guides

On this page

EnvironmentsStarting a splitReading resultsPromote or roll back