Objects
Use Data Model > Objects to inspect standard CRM objects, record types, field counts, and record volume before changing schema.
Use Objects to read the CRM data model: standard objects, record types, field counts, record counts, and where to add new structure.
What Objects is for
Objects is the Admin surface for the CRM data model. It shows the standard business objects Frontline uses for customer memory: Tickets, Deals, Companies, and People.
The captured state expands Companies, showing its Companies record type, 20 fields, 18 records, and the Add new record type action.
What each control changes
Search records filters the object list. Create object starts a custom object when Tickets, Deals, Companies, and People do not cover the business entity. Standard badges identify built-in objects.
Expanding an object reveals record types. The field count tells you how much structured data the record type can store; the record count tells you whether the model already has live data behind it.
Operational outcome
Objects make customer memory reliable. Workflows and agents can only read, route, and update the fields that exist in the schema.
Operational playbook
Start with the standard object that owns the work: People for contacts, Companies for accounts, Deals for revenue, Tickets for support or operations.
Add a field when a workflow or agent needs to read or write that value. Add a record type when the same object needs a different process shape. Create a custom object only when the concept is not a person, company, deal, or ticket.
Best practices
Use Objects for durable CRM memory. Use Studio Tables for reference data, lookup lists, routing rules, imports, or temporary operational datasets.
Before changing schema, list the workflows, agents, imports, and CRM views that will read the field. Schema changes should make automation easier to verify, not harder.
Troubleshooting
If a workflow receives empty data, confirm the field exists on the right object and record type. Then check the record itself and the workflow logs.
If operators cannot find a record, confirm whether the data belongs in an existing object, a new record type, or a Studio Table instead of creating another custom object.
FAQs
What does Objects control?
Objects defines the CRM data model: the record families, record types, fields, and records that agents and workflows can reference.
Who should use this page?
Admins, implementation owners, and builders who decide what customer data must exist before workflows or agents depend on it.
How should this page fit into onboarding?
Use it to confirm the schema first: which object stores the data, which record type applies, and which fields workflows need to read or update.
What should I verify before using this in production?
Check which workflows, agents, reports, imports, and CRM views depend on the object before adding, renaming, or deleting schema.