Studio overview
Understand Studio as the operating builder for Frontline: agents, workflows, channels, integrations, tables, resources, logs, analytics, and publishing controls.
Connect the screen to the operation it controls: customer signal, agent behavior, workflow path, channel, CRM context, and review outcome.
Connect this setup to an outcome.
Identify what is configured, which data enters, which action it produces, and where to verify it before publishing.
Connect the screen to the operation it controls: customer signal, agent behavior, workflow path, channel, CRM context, and review outcome.
Summary
Understand Studio as the operating builder for Frontline: agents, workflows, channels, integrations, tables, resources, logs, analytics, and publishing controls.
Concepts covered
Step breakdown
- Map the operationWrite the channel, trigger, data source, AI decision, CRM update, and final output for one sample use case.
- Open each Studio surfaceInspect Agent Builder, Workflow Builder, Channels, Tables, and Integrations so you know where the operation belongs.
- Trace the sample pathFollow the operation from incoming event to log, analytics, and published state.
- Choose the next builderMove to Agent Builder for AI behavior or Workflow Builder for automation logic.
What you will build
You will build a practical map of Studio so you can decide where to configure an AI agent, where to automate a process, where channel events enter, and where operational data should live.
By the end, you should be able to trace one Frontline operation from a channel signal to a workflow run, CRM update, agent response, and Max Activity entry.
When to use it
Use this overview before creating your first production flow or when you inherit a workspace and need to understand which Studio surface owns each part of the operation.
Studio is the right starting point when the work involves agents, workflow logic, channel routing, API integrations, reusable tables, resources, logs, or publish controls.
Before you start
Choose one operation to inspect, such as qualifying a WhatsApp lead, routing a support question, updating a Deal, or notifying a teammate after a handoff.
Confirm you have access to Studio and permission to view agents, workflows, channels, tables, and integrations in the workspace.
Step-by-step implementation
Open Studio and scan the left navigation: Agent Builder for AI behavior, Workflow Builder for automation logic, Channels for WhatsApp, Instagram, and Messenger entry points, Tables for reusable operational data, and Integrations for API or webhook connections.
Open an existing agent and identify its role, instructions, connected resources, workflows, channels, and analytics.
Open an existing workflow and identify the trigger, each action node, routing logic, logs, analytics, and Draft or Live state.
Open Channels and confirm which messaging surfaces are connected or ready to connect.
Open Tables and Integrations only after you know what data or external system the workflow needs.
How to verify it worked
Pick one sample operation and explain where each part lives: the incoming channel, the workflow trigger, the AI agent or logic node, the CRM record update, the log entry, and the final user-facing or teammate-facing output.
If you cannot point to logs, analytics, or the current publish state, keep the operation in review before treating it as launch-ready.
Common mistakes
Do not start by editing a workflow before you know the trigger and expected output.
Do not put long-term customer memory in a Studio Table when it belongs in CRM People, Companies, Deals, or Tickets.
Do not publish an agent or workflow just because the screen looks complete; verify the sample path and the failure path first.
Troubleshooting
If the operation does not run, check the channel connection, trigger configuration, Draft or Live state, and workflow logs in that order.
If the AI response is generic, inspect the agent instructions and confirm the workflow is passing the right CRM or table context.
If the output is correct but no teammate can see it, check Max Activity, assignment, and notification steps.
Clear next step
Open Create an AI agent next if your operation depends on AI behavior. Open Build a workflow next if you already know the trigger and need to automate the path.
Operational playbook
Build this as a small deliverable: define the trigger, source data, owner, expected output, and the exact place the team will review it.
For Studio overview, keep the first version narrow enough that a teammate can test it end to end before expanding it into a broader Overview system.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.
Transcript
Open searchable transcript
FAQs
Is Studio only for workflows?
No. Studio includes agents, workflows, channels, tables, resources, integrations, logs, analytics, and publishing controls.
Where should customer memory live?
Use CRM for durable customer records and relationships. Use Studio Tables for operational reference data that agents or workflows need to read or update.
How do I know an operation is ready?
You can explain the trigger, context, routing, output, logs, analytics, and current Draft or Live state without guessing.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.