CRM overview
Understand CRM as Frontline customer memory: People, Companies, Deals, Tickets, relationships, activity history, workflow context, and operational reporting.
Inspect the customer memory that work depends on: record identity, relationships, activity, ownership, and recent context.
Summary
Understand CRM as Frontline customer memory: People, Companies, Deals, Tickets, relationships, activity history, workflow context, and operational reporting.
Concepts covered
Step breakdown
- Inspect CRM objectsReview People, Companies, Deals, and Tickets and identify which object owns the operation.
- Open a sample recordCheck relationships, owner, fields, activity history, and linked work.
- Trace workflow contextConfirm which fields a workflow or AI agent should read or update.
- Verify the outcomeUse sample data to confirm updates attach to the right record.
What you will build
You will build a working map of CRM objects and relationships so workflows and agents use the right customer context instead of disconnected notes.
The outcome is a clear distinction between durable customer memory in CRM and temporary operational data in Studio Tables.
When to use it
Use CRM when the operation depends on customer identity, company relationships, pipeline state, support history, ownership, or activity history.
CRM should be reviewed before an AI agent responds with customer context or a workflow updates a record.
Before you start
Choose one sample customer journey to trace, such as new lead, active deal, open ticket, or returning support contact.
Use demo contacts and sample company records for Academy review. Do not publish customer lists, private emails, phone numbers, billing details, workspace IDs, or production conversation text.
Step-by-step implementation
Open CRM and inspect the main objects: People, Companies, Deals, and Tickets.
Open a Person record and check ownership, company relationship, activity history, linked deals or tickets, and fields used by workflows.
Open a Company record and confirm related people, account context, and active work.
Open Deals or Tickets to understand stage-based operational work and what a workflow should update.
Trace where Max Activity, workflow logs, and channel events should attach to the customer record.
How to verify it worked
A sample operation should show the right person, company, deal or ticket, owner, activity, and related workflow output.
If the agent or workflow cannot find the right context, review object relationships and field names before changing prompts.
Common mistakes
Do not duplicate customer context in Studio Tables when CRM already owns the record.
Do not let workflows write to fields that the operating team does not understand.
Do not test public Academy material with production contact details.
Troubleshooting
If records do not link correctly, check relationship fields and object names.
If a workflow updates the wrong record, inspect lookup rules and sample payload variables.
If an AI answer misses context, confirm the workflow passes the correct CRM fields into the agent step.
Clear next step
Trace one sample journey from channel message to CRM record to workflow output, then decide whether the next change belongs in CRM, Studio Tables, or Workflow Builder.
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 CRM 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.
How to read CRM screens
CRM lives under Work / Records. People and Companies use list-style tables; Deals and Tickets use pipeline columns for stage-based work.
Start with the visible controls: List or Pipeline, Filter, visible-field counts, Actions, Add, row links, field columns, stage totals, and calculations.
Before acting on a record
Before acting on a customer, review the person or company, related deals or tickets, recent activity, ownership, and any workflow or Max-generated context.
If the record is connected to a workflow, make sure the owner, status, relationship fields, and required values are current before the workflow reads or updates it.
Transcript
Open searchable transcript
FAQs
What belongs in CRM?
Durable customer memory: people, companies, deals, tickets, relationships, owners, fields, and activity history.
What belongs in Studio Tables?
Operational reference data such as routing rules, product tiers, scoring thresholds, or other automation support data.
How do agents use CRM?
Workflows can pass relevant CRM context into an agent step so the agent can answer with the right customer memory.
How do CRM records improve AI workflows?
CRM records give Max and Studio shared customer memory: identity, relationships, deals, tickets, activity, and context that workflows can retrieve, summarize, update, or route around.
When should I create a relationship between records?
Create relationships when context should travel together: a person belongs to a company, a deal depends on contacts, a ticket affects customer health, or a workflow needs related records.
What should I check before changing the data model?
Check which workflows, summaries, views, and teammates rely on the field or relationship. Schema changes should preserve operational context and avoid breaking automation.
How should teams handle duplicate or incomplete records?
Prioritize records that affect active work. Merge or clean duplicates when they confuse ownership, customer context, workflow routing, or AI-generated summaries.
What makes CRM context trustworthy?
Trust comes from clear ownership, current activity, useful relationships, well-defined fields, and visible history. AI suggestions should point back to this structured context.