The one-chat problem
A small sales team usually starts with one group chat. It's fast and everyone reads it. For a while, it works.
Then it fills up. A client's budget gets mentioned between a meme and a question about the printer. Someone asks "who's handling the Lim account?" three times in a month. A rep posts a win, and a question about a price change from an hour earlier disappears under the congratulations.
The problem isn't the chat. It's using one channel for five different jobs. Good sales team communication mostly means deciding what goes where, and then sticking to it.
What goes in which channel
Here's a simple map for a team of 3 to 20. Swap in whatever tools you use.
| What | Where it goes | Why |
|---|---|---|
| Wins, shout-outs, quick questions | The team group chat | Fast, social, fine to scroll past |
| Anything about a specific client | The client's record in your CRM or shared file | You'll need it in three months, and so will whoever covers for you |
| Your numbers for the week | Logged where the manager can see them | So nobody has to ask "how's your week?" |
| Decisions that change how the team sells | The weekly meeting, then written up in one place | So everyone hears it once, the same way |
| Personal performance, problems, coaching | The 1:1 | Never in the group |
| Urgent: a client waiting, a deal at risk today | A direct call or message to the person | Not a group post that might be missed |
The most important row is the second one. Client details posted in a chat are lost within a week. Written on the client's record, they're there when anyone picks the client up.
The chat is for talk. Keep the record somewhere else. If your team uses a WhatsApp group, ActivityTracker vs the WhatsApp group sets out what to keep in the group and what to count elsewhere.
A weekly rhythm
Most communication problems on a sales team come from missing rhythm, not missing tools. When everyone knows when things will be discussed, they stop posting everything the moment it occurs to them.
| When | What | How long |
|---|---|---|
| Monday morning | Team meeting: last week's numbers, this week's focus, one thing to practise | 30 minutes |
| Monday to Friday | Reps log activity as they go; the chat carries wins and quick questions | A few seconds each |
| Wednesday | Manager checks who's behind on the week and messages them directly | 15 minutes |
| Every week or two | 1:1 with each rep: numbers, one stuck deal, one skill | 20 to 30 minutes each |
| Friday | Each rep sends a short check-in: the week's numbers, what worked, what got in the way | 5 minutes each |
The weekly sales meeting agenda has a 30-minute agenda to copy, and the 1 on 1 meeting template keeps each 1:1 on one skill and one promise.
A Friday check-in is the most useful habit on the list. Four lines from each rep, sent to the manager, replaces most of the "how's it going?" messages during the week.
This week: [calls] calls, [meetings] meetings, [proposals] proposals, [won] won.
What worked: [one thing]
What got in the way: [one thing]
Next week I need: [help, a decision, nothing]
Less chasing starts with seeing the week without asking. With ActivityTracker your reps log calls in one tap, and you see who's gone quiet, read their Friday check-ins and prep each 1:1, for a team of 5 or 30.
Handovers that don't drop clients
Clients get dropped at the handover: a rep goes on leave, moves territory, leaves the business, or hands a signed client to whoever looks after them next.
A handover works when the next person can run the next conversation without calling the last one. Write it down, on the client's record, before the handover happens:
Client: [name, company, role]
Where things stand: [stage, in two lines]
What they care about: [in their words]
What we've promised, and by when: [each item]
Next step: [what, when]
People involved: [who decides, who signs, who to avoid]
Anything sensitive: [a complaint, a price exception, a personal matter]
Then introduce the new person to the client yourself, by call or message, and say why they're a good fit. A client who hears about the change from you stays. One who finds out when a stranger calls often doesn't.
If your team shares one WhatsApp number, decide who owns each chat before anyone goes on leave. WhatsApp Business multiple users covers how to set that up.
Sharing what works
Most of what a team learns stays in one rep's head. The rep who found a better way to handle a price objection uses it for a year, and nobody else hears about it.
Three habits spread it:
- A "what worked" slot in the weekly meeting. Five minutes, one rep, one thing: a line, an email, a question that opened a deal.
- A shared page of lines that work. When someone's answer to an objection gets a yes, it goes on the page, in their words.
- Wins posted with the how. "Signed Harbour Dental" is nice. "Signed Harbour Dental: asked who else decides on the first call, and got the owner on the second" is useful.
Sales and delivery talking
On many small teams, the biggest communication gap isn't inside sales. It's between the people who sell and the people who deliver what was sold.
What goes wrong: sales promises a start date that delivery can't meet, or a feature that doesn't exist, or a price that doesn't cover the work. Delivery finds out when the client arrives. The client hears two different stories.
What helps:
- A short handover note from sales to delivery for every new client. The template above works.
- A 15-minute check between the sales manager and the delivery lead once a week: what's coming, what's promised, what's stuck.
- A rule that anything unusual, like a custom deadline or a special price, is agreed with delivery before it's promised.
- Delivery tells sales when a client is ready for more, or unhappy, so a rep can call them that week.
Made-up example: a five-person team sells and installs security systems for small shops. Four reps, one install lead, one group chat.
Monday: the manager, Faiz, sets up the map. Wins and quick questions stay in the group. Client details go on the client's record. Reps log calls as they go. He moves the Monday meeting to 9:00 for 30 minutes.
Tuesday: a rep posts "Mr Tan wants the install before the 15th" in the group. Faiz asks her to put it on Mr Tan's record and message the install lead directly. The install lead replies that the 15th is full and offers the 17th, and the rep tells the client the same day.
Wednesday: Faiz checks the week. One rep has 9 calls logged against a target of 40. He messages her directly. She's been doing site surveys that another rep booked. They agree who does surveys from now on.
Thursday: a rep shares in the group how she got a hesitant shop owner to agree: she offered a trial camera at the till for a week. Two other reps try it on Friday.
Friday: four check-ins arrive by 5pm. The chat has half the messages of last week, and nobody asked "who's handling this?"
What to do first
- Write your channel map on one page and share it with the team.
- Move any client details from the group chat onto the client's record this week.
- Start the Friday check-in: four lines from each rep.
- Put the weekly meeting and every 1:1 in the calendar for the next month.
- Book a 15-minute weekly check with whoever delivers what you sell.
For a written version of the week, the weekly sales report template covers activity against target, deals, pipeline changes and what each rep needs.