Contacts, people and organizations
How os.construction's CRM separates working contacts from the company's relationship graph of people and organizations, where intake ends and project CRM begins, and when to merge versus mark the same identity.
Partly in the app today. Items marked Planned are not built yet.
On this page
The CRM has three kinds of “who” record. Knowing which is which explains most of the questions people have: why a contact moved into a project, why the same person shows up twice, and why “merge” and “same identity” are different buttons.
Three records, three jobs
| Record | What it is for | Where it lives | Has opportunities and follow-ups? |
|---|---|---|---|
| Contact | A working relationship you are pursuing or serving: the facilities director on this pursuit | Company intake, or inside one project after handoff | Yes |
| Person | The human being, once, across every job: name, email, phone, affiliations, communication preferences | Company relationship graph | No, it links to contacts |
| Organization | The firm, once: name, website, phone, the people affiliated with it, its roles on projects | Company relationship graph | No |
Contacts carry the work. Opportunities, follow-ups and service cases hang off a contact. A contact also has a relationship (lead, client, partner, subcontractor) and a relationship owner.
People and organizations carry identity. They don’t move when work moves. A contact can be linked to its Master person with Save person link. People get affiliations to organizations (“Facilities Director at Harbor Point Dental Group”), and an organization can hold a project stakeholder role on a job.
None of these records give anyone a login. People in the CRM are relationship records, not users.
Intake versus project CRM
A contact sits in exactly one place:
- Company intake: before there is a project. Visible to members with a Company CRM grant.
- A project’s CRM tool: after Attach to project or Review new project moves it. It then follows that project’s CRM permissions and leaves intake.
When a contact moves, its opportunities and activities move with it, keeping their IDs and history. The linked person and organization stay where they are in the company graph. That’s why the graph can show one person’s history across several jobs. See Turn a lead into a project.
The two scopes don’t grant each other: a project CRM permission doesn’t show you intake, and an intake grant doesn’t show you project records. The relationship timeline on a person or organization shows project entries only for projects where you can see CRM.
Merge versus “same identity”
Duplicates happen: an inquiry and an import both create Maria Lopez. There are two tools, and they do different things.
| Merge into… (contacts) | Mark as same identity (people, organizations) | |
|---|---|---|
| Use when | Two working contacts are the same relationship | Two graph records are the same person or firm |
| What happens | Opportunities, activities and service cases move to the kept contact; blank details are filled from the merged one; the merged contact is archived | Nothing moves or is deleted. The duplicate points to its primary, and both show together on the timeline |
| Undo | Not from the app | Undo resolution |
| Who | Contact edit access | Company CRM edit access |
Duplicate suggestions are clues only: people match on the same email or name, and organizations on the same website domain or name. Suggestions show at most 25 records, so use Find another primary record to search when you know a match exists.
When you create a contact by hand, an exact email match, or the same name at the same organization, shows a warning with Create anyway. It doesn’t block you, because two people can share a name.
What the timeline shows
Open a person or organization to see its Relationship timeline, newest first.
- Person: linked contacts, opportunities, activities, proposal revisions, affiliations and identity events (created, updated, duplicate resolved or undone, preference recorded).
- Organization: affiliations, project stakeholder roles and identity events.
Opportunity stage changes are not timeline entries. They live in the opportunity’s forecast history.
Communication preferences are evidence, not consent
A person’s Communication preferences record what you know about email and SMS for marketing, project updates and service: Permission evidenced, Blocked or Unknown, with a source and evidence. Entries are appended, never overwritten. A current Blocked on any linked identity wins. The CRM does not send marketing email or SMS, and a recorded permission is a staff record, not a legal finding.
Common mistakes
Mistake: Creating a new organization for every contact
In the app: Search Organizations first, then add an affiliation. The contact's organization text field does not link to the organization record on its own.
Mistake: Merging contacts to fix a duplicate person
In the app: If only the person record is doubled, mark the same identity instead. It is reversible and moves nothing.
Mistake: Expecting a stakeholder role to add someone to the project team
In the app: Project stakeholder roles are relationship data. They don't grant project access.
Mistake: Treating Unknown as permission to email
In the app: Unknown means nothing is recorded. Only current evidence counts, and messaging has its own compliance rules.
Terms on this page
Single source of truth · Audit trail · Lead conversion rate · Row-level security
Related
- See it in context: CRM for contractors.
- The full screen-by-screen reference: Construction CRM guide.
- Next step: Import your contacts from another CRM.
Keep exploring
Related across os.construction
- DocsImport your contacts from another CRMPrepare a CSV, map the columns, review every row and create company intake contacts with a receipt. Plus what the import will and won't do, and how to export contacts back out.
- GlossaryRow-Level SecurityFiltering data row by row so each person sees only the records they're allowed to see, in every report and query.
- GlossarySemantic Layer (Metric Catalog)A governed list of business metrics, each defined once with its formula, unit and allowed groupings, that every dashboard and query reads from.
- DocsHow agents workPlanned. What AI agents in os.construction would do, what they could read, how they would propose work, and why a human would approve every action.
- BlogAgents with approvals: our approach to AI in the back officeAI in construction accounting goes wrong in two ways: chatbots that know nothing about your jobs, and autopilots that post entries nobody checked. Our model is an apprentice with a supervisor. Here are the rules.
- BlogWhy construction needs an operating system, not another appMost contractors don't have a software problem. They have a seams problem: the same number lives in five systems and none of them agree. The fix is a shared record, not another tool.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →