Record relationships
Understand how relationships connect people, companies, deals, tickets, and custom objects into usable context.
Inspect the customer memory that work depends on: record identity, relationships, activity, ownership, and recent context.
What relationships are in Frontline CRM
A relationship is a link between two records. A Person belongs to a Company. A Deal is connected to a Person and a Company. A Ticket is connected to a Person and possibly a Deal. These links are not just display annotations — they are the paths Frontline uses to retrieve context, power workflow logic, and generate AI summaries.
Without relationships, CRM is a collection of isolated rows. With relationships, it is a graph that answers questions like: 'Which tickets belong to this company's contacts?' or 'Which deals is this person involved in?'
The core CRM relationship structure
How relationships are used by AI and workflows
When an AI Agent receives a WhatsApp message with a phone number, it looks up the Person, then follows the relationship to the Company, active Deals, and open Tickets — assembling full context before generating a response.
When Max generates a pre-meeting brief, it starts from the meeting attendees' Person records, follows relationships to their companies and deals, and includes the complete account picture in the summary.
When a workflow needs to update the account-level record after a conversation, it follows the Person → Company relationship to write the update in the right place.
Broken relationships and their consequences
A Person without a Company relationship means account-level context is inaccessible. A Deal without connected People means no individual can be attributed as the contact for follow-up. A Ticket without a Person means the support request has no customer attribution.
These gaps produce silent failures: AI summaries that omit account context, workflows that skip CRM updates because the lookup returned empty, and activity entries with no record attribution. Check relationships as part of any CRM data quality review.
Why relationships matter
Relationships connect records into usable context: a person belongs to a company, a company has deals, a deal can produce tasks, and tickets can affect customer health.
Relationships are retrieval paths for both humans and AI. They tell Frontline which context should travel with a workflow, summary, or action.
How to check relationship quality
Open the record and verify the links that should travel with the work: person to company, deal to company and people, ticket to customer, and related activity.
If a workflow or Max output feels generic, check relationships before changing prompts. Missing links usually mean missing context.
FAQs
What is a relationship in Frontline CRM?
A relationship is a link between records, such as a person connected to a company, a deal connected to contacts, or a ticket connected to the customer who opened it.
How do CRM records connect to workflows?
CRM records provide structured customer context that Studio workflows and Max assistance can reference, update, summarize, or route around.
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.