People relationship context
Use People records to understand contact identity, ownership, related company, deals, tickets, and activity before follow-up.
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.
Use this product state to inspect customer memory: record identity, relationships, activity, and context that AI or workflows may depend on.
Summary
Use People records to understand contact identity, ownership, related company, deals, tickets, and activity before follow-up.
Concepts covered
Step breakdown
- Open PeopleStart in the People area and confirm what the real screen is showing.
- Inspect product behaviorUse screenshots and visible product states to understand what the screen does, why it exists, and how teams use it.
- Connect the platformSee how the screen connects to agents, workflows, records, activity, channels, integrations, or ownership.
What a People record tells you about the contact
A People record holds contact identity (name, email, phone, role), ownership (assigned teammate), relationship links (connected company, deals, tickets), and conversation history.
Max uses this to understand who the contact is before drafting outreach or deciding what to suggest. A person with no company link, no owner, or no conversation history will produce vague AI output.
Relationship links that matter
Each person should be linked to their company if one exists. This lets Studio workflows retrieve account-level context when operating on a person — for example, checking whether the account already has an open deal before routing a new inquiry.
Tickets and deals should also link back to the person so resolution history and revenue motion connect to the right contact.
Ownership and routing
The owner field on a People record determines who Max presents follow-up tasks to and which teammate a workflow assigns work to.
Keep ownership current. If a contact transfers to a new rep, update the owner field immediately — otherwise AI will surface tasks to the wrong person and workflows may route incorrectly.
Activity shaping what AI does next
Max reads a person's conversation history and activity log when generating context for the next action. Recent conversations tell Max what was said; tasks tell it what was agreed; stage changes tell it where the relationship stands.
Before drafting an email, generating a summary, or suggesting a next step, Max uses People context to ground the response. Sparse activity means generic output. Rich activity means contextual output.
Operational playbook
Use People relationship context as part of the Frontline CRM People 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.
FAQs
What does People relationship context teach?
Use People records to understand contact identity, ownership, related company, deals, tickets, and activity before follow-up.
How should teams use this lesson?
Use it as a product walkthrough: understand the real screen, the product behavior, the operational outcome, and how the area connects with the rest of Frontline.
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.