Company account context
Use Companies to understand account-level history across people, deals, tickets, conversations, and workflows.
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 Companies to understand account-level history across people, deals, tickets, conversations, and workflows.
Concepts covered
Step breakdown
- Open CompaniesStart in the Companies 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 Company record contains
A Company record holds account identity (name, industry, size, domain), linked people, connected deals, open tickets, and activity across all of them.
It is the account-level view — not just a single contact's history, but the entire relationship between the organization and your team.
Why account-level context changes decisions
Before prioritizing an inbound request, a workflow or teammate should check whether the account has an active deal, an open ticket, or a recently escalated issue.
A new inquiry from a company mid-deal should be routed differently than one from a cold account. Company context is what makes that routing decision possible.
How Studio uses Company records
Studio workflows can look up a Company record to retrieve account-level context during execution — checking deal stage, open tickets, or recent activity before deciding how to handle a new event.
For this to work reliably, People records must be linked to their companies and tickets must be associated with the right account. Orphaned records break the account view.
Keeping account context current
Stale Company records produce stale AI output. If a company's deals, tickets, and people are not being updated through Frontline activity, the account view is a snapshot from months ago.
Audit Company records by looking at activity recency. If the last logged event was six months ago, either the relationship has gone cold or work is happening outside of Frontline — both are worth addressing.
Operational playbook
Use Company account context as part of the Frontline CRM Companies 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 Company account context teach?
Use Companies to understand account-level history across people, deals, tickets, conversations, and workflows.
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.