CRM overview
Understand CRM as the customer memory layer behind records, relationships, context, workflows, AI agents, and operational reporting.
Use this product state to inspect customer memory: record identity, relationships, activity, and context that AI or workflows may depend on.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Record identityRelationship contextActivity evidenceUse this product state to inspect customer memory: record identity, relationships, activity, and context that AI or workflows may depend on.
Record identityRelationship contextActivity evidenceThis is the state to compare against when the system is configured, connected, or ready for review.
Summary
Understand CRM as the customer memory layer behind records, relationships, context, workflows, AI agents, and operational reporting.
Concepts covered
Step breakdown
- Understand recordsLearn how people, companies, deals, and tickets preserve operating context.
- Connect relationshipsUse relationships so customer context is available to workflows and agents.
- Operationalize memoryUse CRM context inside solutions, workflow routing, and Max summaries.
What CRM is
CRM is the operational memory of Frontline. It stores the customer records, relationships, ownership, and structured context that AI agents and workflows need in order to act responsibly.
Use the overview before entering record types so users understand why People, Companies, Deals, Tickets, Objects, and Relationships form one context layer.
System diagram
Operational examples
A lead reply updates a Person, connects the Company, creates or updates a Deal, and gives a Studio workflow the structured context it needs to route follow-up.
A support conversation checks open Tickets before an AI agent replies, so the customer experience reflects history instead of starting from zero.
Operational playbook
Use CRM overview as part of the Frontline CRM Overview operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
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.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
Validated CRM behavior
The real CRM surface lives under Work / Records with object routes such as People, Companies, Deals, and Tickets. People and Companies use list-style record tables; Deals and Tickets use pipeline columns for stage-based work.
Learning content should show the controls users actually see: List or Pipeline, Filter, visible-field counts, Actions, Add, row links, field columns, stage totals, and calculations.
Customer context checklist
Before acting on a customer, review the person or company, related deals or tickets, recent activity, ownership, and any workflow or Max-generated context.
The strongest CRM habit is relationship-first review: understand how the record connects before deciding what should happen next.
Transcript
Open searchable transcript
FAQs
What is CRM overview?
Understand CRM as the customer memory layer behind records, relationships, context, workflows, AI agents, and operational reporting.
Why start with this overview?
The overview explains how this product area works before users enter a specific screen walkthrough or implementation blueprint.
How does this connect to the Frontline ecosystem?
Each overview shows how Studio, CRM, Max, Channels, AI agents, workflows, and Activity connect into one operating system.
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.