Studio Automation

Studio is Teloring's visual automation builder. It lets admins create flows that react to customer messages, conversation changes, schedules, webhooks, CRM updates, and other events.

Use Studio for repeatable workflows such as first-response bots, routing, follow-up reminders, CRM updates, webhook integrations, and AI-assisted customer journeys.

Studio list

Open Studio from the sidebar to see your flows.

The list page includes:

Control	Use it to
New flow	Create a new automation.
Search	Find a flow by name.
Status filters	Show all, draft, live, or paused flows.
Flow cards	Open, review, delete, or manage existing flows.

Flow basics

A Studio flow is made of blocks connected on a canvas.

Block type	What it does
Trigger	Starts a flow when an event happens.
Condition	Chooses a path based on rules.
Action	Performs work, such as replying, assigning, updating CRM data, or sending an HTTP request.
Wait/reply step	Pauses until the customer answers, then continues with the new message.
End session	Ends Studio ownership and optionally resolves the conversation.

Common triggers

Studio supports several trigger types, including:

Trigger	Example use
Incoming message	Start a bot when a customer sends a message to a selected inbox.
Conversation changed	React when status, assignment, priority, labels, flag, or other conversation fields change.
Customer changed	React when a customer is created or edited.
Customer record changed	React when a custom CRM object record is created, edited, or deleted.
Agent status changed	React to online/offline presence changes.
Interval	Run a flow every defined number of minutes, hours, or days.
Specific time	Run a flow on a weekly schedule in a selected timezone.
Incoming webhook	Start a flow from an external system using a unique webhook URL.

Common actions

Common action blocks include:

Action	Example use
Reply message	Send a customer-facing message in the active conversation.
Private note	Add an internal-only note for agents.
Conversation update	Assign, prioritize, label, resolve, or otherwise update a conversation.
Contact update	Update contact fields.
Customer record	Create or update CRM object records.
HTTP request	Send data to an external system.
Code	Transform data in a sandboxed JavaScript block.
Datetime	Calculate or format dates for later blocks.
Save as variable	Store a flow-scoped variable for future runs.

Draft, publish, and live behavior

Studio separates editing from production:

State	Meaning
Draft	Canvas changes are being edited and are not yet used by live conversations.
Published/live	The flow version that production events can run.
Paused	The flow is not currently active.
Version history	Saved snapshots that can be previewed and restored.

Click Publish when the edited flow is ready to become the live runtime version.

warning

Publishing affects real customer conversations when the trigger conditions match. Test with a safe inbox or demo conversation before publishing important flows.

First flow example

A simple starter flow:

1. Add an Incoming message trigger.
2. Configure the inbox or conditions that should start the flow.
3. Add a Reply message action with a short greeting.
4. Add a condition that checks the customer's answer.
5. Route matching answers to the right team or next message.
6. Add End session when the bot should hand control back to agents.
7. Publish after testing.