New Leads
Track inquiries from the website, phone, referrals, events, walk-ins or other sources.
Leads • Customers • Follow-Ups • Tasks • Communication History
A CRM should help the business remember what happened, what needs to happen next, and who is responsible. The goal is not to collect as many fields as possible. The goal is to keep customer and lead information organized enough that sales, service and follow-up do not depend on one person's memory.
CRM features vary by platform. Before choosing software, verify user permissions, integrations, data export, communication capabilities, automation limits and ownership of the business's customer data.
Start with a clean contact record, a small number of useful lead/customer statuses, clear ownership, and one place for notes, tasks and communication history. Every open lead or service issue should have a next action, an owner and a date. Keep the system simple enough that staff will actually use it.
Main Principle
Notes are useful, but a business still loses opportunities when nobody knows who should follow up or when. The best CRM process turns customer history into an assigned next step.
Step 1
Do not start by creating dozens of custom fields. Start with the workflows that the business needs to control.
Track inquiries from the website, phone, referrals, events, walk-ins or other sources.
Track what the customer is interested in, the stage of the conversation and the next action.
Keep contact information, services/products, important notes and relationship history organized.
Track unresolved questions, promised callbacks, service issues and tasks that should not disappear.
Use dates and tasks when contracts, subscriptions or periodic services need future action.
Keep the business account separate from the people, locations and conversations connected to it.
Step 2
A useful record should answer who the customer is, what they need, what has happened and what happens next.
| Field / Record | Why It Matters | Keep It Clean By |
|---|---|---|
| Business / Account Name | Connects contacts and activity to the correct organization. | Use a consistent naming standard. |
| Contact Person | Identifies the individual responsible for the conversation. | Separate people from company/account records when the CRM supports it. |
| Phone & Email | Supports follow-up and helps detect duplicates. | Validate obvious errors and avoid creating a new record for every interaction. |
| Lead Source | Shows where the inquiry came from. | Use a controlled list instead of dozens of nearly identical source names. |
| Interest / Need | Explains what the customer wants. | Use structured choices plus notes when practical. |
| Owner | Shows who is responsible. | Reassign records when employees or territories change. |
| Next Action / Due Date | Turns history into follow-up. | Do not leave active records without a next step. |
Two records for the same business can split notes, calls, tasks and ownership. Decide how the CRM detects or merges duplicates and which fields—such as email, phone number or account name—staff should check before creating a new record.
Step 3
The pipeline should describe the business process, not every sentence that could describe a lead.
The inquiry exists but has not yet been meaningfully worked.
A first attempt or conversation has happened and follow-up may be required.
The need, fit, timing or other qualification criteria are sufficiently understood.
The opportunity is actively evaluating a quote, proposal or solution.
The relationship has moved into active customer/onboarding status.
The opportunity is not active; preserve the reason when useful.
The exact stages should match the business. Avoid creating so many stages that staff are unsure where a record belongs.
Step 4
Step 5
A useful CRM can reduce the “Who spoke to this customer?” problem by keeping authorized communication history close to the customer record.
Store call notes or call activity when the phone system and permissions support it.
Keep business messaging connected to the correct customer when the platform supports compliant messaging workflows.
Link relevant business correspondence when appropriate so follow-up does not depend on one person's inbox.
Use internal notes for context employees need, while avoiding unnecessary or inappropriate personal information.
Step 6
May need leads, tasks, notes, quotes and communication history without full system administration.
May need customer records, service history and communication tools without access to unrelated financial or administrative settings.
May need assignment, pipeline visibility, reporting and workflow controls.
Should be limited to trusted users who manage settings, integrations, permissions and data access.
Step 7
Integrations can save duplicate work, but every integration also creates another dependency to maintain.
Send new inquiries into the CRM with the customer's source, interests and contact information.
Connect calls, voicemail or messaging when the platform supports the workflow and permissions are appropriate.
Sync or log customer correspondence when the business wants shared visibility.
Integrate only when the shared data has a clear business purpose and the systems support it reliably.
Useful when the sales process needs to move from opportunity to quote, invoice or service without re-entering data.
Automate reminders or routing after the workflow is understood; do not automate a broken process.
Step 8
Before relying on a CRM, understand how the business can access and export its records if the software, vendor or plan changes.
Practical Setup Checklist
Commercial Next Step
RH Now can help businesses evaluate CRM and software needs alongside phone systems, websites, lead forms, POS/business technology and other customer-facing tools.
10D.6 Business Technology Series
Frequently Asked Questions
A CRM is a system for organizing customer and lead information, activity, tasks, follow-ups and related business workflows.
A lead is generally a potential customer or inquiry that has not yet become an active customer. The exact definition should match the business's own process.
Use enough stages to describe meaningful changes in the sales or service process, but not so many that staff are unsure where records belong.
Every active lead that requires future action should have a clear next step, owner and due date.
They can be useful when the platform supports it and the business has appropriate permissions, consent and retention practices for the communication type.
Use consistent data-entry rules, search before creating new records and use duplicate-detection or merge features when the CRM supports them.
Confirm data export, activity/history export, user access, integrations, field mapping, ownership, retention and the migration plan before ending the old service.
Related RH Now Resources
Reviewed by RH Now • Last reviewed: October 10, 2026
CRM features, integrations, privacy requirements, messaging capabilities and data-retention options vary by platform and business use case. Verify current requirements before deployment or migration.