How to choose a CRM for a small business whose customers message you

Most CRM buying guides assume your customers fill out forms, take calls and answer emails. Many small businesses don’t work that way anymore. A dog groomer gets booking requests by text. A tutoring center hears from parents on WhatsApp. A remodeling company gets photos of water damage at 9 PM and a “can you come tomorrow?” before anyone has opened a CRM.

If that sounds like your business, the questions that matter when choosing a CRM are different. Whether it has forty dashboard widgets matters less than whether a text to your business number reaches the right person, and whether the history stays with the company when someone leaves.

This guide walks through how to choose a CRM when your customers message you: what to require, what to ask vendors and how to score the options side by side. It doesn’t name vendors. The goal is a method you can apply to any shortlist.

Start with how your customers actually reach you

Before you look at a single product page, spend a week writing down where conversations happen. A simple tally is enough:

• Which channels do new leads use? Text, WhatsApp, Instagram DMs, web forms, phone calls, email?
• Which numbers do they text? A business line, or individual employees’ personal phones?
• Who replies, and how quickly?
• Where does the history live once the job is booked?
• What happens to those conversations when an employee leaves?

This exercise often surfaces the real problem. Many small teams don’t lack a CRM; they lack a single place where customer conversations live. If most of your leads arrive by message, a contact database with messaging bolted on may still leave the actual work scattered. The glossary entry on messaging CRMs covers that difference in more detail.

Requirements checklist

Use this list to separate must-haves from nice-to-haves. Mark each line Must, Should or Not needed for your business before you talk to any vendor.

Conversations and channels

• Texts and WhatsApp messages arrive in one shared team inbox, not on personal phones.
• Each customer has one history across channels, not a separate thread per app.
• Supports a shared business number that stays with the company.
• Every conversation can be assigned to an owner.
• Team members can leave internal notes and mention each other without the customer seeing it.
• You can see which conversations are waiting for a reply and for how long.

Sales and follow-up

• Conversations connect to contacts and deals without copying and pasting.
• A simple pipeline with stages that match how you sell.
• Follow-up reminders when a customer hasn’t replied, or when you haven’t.
• Custom fields for the details your business tracks (service type, property size, preferred time).

Team and control

• Roles and permissions that match your team (owner, manager, rep).
• History stays with the business when an employee leaves.
• Basic reporting on response times and volume by channel.

Data and setup

• You can export your contacts, deals and conversation history in a usable format.
• You understand how you’ll move existing contacts in.
• Setup is realistic for your team’s time and skills.

Keep the list short. A CRM that does six things your team uses every day beats one that does sixty things nobody touches.

Questions to ask vendors

Product pages describe the ideal. These questions get at how things actually work. Ask for a live demonstration where you can.

Shared numbers

• “Can my whole team reply from one business number, by text and by WhatsApp?”
• “Can I bring my existing business number, or do I need a new one?”
• “If a customer texts the number, who sees it first, and how is it assigned?”

Getting client conversations off personal phones is often the biggest practical change. Our guide on moving client chats off personal phones covers the transition step by step.

Ownership

• “How do I see who owns each conversation right now?”
• “What happens to an assigned conversation when a rep is out sick or leaves?”
• “Can two people accidentally reply to the same customer at the same time?”

History

• “If a customer texts us and then messages on WhatsApp, do we see one history or two?”
• “How far back does the history go, and is anything deleted automatically?”
• “Can a new team member read the full context before replying?”

Provider and carrier fees

Business messaging usually involves costs beyond the software subscription. In the US, business texting goes through carriers and typically requires 10DLC registration, which comes with registration and per-message carrier fees. WhatsApp Business Platform messages are charged by Meta according to its own pricing model. Ask:

• “Which messaging fees are included in your price, and which are passed through?”
• “Who handles 10DLC registration, and are there fees for it?”
• “How are WhatsApp message charges billed to me?”
• “Are there extra charges for media messages, extra numbers or additional users?”

You don’t need to understand every fee structure in detail. You just need the vendor to tell you clearly which costs you’ll see and where.

Data export

• “Can I export everything, including conversation history, not just contacts?”
• “In what format? Can I open it in a spreadsheet?”
• “If we cancel, how long do we have to get our data out?”

A vendor who is vague about export is telling you something.

AI, if offered

• “Does anything get sent to customers or saved to records without a person approving it?”
• “Where does customer data go when the AI reads it?”

For a deeper list, see our article on what an AI CRM should actually do.

A scoring table template

Once you have two to four options, score them side by side. Weight each criterion by how much it matters to your business (1 = nice to have, 3 = critical), then score each vendor from 0 to 3 based on what you saw in the demo, not on what the website says.

To calculate the weighted total, multiply each score by its weight and add the results. Then look past the total: if an option scores 0 on something you marked critical, it’s probably out, no matter how good the rest looks.

Common mistakes

Buying for the team you might have in five years. Pick for the team you have. Most small businesses can switch later if they keep their data exportable.

Letting the demo set the agenda. Bring two or three real (anonymized) conversations and ask the vendor to show how each would be handled.

Ignoring the people who’ll use it. Have at least one rep who handles customer messages sit in on demos. If they won’t use it, the data will go stale.

Skipping the migration plan. Moving contacts and open deals takes longer than expected. A CRM migration checklist helps you clean up spreadsheets before you import anything.

Over-buying integrations. Start with the connections you’ll use in the first month. We cover that in which CRM integrations a small team needs first.

Where inChat fits

inChat is a conversation-first CRM built for small teams whose customers message them. It’s in development, with WhatsApp and US business texting as launch channels, and it’s designed around shared numbers, conversation ownership and one history per customer. It isn’t generally available yet, and pricing isn’t published. If your small business runs on customer messages, you can use the checklist above to evaluate it alongside anything else, and request early access when you’re ready.