A new tool rarely fails on features. It fails on Tuesday of the second week, when a rep answers a customer from their phone because it was faster, and nobody notices. By week four, half the conversations are in the new system and half aren’t, and the team quietly goes back to what it did before.
This plan is built to prevent that. It’s for a team of 3–25 people that sells and serves customers over WhatsApp, text or other messaging, and is moving to a messaging CRM: one place where conversations, contacts and deals live together. The plan is tool-neutral, so adapt the specifics to the system you choose.
The plan at a glance
| Week | Focus | Done when |
|---|---|---|
| Week 0 (before day 1) | Decide, assign roles, prepare data | Roles named, data cleaned, numbers ready |
| Week 1 | Set up and pilot with a small group | Pilot group handles all their conversations in the CRM |
| Week 2 | Whole team goes live on the inbox | Every new conversation lands in the CRM with an owner |
| Week 3 | Pipeline, follow-ups and templates | Every active lead has a stage and a next step |
| Week 4 | Measure, adjust, lock in habits | Metrics reviewed, old channels retired |
Before day 1: prepare
Spend a few days on preparation before the 30 days start. It makes everything after easier.
Name the roles
Even on a five-person team, give each role to a named person:
| Role | Responsibilities | Typical person |
|---|---|---|
| Owner (sponsor) | Sets the expectation that the CRM is the way the team works; makes final calls | Business owner or GM |
| Rollout lead | Runs the plan, configures the system, answers questions | Ops lead, office manager or senior rep |
| Pilot users (2–3) | Use it first, find problems, help teach others | Reps who are open to change, plus one skeptic |
| Inbox coordinator | Watches unassigned conversations each shift | Office manager or a rotating rep |
| Everyone else | Uses the CRM for all customer conversations from their go-live date | The team |
Include one skeptic in the pilot. They’ll find the real problems, and their buy-in persuades others.
Prepare data and numbers
- Clean your contact data. Follow the CRM migration checklist: normalize phone numbers, dedupe and map pipeline stages.
- Decide which numbers connect. If conversations live on personal phones, plan the move to shared business numbers first. See moving client chats off personal phones.
- Start channel registration early. WhatsApp Business Platform setup and US texting registration (10DLC or toll-free verification) can take time. Begin before week 1. Our WhatsApp guide and texting compliance basics cover the steps.
Write a one-paragraph “why”
Share it with the team before day 1:
Starting November 3, all customer messages go through our shared inbox. Every conversation will have an owner, so nothing waits because someone’s out, and nobody needs to answer customers from their personal phone at night. We’ll start with a small group and the whole team will be on by November 10.
Week 1: set up and pilot
Tasks
- Connect channels. Connect your business WhatsApp and SMS numbers. Send test messages in both directions on each one.
- Create users and teams. Add the pilot users first. Group people into teams if you route by service line or location.
- Set up conversation statuses. Keep them few. A common set: Open, Waiting on customer, Closed.
- Set up pipeline stages. Use the stage map from your data preparation. Five to seven stages are usually enough for a service business.
- Add the custom fields you actually need. Lead source, service type, location and budget range are typical. Skip anything you won’t filter or report on.
- Import cleaned contacts if your system supports it, starting with active leads and customers.
- Run the pilot. The pilot group handles all their customer conversations in the CRM for the rest of the week.
Draft your inbox policy
Write it in week 1 and test it during the pilot. A one-page inbox policy for a small team might say:
- Every conversation has one owner. The owner replies or hands off with a note. Others don’t reply in someone else’s thread unless asked.
- New conversations are assigned within 15 minutes during business hours, by the inbox coordinator or an automatic rule.
- First response target: within 15 minutes during business hours for new leads; same day for existing customers. Choose numbers you can actually meet.
- Waiting on customer means the ball is in their court. Set a follow-up reminder.
- Closed means nothing more is needed. A new customer message reopens it.
- Internal discussion happens in internal notes, not in a separate group chat.
- No customer conversations on personal phones after your go-live date.
Pilot check-in (end of week 1)
Meet for 20 minutes. Ask:
- What did you do outside the CRM, and why?
- Which step felt slow?
- Did any message get missed or answered twice?
Fix the top two or three issues before week 2.
Week 2: the whole team goes live
Tasks
-
Add everyone. Create the remaining users.
-
Turn on assignment rules. Decide how new conversations get an owner:
Rule How it works Good when Manual by coordinator One person assigns each new conversation Low volume, varied requests Round-robin New conversations rotate across available reps Similar leads, similar reps By channel or number Each number or channel goes to a team Separate sales and support lines By territory or service Based on location or service type Specialized reps Sticky owner Returning customers go back to their existing owner Almost always, combined with one of the above Most small teams use “sticky owner” plus manual or round-robin for new leads.
-
Train in short sessions. Run two 30-minute sessions instead of one long one (see training below).
-
Set the go-live rule. From this day, every customer conversation happens in the CRM. Personal-phone conversations get moved over with a short note.
-
Hold a daily 10-minute standup for the week. Look at unassigned and overdue conversations together.
What to expect
The first few days are slower. People will look for buttons, forget to assign threads and occasionally reply from their phone. That’s normal. The rollout lead should be available to answer questions quickly, and the owner should visibly use the system too.
Week 3: pipeline, follow-ups and templates
With conversations flowing, connect them to the sales process.
Tasks
-
Link conversations to deals. Every lead conversation that’s more than a quick question should be linked to a contact and a deal at the right stage.
-
Add next steps. Each open deal gets a next step and a date. Use follow-up reminders for “no reply in X hours” situations.
-
Agree on qualification questions. Pick three to five questions every rep asks new leads. Our lead qualification questions template is a starting point.
-
Build a shared template library. Start with 8–12 templates the team actually uses:
- First reply to a new inquiry
- Asking for photos or details
- Quote sent
- Quote follow-up (two to three days later)
- Appointment confirmation and reminder
- After-hours reply
- Handoff to a colleague
- Closing the loop after a lost deal
For WhatsApp, remember that messages outside the 24-hour customer service window need approved templates. Our WhatsApp follow-up templates have wording you can adapt.
-
Agree on follow-up stop rules. Decide how many times you’ll follow up without a reply before closing a deal as lost. Three or four attempts over about two weeks is a reasonable starting point to test.
A sample first reply template:
Hi {first name}, thanks for reaching out to Brightline Remodeling. I’m Ana, and I’ll be helping you. To give you an accurate estimate, could you tell me which room you’re thinking about and roughly when you’d like to start?
Week 4: measure, adjust and lock in
Metrics to watch
Keep the list short. You’re checking whether the new habits are taking hold, not building a dashboard.
| Metric | What it tells you | How to read it |
|---|---|---|
| First response time for new leads | Whether new inquiries get answered quickly | Track the median and the slowest cases; look at after-hours separately |
| Unassigned conversations | Whether assignment is working | Should be close to zero at the end of each shift |
| Conversations with no reply in X hours | Whether anything is falling through | Review each one; find the pattern |
| Open deals with no next step | Whether the pipeline is being maintained | Should shrink each week |
| Conversations on personal phones | Whether the old habit is gone | Ask directly at the weekly check-in |
| Lead-to-won by channel | Whether each channel is working | Look at it monthly, not weekly; small numbers are noisy |
Don’t set targets based on someone else’s numbers. Measure your own baseline for a couple of weeks, then set goals relative to it.
Tasks
- Run a 30-minute retrospective. What’s working, what’s annoying, what should change?
- Adjust rules. Tighten or loosen response targets, change assignment rules, remove fields nobody uses.
- Retire old channels. Set auto-replies on old numbers and remove the old spreadsheet’s edit access.
- Make the weekly review routine. A 15-minute weekly look at the metrics above, led by the owner or team lead.
- Write down the final inbox policy and add it to onboarding for new hires.
Training plan
Keep training short and hands-on. People learn by handling real conversations, not by watching a long demo.
| Session | Length | Who | Content |
|---|---|---|---|
| 1. The inbox | 30 min | Everyone | Finding your conversations, replying, assigning, statuses, internal notes |
| 2. Contacts and deals | 30 min | Sales roles | Linking conversations to contacts and deals, stages, next steps |
| 3. Templates and follow-ups | 20 min | Everyone | Using templates, follow-up reminders, the 24-hour window on WhatsApp |
| 4. Office hours | 30 min, weekly | Anyone | Open questions with the rollout lead |
Training tips:
- Use real conversations (or realistic test ones) in every session.
- Give each person a one-page cheat sheet with the inbox policy and the five most-used actions.
- Pair new users with a pilot user for the first few days.
- Train new hires the same way after the rollout, from the written policy.
Common rollout problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Reps still reply from their phones | Habit; phone feels faster | Owner sets a clear go-live date; check in daily during week 2 |
| Conversations sit unassigned | No one is responsible for the queue | Name an inbox coordinator for each shift |
| Two people reply to the same customer | Ownership isn’t respected | Reinforce “one owner per thread”; use internal notes to ask |
| Pipeline is out of date | Stage updates feel like extra work | Make stage updates part of the weekly review; keep stages few |
| Too many fields and templates | Over-configuration in week 1 | Remove anything not used in the last two weeks |
| After-hours messages pile up | No after-hours plan | Set an auto-reply and a first-hour-of-the-day review |
Rollout checklist
- Roles named: owner, rollout lead, pilot users, inbox coordinator
- Contact data cleaned and stage map ready
- Business numbers ready and channel registration started
- Inbox policy written and shared
- Assignment rules set
- Pipeline stages and key custom fields configured
- Template library of 8–12 messages created
- Training sessions held and cheat sheet shared
- Baseline metrics recorded
- Old numbers and spreadsheets retired
- Weekly review scheduled
Where inChat fits
inChat is a conversation-first CRM in development for small teams. Its unified inbox, conversation assignment and follow-up reminders are designed around the kind of rollout described here. WhatsApp and SMS are planned launch channels. It isn’t available yet; if you’d like to follow along, you can join early access. For more on how small teams use a messaging CRM, see small business teams.