Editor

The editor is where you build a conversation: a canvas of connected nodes that runs your flow. Conversations can be pushed as a voice channel, or an SMS channel (coming soon).

Anatomy of the editor

Open any conversation to edit it. The workspace has a few key regions:

Node types

Every flow is built from a small set of nodes. Combine them to handle anything from a one-line autoresponder to a multi-branch, AI-routed call.

Trigger

Every flow starts with exactly one Trigger. It decides how and when a conversation begins, who it reaches (the Audience, one or more contact groups), and the organization phone number it runs on. Pick a trigger type from Trigger Details:

Question

A Question node asks the contact something and branches on their reply. Open Question Details and pick a question style. Both share a few fields:

Final Statement

A Final Statement delivers a closing message and ends that branch of the conversation: a confirmation, a thank-you, or a hand-off line. Open Statement Details to configure it:

Action

An Action runs an operation mid-flow: call an API, update a contact, request a payment, or send an SMS. Open Action Details and choose one of four action types:

Variables & context

The editor exposes two kinds of values you can reference with @ mentions: variables, which the flow captures as it runs, and context, which comes from the contact.

Variables

A variable holds a value the conversation captured, typically a Question's answer. In a Question node, set Save answer as to name the variable; reference it later as @variable.<name>.

# Question node - "Save answer as":
visited_or_trained

# Later, reference the captured answer:
@variable.visited_or_trained
@variable.visited_or_trained.intent

Use an Action node to persist a variable to a contact field: pick Update contact, choose the Field, and set its Value to a @variable.… mention.

Context

Context is what Pindo already knows about the contact: their name, phone number, and any custom field you've defined. Reference it with @contact.<field>:

Muraho @contact.name! Ombi ryawe ryakiriwe.
Uzamenyeshwa kuri @contact.phone.

Build your first workflow

We'll build a simple loan intake: a call comes in, the contact is welcomed and asked a question, and each answer routes to a closing message.

Publish & publications

Publishing snapshots the current draft as a version and routes live traffic to it. The previous version keeps running until the moment you publish, so there's no downtime.

Choose a publishing channel

Hit Publish and Pindo asks how the conversation should interact with users:

Pick a channel and click Continue. Pindo runs through a short Publishing sequence (Preparing to publish, Compiling conversations, Optimizing for selected channel, and Finalizing deployment), then the version goes live.

Conversation states

A conversation can be in one of four states:

The Publications tab

Open the Publications tab (next to Editor) to see how each published version is performing. A metric dropdown (e.g. Calls) sets what the summary cards count.

The Conversations table lists each published version:

Each row's ⋮ menu lets you manage that version: pause or resume it, and review its deployment.