← Insights
Product
CX Library: start every playbook from a template that works
Dongmei Hu
Updated

Today we’re launching the CX Library: templates built from real support conversations, adapted to your business by Vela, our AI Assistant. They come from our work running Emily, Level3AI’s customer service AI agent, for businesses in mobility, loyalty platforms, e-commerce and consumer hardware.
A template helps you start fast, but on its own it’s only text. With the CX Library, Vela does the rest alongside your team:
Launch faster. Start from a template built from real customer conversations, not a blank page.
Fit it to your business without manual setup. Describe how your team works in your own words, and Vela adapts the template to your systems and policies.
Safeguards from day one. They’re built in, so Emily never tells a customer something is done before your system confirms it.
Keep improving after launch. Vela reviews how Emily is doing and suggests the next fixes, following best practices from the teams already running Emily.
Stay in control. Nothing goes live until your team approves it.
The CX Library has three categories of templates: Playbook, Workflow and Skill. Vela uses all three to build and run Emily for your business.
Each template shows how it works, what it needs from your systems and what to adapt to your business. Here’s what each category does:
Playbook templates: what Emily does for each type of request
A playbook is the step-by-step procedure Emily follows for one kind of customer request, such as checking an order or troubleshooting a product, written in plain language. It sets out what to ask, which actions she can take, and the business criteria for each scenario.
Workflow templates: the actions behind each step
A workflow is a fixed set of steps Emily must follow, in order, to get one task done, such as verifying a customer or crediting a refund. Each step is spelled out: which system to check, what to ask if a detail is missing, and how to confirm the result. Playbooks call a workflow whenever a task has to be done the same way every time.
Skill templates: best practices for your ops team
A skill is a best-practice method Vela follows to help your ops team, from turning your handbook into your first playbooks to testing changes and spotting what to fix after launch.
Each skill carries the know-how of an experienced ops team. The Weekly Performance Review skill template, for example, won’t draw conclusions from a CSAT score based on a handful of survey replies alone, where one or two unhappy customers can swing the result. Instead, it reads the conversations behind the score, groups the root causes and recommends next steps by impact.
Built-in safeguards
Playbook and workflow templates come with safeguards we learned from real customer conversations across those industries, so your team has them from day one. Here are the five most common:
Emily says an action is done only after your system confirms it.
She asks the customer to confirm anything that can’t be undone, and acts only on a clear yes.
If one detail is missing, she asks for that detail and nothing else.
She guides the customer through troubleshooting steps one at a time, and skips any they’ve already tried.
When she hands off to a person, she passes on a short recap, so the customer doesn’t have to start again.
Each template includes the safeguards its scenario needs.
Imagine a support team at a company that sells robot vacuums. One of their most common requests: a vacuum that won’t go back to its dock. The team already knows the troubleshooting steps. Here’s how they’d get Emily handling it, using the CX Library.
Pick. Your team chooses a template from the CX Library in the Emily Portal: in this case, Conduct Guided Troubleshooting.
Fit. Choose Use With Vela and describe how your team handles it, in your own words: “Check the dock has power, clean the charging contacts, then restart the robot. If it still won’t dock, hand off to the warranty team.” Vela matches the template to your setup. It links every piece of data the flow needs to your APIs, such as the product model or order details, along with a way to mark the problem as solved, a running note of the steps already tried, and the team to hand off to. It creates anything that’s missing and builds in what’s different in your process.
Approve. Your team reviews what Vela fitted, with the before and after side by side. Vela tests the change first, and nothing goes live until your team approves and publishes it.

Here’s how it plays out. A customer writes: “It won’t go back to its dock. I’ve already wiped the contacts.” Emily confirms the problem, then suggests checking the dock’s power. It’s fine. She skips the contacts and offers the restart. Still broken. So she hands off to the warranty team, with what was tried.

Copying a template was never the hard part. Adapting it to your business and keeping it working is, and that’s what Vela is for.
Pick your busiest request type, whether that’s returns, order status or troubleshooting, and we’ll show you a template adapted to your process in one walkthrough. You don’t need to be an Emily client.
Prefer to look around first? Browse the templates without an account.
Written by
YOUR WORKFLOW / YOUR RULES
Request access







