A WhatsApp sales day is the path from a message that arrived after you closed to a named owner, a status, and a time on the calendar before anyone starts calling. The chat does the remembering. The morning is for the conversations that need a person.
This is the long version of that day. The short notes on qualifying a lead, the sheet, and follow-ups sit underneath it. Industry setups for property, showrooms, and studios are in the playbooks.
If the sheet is empty in the morning, the day did not happen. The messages may have been friendly. They were not a sales process.
What the day is for
A small team does not lose deals because nobody can talk. It loses them because the talking starts late, starts twice, or starts with no idea what the person already said. WhatsApp makes that worse and better at the same time. Customers write at 9pm. They expect an answer that still feels like the business, not a ticket number. They will not open a second app to book a visit.
The day exists to absorb that timing. Night is for capture. Morning is for judgment. The automation covers the first. The people cover the second. Mixing them up is how a team ends up with a full chat history and an empty calendar.
A full chat history is not a sales day. A status and a time are.
You do not need a large sales floor for this. One owner and one colleague can run it, if the chat always knows who owns the next step. A shared number with no owner is a different problem, and it has its own long read.
The message that arrives after you close
Most enquiries that matter do not arrive at 11am. They arrive when the person is done with work, sitting with a partner, or comparing two options on the sofa. The business is closed. The phone is not.
If the first reply waits until the next working morning, two things have usually happened. The person has written to a competitor who answered, or they have gone to sleep and will not reopen the thread with the same intent. Neither outcome is a mystery. Both are a timing problem.
The night reply does not have to close the sale. It has to do three small things. It confirms a person reached the right business. It asks the next useful question. It tells them a named human will pick the thread up, and roughly when. A reply that only says "Thanks, we will get back to you" wastes the moment they were willing to type.
Write that opening in the language your customers already use with you. If your desk speaks Hindi and English in the same thread, the first line can too. A stiff English paragraph at 9:40pm reads like a form, and people abandon forms.
The first reply has one job
The first reply is not a brochure. It is a turn in a conversation. One job: get the person to the first qualifying question without making them feel processed.
A usable opening has four parts, in this order.
- The business name, so they know the message is not a stranger.
- One sentence on what you can help with today. A visit, a call, a quote, a viewing. Not the whole catalogue.
- The first question, specific enough that the answer changes what you do next.
- A human's name and the hour they will join, if the chat will not finish the booking itself tonight.
That is enough. A PDF, a price list, and three follow-up questions in the same bubble teach the person to stop reading. Send the document after you know which document they need.
If you are on the official WhatsApp Business API, this reply can go out in seconds while the customer care window is open. The window, and the templates you need after it closes, are covered in message templates. For the sales day, the practical rule is simpler. Answer while they are still in the thread. The template is the backup for tomorrow, not the voice of tonight.
Three questions, then a status
A person should not spend a morning reconstructing a chat. Three answers are enough to decide whether this lead is worth a call today.
Ask what they want, in their words. A 3BHK in a named locality, a test drive of a model, a site visit for a kitchen, a batch that starts next month. The noun matters. "Interested" is not an answer you can route.
Ask the constraint that would make you say no, or say not yet. Budget, dates, locality, party size, whether there is a car to exchange. One constraint is enough. A second constraint is a conversation for the human, after the status is set.
Ask when they can talk or visit. Offer real options if you have them. "Whenever" is how meetings evaporate.
Then mark a status. Hot means they answered, the constraint fits what you sell, and there is a time. Warm means they started and stopped, or the constraint is close but not clear. Not now means the constraint is outside what you sell, or they said they are only looking next year. Not now is a real status. It is how the morning stays short.
The questions themselves, and how to keep them from sounding like an interrogation, are in the qualification guide. Use that script. Do not invent a fourth question because the CRM has an empty column.
Book the time in the thread
A lead with a status and no time is still homework. The sales day tries to leave a time on the calendar before the team arrives.
Offer two or three real openings. Not "when are you free," which pushes the work back onto the customer and produces a reply you cannot put on a calendar. If they pick one, confirm it in a single message: who they will meet, what the meeting is for, the time, and where it happens or which link to use. Ask them to reply if the time is wrong. That reply is also what keeps the conversation inside the window.
Write the same time to Google Calendar. If the sheet says Tuesday 6pm and the calendar does not, someone will double-book, and the customer will be the one who finds out. One write, from the chat to both places, is the point of connecting them.
If they will not pick a time tonight, do not invent one. Leave the status as warm and the next step as "offer times in the morning." A fake hold on the calendar is worse than an empty slot. It trains the team to ignore the calendar.
Appointment-heavy desks, where the product is the slot itself, should read how to book appointments on WhatsApp. The sales day uses the same confirmation habit, even when the meeting is a call rather than a chair.
Write the row before you forget
The row is not an export. It is the handoff. Six fields cover it: name, ask, constraint, status, next step, and meeting time. The sheet guide explains why each one earns its place. The sales-day rule is when the row is written. It is written when the person answers, not when someone remembers after chai.
A travel brief wants dates and headcount in the constraint. A showroom row wants budget and whether there is a car to exchange. A property row wants locality. The playbooks name the exact fields. The day does not care which noun you sell. It cares that the next person can act without rereading forty messages.
Add an owner column the moment two people sell. An unowned row is a lead nobody calls. If you are still the only person on the number, you are the owner, and the column can wait until the second person joins.
Do not paste the chat into the notes column. Notes become a second inbox, and second inboxes do not get read at 9am. If a fact does not change the next step, leave it in WhatsApp.
Tomorrow's message is a different kind
Inside the 24 hours after the customer last wrote, you can continue the conversation as a reply. After that, a business on the API sends a pre-approved template, and only if the person opted in to hear from you. The sales day has to respect that line, because the follow-up you meant as helpful becomes the message they report as spam.
So the night chat tries to finish the useful part while they are still with you: the three answers, or at least the first, and a time if they are hot. The morning follow-up is then either a normal reply, because they wrote late, or a short template that refers to the thing they already asked about. "Checking in" with no reference to their ask is how a list goes quiet.
One follow-up to a warm row. None to a not-now row. The follow-up guide is the rule for cadence. The sales day only adds this: decide the follow-up the night before, while the constraint is still fresh, and store it as the next step. Do not improvise a second nudge because the morning feels slow.
The morning standup is a sort, not a meeting
Ten minutes is enough if the sheet is true. Sort by status, then by meeting time.
Call the hot rows with a meeting today. Confirm they are still coming, or catch the cancellation early enough to offer the slot to someone on a waitlist. If the meeting is a phone call, place it at the time you promised, not "sometime this morning."
Send the one prepared follow-up to warm rows that stopped mid-question. Do not reopen the script from the top. Quote the question they did not answer.
Ignore not-now. Ignoring is an action. It keeps the afternoon from filling up with people who already told you the timing is wrong.
Then look for rows with no owner and no next step. Those are the failures of last night. Assign them before anyone new writes in. A standup that starts with fresh messages, and never looks at yesterday's unfinished rows, will repeat the same leak every day.
If you are a solo operator, the standup is still worth doing. Open the sheet before you open the chat. The chat is chronological. The sheet is priority. Chronology is how a polite time-waster outranks a buyer who wrote one line at midnight.
Where the automation stops
Automation should stop when the next message requires judgment, a number you will not put in a template, or a promise only a person can keep.
Stop when they ask for a discount, a custom quote, or an exception to a date. Stop when they are upset. Stop when the ask is outside the three questions and a human would want to hear the tone. Stop when two people in the same thread disagree about what they want. The chat can introduce the colleague by name and hand over the answers already collected. It should not negotiate.
For clinics and insurance desks, the stop is earlier and stricter. A clinic chat can book a listed visit. It cannot interpret symptoms or suggest a treatment. An insurance chat can arrange a time to speak about a product the person asked for. It cannot recommend a policy. Those limits are part of the day, not a footnote. The playbooks for clinics and insurance advisors state them in the setup itself.
The handoff sentence can be plain. "Priya will take this from here. She has the locality and the budget you sent, and she will call at 6." The person who joins should not ask those two things again. Asking again is how customers decide the business is not actually one business.
A worked example, labeled as an example
This record is an example, not a customer. It shows the shape of a finished night, not a result you should expect.
A message arrives at 8:50pm. "Hi, is the 2BHK on Lake Road still available?" The reply names the business, says viewings are booked on WhatsApp, and asks the budget range and whether Saturday or Sunday afternoon works. The person answers: under 80 lakh, Sunday after 4. The status becomes hot. The next step is the Sunday viewing. The meeting is written as Sunday 4:30pm, with the colleague who runs viewings. The sheet row exists before 9pm. The calendar matches.
On Sunday morning the reminder asks them to confirm or release the slot. They confirm. The viewing happens. Nothing in that chain required a night-shift salesperson. It required the questions, the status, and the write.
If they had said the budget was far below what that property can be shown at, the status would be not now, the next step would be stop, and Sunday would not have a ghost viewing on it. Both endings are a successful sales day. Only one of them is a meeting.
What to leave manual this month
Do not automate price negotiation, legal explanations, or a weekly broadcast to everyone who ever said hello. Do not add a seventh column to the sheet because a report might want it later. Do not split into three WhatsApp numbers until one number has an owner on every row.
The month-one version of this day is deliberately small. Night reply. Three questions. Status. Time when they are hot. Row written during the chat. Morning sort. One follow-up where the rules allow it. When that week repeats without heroics, add the pieces in what to automate, and what a person should still do.
What is a WhatsApp sales day?+
It is the path from a message that arrived after you closed to a named owner, a status, and a time on the calendar before the team starts calling the next morning.
What should happen before a person spends time on a WhatsApp lead?+
The chat should already know what the person wants, the constraint that decides fit, and whether they can take a call or a visit. Those three answers are enough to mark the lead hot, warm, or not now.
Why does the sheet row have to be written during the chat?+
A row written the next morning is a memory of the chat, and memories drop the constraint. The row should appear when the person answers, with a status and a next step.
What does the morning standup on WhatsApp actually decide?+
It sorts the sheet. Call the hot rows with a meeting today, send one follow-up to warm rows that stopped mid-question, and leave not-now rows alone.
Run tomorrow morning from a sheet that is already true
We will map the night reply and the three questions you already ask. The first 14 days are free.
Talk to us