PearlVibe

PearlVibe is a powerful AI-assisted flow editor that allows you to design and visualize conversation flows in a user-friendly, visual interface. Whether you’re creating customer surveys, support dialogues, or interactive voice responses, PearlVibe helps you craft natural and personalized conversations.

Overview

What is PearlVibe?

PearlVibe is an AI‑assisted flow editor for building your agents - both voice (phone) and text agents. You build your Pearl as a decision tree made of nodes (dialogue, actions, integrations…) and transitions (what happens next depending on user intent, answers, or conversation outcome).

You can work in two complementary ways:

Mode	Description
Chat (default)	You describe changes in natural language to Ask Pearl (e.g. “Add a post‑call SMS when the booking is confirmed”) and Pearl Vibe creates or edits the nodes and transitions for you.
Manual Edit	You open Manual Edit on the selected node to configure it and its transitions yourself, for full control. Every setting is visible and editable.

What can you build with PearlVibe?

With PearlVibe, you can design both voice (phone) and text (chat) flows:

Flow Type	Use Cases
Inbound flows	Support and customer care lines, order tracking, FAQs, triage, appointment management, etc.
Outbound campaigns	Sales campaigns, payment reminders, debt collection, upsell flows, satisfaction surveys, and more.

Each of these works the same way whether your Pearl is voice or text — you build the flow once, and the editor adapts labels and available nodes to your Pearl’s channel.

Key benefits

Build in minutes instead of days – Use the chat to describe what you want, then refine visually.
Safe versioning – Work in a separate version with autosave while your Published version keeps running in production.
Visual understanding of calls – Use test calls and live node highlighting to see exactly how calls traverse your flow.
Structured but flexible – Combine high‑level “vibes” (global instructions, personality) with precise node and transition logic.

The header is always visible at the top of the editor. From left to right, it holds the Pearl icon (menu) and the editable Pearl title with its autosave indicator, the version selector, the top navigation tabs, and — on the right — the credentials & variables ({ }) button, Test Call, and Publish. Each of these is detailed below.

PearlVibe header bar with title, version selector, and top-right controls

Pearl Title & Menu

The top-left corner shows the Pearl’s title as an inline, editable field (it reads Untitled Pearl by default). Click it to rename your Pearl — this is the label you’ll reuse across the platform and in your workspace. Just below, an autosave indicator shows the save status (for example Saved 2 min ago).

Inline editable Pearl title with autosave indicator

Pearl menuThe Pearl icon next to the title opens a menu with quick actions for the whole Pearl.

From this menu you can go back to the Dashboard or Overview, open the Pearl’s Settings, Duplicate or Delete the Pearl, check your Credit Balance, switch the Theme, and reach the Documentation or Support & Feedback.

Pearl menu with dashboard, settings, duplicate, delete, credit balance, and theme options

Versioning & Publishing

Pearl Vibe is built for safe iteration: you can experiment freely without breaking your live calls. Your work is organized into versions (v1, v2, v3…), and the one currently handling calls carries a Published badge.AutosaveEvery change you make is saved automatically. The header shows an Auto Save indicator that turns into Saved N min ago once your edits are stored, so you never lose work and can come back later.

Versions & historyThe version selector next to the title shows the version you’re editing (for example v35).

Version selector next to the Pearl title

Open it to browse the full version history. You can search for a version, see when each was last edited, spot the Published one at a glance, and open any past version to review it. You can also tag each version with a label of your own so it’s easy to recognize later (e.g. “stable”, “summer promo”, “before refactor”).

Version history dropdown with a Published badge on the live version

Creating a new versionUse the + button next to the version selector to create a new version.

In the Create New Version dialog, pick the existing version to use as the base, then click Create.

Editing a version that is already Published automatically creates a new version for your changes, so the live configuration keeps running untouched while you iterate.

PublishingWhen you’re satisfied with your changes and tests, click Publish (top-right of the header). The current version becomes the new Published version and starts handling calls.

If your flow still has unresolved issues, the Publish button is replaced by an Errors & Tasks (N) button until you fix or dismiss them (see the Tasks & Errors section below).

Credentials & Variables Managers

Credentials and variables are what connect your Pearl to the rest of your stack. Both are opened from the { } button in the top-right of the header.Variables ManagerThe Variables Manager lets you create, edit, and organize the variables used in your conversation flows.

Variables Manager to create, edit, and organize variables

See the Variables documentation for more details.

Credentials ManagerThe Credentials Manager is where your integrations live: you connect external systems by adding credentials and configuration for each one. Once a credential is added, the matching integration becomes available as a node in your flow.

Credentials Manager to connect external systems

It lets you:

Add new integrations (e.g. Salesforce, HubSpot, ticketing tools, booking engines).
Configure authentication.

Tasks & Errors

As your flows grow, PearlVibe helps you keep them valid, connected, and fully configured.

Error detectionPearl Vibe automatically scans your Pearl for common issues, such as:

Nodes without outgoing transitions.
Transitions not connected to any node.
Missing required fields (for example: API nodes without an endpoint or description).
Incomplete campaign or flow configuration.

When such issues are detected, the Publish button in the header is replaced by a red Errors & Tasks (N) button that signals how many items need your attention.

Tasks & Errors panelClicking the Errors & Tasks button opens a right-hand Tasks & Errors panel that groups every issue in one place, organized per workspace (Flow Editor, credentials, etc.). Each card names the affected node and what’s missing (e.g. “Missing Transition: Budget provided”, “Missing Inbound Transition”).

Tasks & Errors panel listing issues per node

Each card offers two actions:

Fix With Pearl — let the agent propose and apply the corrected configuration for you.
Open in editor — jump directly to the affected node in the Flow Editor.

Selecting an issue card in the Tasks & Errors panel

On the canvasAffected nodes are highlighted in red, and the problem is flagged directly in the node’s Transitions section, so you can spot exactly what needs attention.

Node flagged with a missing transition error on the canvas

You can also fix an issue from the node itself: hovering a node reveals a quick Fix With Pearl action.

You can either fix issues manually or let Pearl draft and apply the corrected configuration for you.

Test Calls & Debugging

Test calls are the safest way to validate your Pearl before and after publishing.

On text Pearls, these controls read Test Chat and Past Chats instead of Test Call and Past Calls.

Launching a Test CallOpen the Test Call menu in the header. From here you switch between the two views: Test Call (test your agent by phone) and Past Calls (view your call history and details).

Test Call menu to switch between Test Call and Past Calls

In the Test Call panel, choose the From and To phone numbers, optionally reset the Pearl’s memory for a fresh test, prefill opening sentences and lead variables, then click Call Now. The Pearl calls that number using the version you’re currently editing.

Test Call panel with phone numbers, lead variables, and Call Now button

Live Node TracingDuring the test call, a Ringing… / Stop Following pill appears and the nodes in the canvas light up one after another as the conversation progresses, so you can visually follow the path the call is taking through your flow.

Live node tracing during a test call with a Stop Following pill

This helps you understand why a certain question was asked, see which transition was taken at each step, and debug misrouted calls or unexpected behaviors.

Past CallsThe Past Calls view lists your previous test calls grouped by date. Open any entry to inspect its details and verify that your flow — including post-call automation — behaved as expected.

Past Calls panel listing previous test calls by date

To learn more about post-call actions, see the Post-Call documentation — or, for text Pearls, the Post-Chat documentation.

The chat sidebar is where you build your Pearl — either by talking to PearlVibe in natural language to create and edit your flow, or by switching to Manual Edit to configure things by hand.

It combines two complementary views:

View	Description
Chat (Ask Pearl)	Describe changes in natural language and let Pearl build them. This is the default view.
Manual Edit	Explicit, hands-on configuration of the selected node.

All actions in this sidebar always apply to the node currently selected in the flow editor (unless explicitly noted as global, like General Instructions).

Chat (Ask Pearl)

Ask Pearl chat panel in the left sidebar

This is the default view. You design and update the flow by describing changes in natural language, and Pearl builds them into your current version.Typical operations you can perform:

Operation	Example
Create or delete nodes	”Add a qualification step after the greeting.”
Edit a node’s content and behavior	”Make the opening more formal and mention our summer offer.”
Add, rename, or reconnect transitions	”Add a ‘Not interested’ branch that ends the call politely.”
Attach actions	”Send a confirmation SMS after a successful booking.” (API calls, SMS, email, transfers, etc.)
Configure post-call logic	”Log the outcome to the CRM once the call ends.”

The composerType your instruction in the Ask Pearl… box — for example: “Split this node into three outcomes based on payment status.”, “After a successful payment, send a confirmation SMS and end the call.”, “Create a post-call node that logs the outcome to the CRM.” Press Send and the editor updates in real time.

The composer includes a few helpers:

Attach files — add supporting material (FAQs, pricing sheets, policy docs, playbooks…) to enrich the Pearl’s knowledge and reference it in node prompts.

Accepted formats: .pdf, .docx, .txt, .jpg, .jpeg, .png, .webp, .gif, .mp3, .m4a, .wav, .webm — up to 10 files per message.

You can attach a full recording of a real conversation (e.g. an .mp3 or .wav call) and ask PearlVibe to build the flow from it — it will turn the exchange into nodes and transitions for you.

Enhance prompt — rewrite a rough or short instruction into a clearer, more structured request before it runs.

Voice input — dictate your instruction instead of typing it.

Node contextWhen a node is selected in the canvas, its name appears as a pill above the composer. Any instruction you send while this pill is active is interpreted in the context of that node (for example: “Change the greeting”, “Add a failure transition that transfers to support”).

Node context pill above the Ask Pearl composer

Reviewing what Pearl buildsBefore applying larger edits, Pearl often shows a short plan and asks you to confirm (Yes, build it) or answer directly.

Pearl asking to confirm before building changes

When Pearl needs a decision, it can present interactive choices right in the chat (for example, which CRM to connect).

Interactive choice prompt in the Ask Pearl chat

Once applied, each batch of edits appears as a Changes card summarizing what was added and removed.

Expand it (View more) to see the full diff — added, edited, and removed nodes and transitions, highlighted in green and red.

If you don’t want to keep a batch, click Undo changes to roll it back.

Chat is the recommended entry point to quickly build or refactor a flow, especially for large or complex trees.

Manual Edit

Select a node in the canvas, then click the Manual Edit button at the bottom of the sidebar to configure it by hand.

Manual Edit always targets the currently selected node (shown by the node context pill).

Manual Edit with a node selected in the canvas

It is split into two tabs: Edit and Transitions.The Edit tabExposes all the settings specific to the current node type (Script / Free Text, Instructions, variables…). What you see here changes depending on whether the node is a Dialogue, API, SMS, Email, Transfer, Integration, or Post-Call node.

In short, the Edit tab is where you configure what this node does internally, based purely on its type.

Routing to other nodes is not handled here, but in the Transitions tab.

The Transitions tabDefines how the conversation can exit this node. Each transition is a labeled branch (for example “Agreed to future contact”) pointing to the next node, and you add new ones with New Transition.

Transitions tab in Manual Edit with a transition and the New Transition button

From here you can:

Create transitions – Add exits such as “Success”, “Failure”, “No answer”, “Customer asks for human”, etc.
Connect transitions – Choose the target node for each transition to shape the path of the conversation.
Edit or delete transitions – Rename transitions, change their destination, or remove them when they are no longer needed.

Back to ChatWhen you’re done, click Back to Chat to return to the Ask Pearl view.

Any modification done in Manual Edit is immediately reflected in the visual flow and remains fully understood by Pearl.You can freely switch between Chat (Ask Pearl) and Manual Edit as you work on the same node.

Central Canvas

The central canvas displays your flow as a graph of nodes and transitions.

Element	Description
Nodes	Each node represents a step in the conversation (a message, an action, or a set of actions).
Transitions	Each transition represents a possible path from one node to another based on intents, recognition results, or business logic.

From the canvas you can:

Action	Description
Add, connect, branch, disconnect	Create nodes and wire transitions to shape the flow.
Move, pan & zoom	Navigate large trees comfortably.
Search	Find a node by name or content.
Reorganize	Re-lay out the flow automatically (auto-layout).
Go to Start / End	Jump straight to the beginning or end of the flow.
Hover preview	See a quick summary of what a node does.
Quick actions	Fix, Edit, Duplicate, or Delete a node in place.
Undo / Redo	Roll your latest changes back and forth.

The canvas has no minimap — use zoom, pan, Reorganize, and Search to move around instead.

Right toolbar The vertical toolbar on the right groups the navigation controls: Undo / Redo, Go to Start / End, Reorganize (auto-layout), and Zoom in / out.

Right toolbar with undo/redo, go to start/end, reorganize, and zoom

Node Types Overview

Pearl Vibe supports several node types:

Node Type	Description
Start node	Entry point of the flow.
In‑Call nodes	Actions that occur while the caller is on the line.
Integration nodes	Interactions with external systems (CRM, ticketing, booking…).
End Call node	The node that ends the conversation.
Post‑Call nodes	Actions executed after the call has ended.

Understanding Node Types: Pre-Call, In-Call & Post-CallYour Pearl flow is built around three categories of nodes, each designed for a specific moment in the call lifecycle. Knowing the difference is essential to avoid misusing an action or expecting behavior that can’t happen at that stage.1. Pre-Call Nodes: Before the call startsThese nodes run prior to dialing or answering. They’re ideal for preparing context: fetching customer data, checking availability, validating an ID, loading account information. They cannot interact with the caller and cannot create or import leads.2. In-Call Nodes: During the conversationThese nodes control everything that happens while the caller and the agent are connected. Dialogue, decision logic, sending SMS/emails, API calls, and CRM updates all happen here in real time. This is the core of your conversational flow.3. Post-Call Nodes: After the call endsOnce the call is finished, these nodes handle asynchronous tasks: writing CRM logs, creating leads, triggering webhooks, updating databases, or launching follow-up workflows. They cannot affect what happened during the call, only what happens after.

Start Node

Every flow begins with a Start node. It controls how the conversation is initiated.

You can configure it in two ways:

Configuration	Description
Opening sentence	A standard greeting and first question, for example: “Hi, you’ve reached [Company]. How can I help you today?”
Pre‑Call API	Before the Pearl speaks, it can call an external API (for example to fetch order details, check account status, or pre‑qualify the caller). The API response can then change the opening sentence, route the caller toward different branches, or preload variables and context. On text Pearls this is labeled Pre‑Chat API.

The Pre-Call API cannot be used to import leads into your Pearl. Its purpose is strictly to enrich or prepare contextual data before the call starts

In‑Call Nodes

In‑Call nodes represent the actions and dialogues that happen during the conversation. In the Add Node picker they’re split into Live Global Nodes (Dialogue, Knowledge Base) and Live Action Nodes (SMS, Email, API, Transfer Call).

Node Type	Description
Dialogue	The Pearl speaks, listens, and interprets the customer’s response according to your instructions.
Knowledge Base	Answer questions using your Pearl’s configured knowledge base.
Send SMS	Send a text message during the call (e.g. a confirmation code, a link, or a summary). Voice only — hidden on text Pearls.
Send Email	Trigger an email to the customer or your team.
API	Call an external API (e.g. update a record, check availability, create a ticket).
Transfer Call	Transfer the caller to a human agent or another phone number. Voice only — hidden on text Pearls.
Hand-Off	Hand the conversation over to a human. Text Pearls only.
Recording	Control call recording (availability depends on your platform).

Integration-specific actions (e.g. Google Calendar, Salesforce) appear in a separate Integration Nodes group of the picker — see below.

Integration Nodes

Integration nodes let your Pearl interact directly with external tools and services without writing any API code yourself. Technically, each one is an API node pre-configured with an integration credential from the Credentials Manager — it handles authentication, request formatting, and data mapping for you. They appear in a dedicated Integration Nodes group of the Add Node picker.

Integration node configured from a credential

Integration node variants:

Variant	Description
In-Call Integration Nodes	Executed while the caller is still on the line (e.g. checking a CRM record before answering).
Post-Call Integration Nodes	Executed after the call ends (e.g. logging call results into a ticketing system).

What Integration Nodes DoIntegration nodes encapsulate tasks such as:

Category	Examples	Tasks
CRM operations	Salesforce, HubSpot, Pipedrive…	Create or update records, attach call results, sync contact data.
Helpdesk platforms	Zendesk, Freshdesk…	Create tickets, update statuses, push conversation summaries.
Booking engines	Calendly, Cloudbeds, Shore…	Check availability, create reservations, cancel or modify bookings.
Search & data services	Algolia, Elasticsearch…	Query product/catalog data, validate inputs, or retrieve structured info.
Payments & billing	Stripe, Paystack…	Check payment status, initiate a payment link workflow, validate customer identity.
Custom Integrations	Any configured integration	Any integration you configure in the Credentials Manager becomes available here as a dedicated node.

How They Work

Feature	Description
Secure Credentials	The Credentials Manager stores credentials securely (API keys, tokens, IDs…).
Available as Node	Once connected, each service becomes available as a node in the flow.
Simple Configuration	The node exposes only the required parameters, no API documentation or coding needed.
Data Mapping	Returned data can be mapped to variables and used later in the conversation.

Available Integrations

ActiveCampaign

Airtable

Algolia

Anthropic

AssemblyAI

Backblaze

Baserow

Bitly

Brevo

Cal.com

Calendly

Clearbit

ClickUp

Cloudflare

Cohere

Contentful

Convertkit

Customer.io

Datadog

DeepL

DigitalOcean

Discord

Elasticsearch

Freshdesk

Ghost

Google Calendar

Google Docs

Google Sheets

Grafana

Groq

Hetzner

HubSpot

HuggingFace

Hunter

InfluxDB

JotForm

Lemlist

Magento

MailerLite

Mailgun

Mailjet

Mandrill

Matrix

Mattermost

MessageBird

Metabase

Microsoft Outlook

MinIO

Mistral AI

Mocean

MongoDB

MQTT

MSG91

MySQL

Netlify

New Relic

NocoDB

OpenAI

OpenRouter

OpenWeatherMap

Pabbly

Paddle

PagerDuty

Perplexity

Pinecone

Plivo

PostHog

PostgreSQL

Postmark

Pushover

Qdrant

RabbitMQ

Redis

Replicate

Rocketchat

Salesforce

SendGrid

Sendy

Sentry

Serp

SIGNL4

SparkPost

Square

Stability AI

Strapi

Supabase

Together AI

Twilio

Typeform

Vercel

Vonage

Wasabi

Weaviate

WooCommerce

WordPress

Wufoo

Yourls

Zulip

End Call & Post‑Call Nodes

End Call nodeThis node closes the conversation gracefully (e.g. “Thanks for your time, goodbye.”). It is typically the last in‑call node. On text Pearls it’s labeled End Chat.

Post‑Call nodesAfter the End Call node, you can add Post‑Call nodes via transitions. These nodes execute actions after the call has ended, such as:

Sending a summary SMS.
Writing a detailed log into your CRM.
Triggering a webhook.
Sending internal notifications to your team.

Post‑Call nodes support many of the same actions as In‑Call nodes but are not constrained by real‑time conversation. In the Add Node picker, the Post-Call tab offers SMS, Email, and API nodes.

Node Structure

Each node shares a common structure.Header

Icon representing the type of node.
Node name, editable to reflect its role (“Payment check”, “Qualification”, “Post‑call CRM update”…).

Node header with type icon and editable name

Transitions listUnder the header, you see the list of transitions for this node (e.g. “Success”, “Failure”, “No match”, “Ask for human”). From here you can:

See which node each transition points to.
Click to navigate along the transition.
Disconnect or reconnect transitions to reshape the flow.

A node's transition branches listed under its header

Quick actionsSelecting a node reveals quick actions right below it — Edit, Duplicate, and Delete.

Node colors when selectedWhen you select a node, the canvas colors the surrounding nodes to show their position relative to it:

Border color	Meaning
Blue	Nodes that come before the selected node.
Green	The selected node (the current one).
Orange	Nodes that come after the selected node.

Selected node with blue (previous), green (current), and orange (next) node borders

Hover popoverWhen you hover a node in the canvas, a preview card shows a short summary of what it does — its main instruction or script, key actions, and transitions.

Bottom tools

The toolbar at the bottom of the canvas groups three controls.

Tool	Description
Add Node	Open the node picker to browse and insert new nodes into the flow.
General Instructions	Open a modal to define global guidance for the whole flow.
Search	Search across all nodes by name or content and jump directly to the node you need.

Add Node

The Add Node picker is organized by moment in the conversation — Pre-Call, In-Call, and Post-Call tabs (labeled Pre-Chat / In-Chat / Post-Chat on text Pearls) — and, within a tab, by group:

Tab	Addable nodes
Start	Opening Sentence or Pre-Call API (Pre-Chat API on text).
In-Call	Live Global Nodes: Dialogue, Knowledge Base — Live Action Nodes: SMS, Email, API, Transfer Call, Hand-Off (text only), Recording.
Post-Call	SMS, Email, API.
Integration	Dynamic integration nodes — an API node pre-filled with an integration credential from the Credentials Manager.

Add Node picker with Pre-Call, In-Call, and Post-Call tabs and node groups

*On text Pearls, SMS and Transfer Call are hidden from the picker, while Hand-Off is available only on text. Post-call SMS remains available for both.

General InstructionsThe middle button opens General Instructions, a modal where you define global guidance for the whole flow — persona, tone, strategy, and guardrails. These act as a “meta prompt” layered on top of individual nodes.

General Instructions modal with global flow guidance

Search

The top navigation switches between the main workspaces of your Pearl. Flow Editor is the PearlVibe editor covered on this page; the other tabs configure your Pearl’s identity, knowledge, analytics, and campaign behavior.

Pearl Settings

Set your agent’s name, language, voice, personality, and timezone.

Knowledge Base

Give Pearl the company context and knowledge it needs to answer accurately.

Analytics

Define success, apply indicator tags, and track your Pearl’s performance.

Inbound Settings

Configure how your Pearl answers incoming calls.

Outbound Settings

Configure how your Pearl runs outbound campaigns.

Getting Started

General

Pearl Voice

Pearl Text

Settings

Overview

What is PearlVibe?

What can you build with PearlVibe?

Key benefits

Header

Chat Sidebar

Central Canvas

Top Navigation tabs

Pearl Settings

Knowledge Base

Analytics

Inbound Settings

Outbound Settings

​Overview

​What is PearlVibe?

​What can you build with PearlVibe?

​Key benefits

​Header

​Chat Sidebar

​Central Canvas

​Top Navigation tabs

Pearl Settings

Knowledge Base

Analytics

Inbound Settings

Outbound Settings

Overview

What is PearlVibe?

What can you build with PearlVibe?

Key benefits

Header

Chat Sidebar

Central Canvas

Top Navigation tabs