CRM overview
Use Spacebrain CRM as the shared record for leads, contacts, companies, deals, ownership, and customer activity.
The CRM connects customer identity with conversations, opportunities, tasks, automations, and AI-assisted work. Its main views are Dashboard, Leads, Deals, Pipelines, People, Companies, Custom Fields, Lead Scoring, and AI Copilot.
Choose the right record
- Lead: an individual or organization being qualified or worked through a lead process.
- Person: a durable individual contact record.
- Company: an organization that can relate to people and commercial activity.
- Deal: an opportunity with a stage and pipeline context.
Your workspace may use all four or a simpler subset. Agree on lifecycle definitions before importing data; inconsistent definitions create duplicate counts, confused ownership, and unreliable automation.
Recommended CRM setup order
- Define the lifecycle and record types your team will use.
- Create only the custom fields needed for routing, qualification, personalization, or reporting.
- Configure a default pipeline and its stages.
- Add a small set of test people, companies, and leads.
- Configure ownership and lead-scoring rules.
- Test inbox, form, enrichment, workflow, and sequence updates against those records.
- Import production data in controlled batches.
Daily operating loop
Start from CRM → Dashboard for current workload and trends, then use saved views or filters to find records requiring action. Each active record should have an owner, clear next step, and current status. Conversations belong in Inbox; tasks should capture commitments; deal stages should reflect observable progress rather than optimism.
AI Copilot
Configure workspace-level Copilot behavior under Settings → AI Copilot. Treat generated summaries, suggestions, and drafts as assistance, not the system of record. Review customer-facing content and never allow a suggestion to silently override ownership, consent, suppression, or an approved policy.
CRM quality checklist
- Required identity fields have clear definitions.
- Duplicate-search behavior is understood before import.
- Every live record has an accountable owner or queue.
- Stages and scores have written criteria.
- Consent and source data survive imports and enrichment.
- Automations use stable fields instead of free-form notes.
- Dashboard totals can be traced to underlying records.
Continue with records and imports, deals and pipelines, and custom fields and lead scoring.