Create a table
Create and manage Studio Tables for small operational datasets such as candidates, FAQs, pricing plans, lead logs, routing rules, and workflow lookup data.
Connect the screen to the operation it controls: customer signal, agent behavior, workflow path, channel, CRM context, and review outcome.
What the Tables screen shows
Studio > Tables lists operational datasets. Cards can represent data such as Candidates, FAQ, Pricing Plans, Lead Log, Contacts, Subscribers, Qualified Leads, or Retargeting. Each card shows field count, created date, owner, and an action menu.
The screen also includes search, list/grid view controls, sidebar shortcuts, and the Create table button. Before adding a new table, check whether an existing one already covers the same operational job.
Create a table
Use Create table, choose an icon, and give the table a name that explains the work: Lead Log, Pricing Plans, FAQ, Candidates, or Routing Rules.
Start small. A good first table has a few fields, demo rows, and a clear owner before it is connected to workflows or agents.
What to put in a table
Use Tables for operational reference data: approved FAQs, pricing references, routing rules, qualification criteria, temporary process state, allowed values, or simple process logs.
Use CRM when the information is durable customer memory: people, companies, deals, tickets, ownership, relationships, and history.
Use it without breaking operations
Where the configuration supports it, a table can help a workflow or agent with lookup, routing, enrichment, scoring, logging, or handoff.
Test with demo rows, review the workflow result, and agree who can edit fields or rows. A table change used by automation can change live operational behavior.
Transcript
Open searchable transcript
FAQs
When should I use a table instead of CRM?
Use a table for small operational or reference data. Use CRM for durable customer memory, ownership, relationships, deals, tickets, and history.
What are good first examples?
Approved FAQs, Pricing Plans, Lead Log, Routing Rules, qualification criteria, option lists, or demo data for testing a workflow.
Why keep the first schema small?
A table connected to automation becomes part of operational behavior. Fewer fields and a clear owner make it easier to test, review, and change.