Many property, automotive and trade businesses start managing WhatsApp enquiries the same way: someone builds a spreadsheet, pastes in numbers from the group chat or the personal mobile, and hopes everyone remembers to update it. It works for a week. Then a lead sits untouched over a weekend, two team members reply to the same customer with different answers, and nobody can say for certain what was promised to whom. This guide sets out the practical steps for moving WhatsApp orders and enquiries off that spreadsheet and onto a system built for the job.
A spreadsheet cannot capture a live conversation. It can only record what someone typed into it after the fact, which means every message sent from a personal phone becomes a message the business itself doesn't own. Messages sent from personal WhatsApp accounts risk being stranded outside any central record, which creates both legal and operational exposure, and removes the defensible record of what was said, agreed or committed to a customer. That gap is precisely what a business messaging platform is designed to close.
Before you start moving off the spreadsheet, have the following ready:
Start by identifying every route a customer currently uses to reach the business on WhatsApp. This typically includes personal staff mobiles, a shared office number used ad hoc, and messages triggered informally from portal leads. For lettings and estate agency operations specifically, this often includes handling high-volume enquiries through what has effectively become a "no reply" WhatsApp account, plus manually forwarding portal leads from sites like Rightmove. For automotive operations, the equivalent leads typically arrive from Auto Trader, Motors, or web-form enquiries. Write down every source before you touch the system — you cannot migrate what you haven't mapped.
The single most important structural change is separating the business from any individual's personal phone. Stitch, the WhatsApp business communication platform, is built on the official WhatsApp Cloud API, which is what allows more than one person to access a single WhatsApp number without the QR-code and mobile-device restrictions of the free app. The right mental model here is a phone system rather than a group chat: a business publishes one number, and messages route to the right person or team, exactly as calls do on a phone system, except the customer makes first contact and the whole conversation is captured centrally. This is the step that turns "several people checking a phone" into a managed inbox.
Once the account is on a proper business platform, structure access before you migrate any conversations. Set up hierarchical user roles — admin, team leader and user — so that permissions match how your team actually works. Alongside roles, use inbox filtering by tags or teams, for example separating a sales progression team from a lettings applicants team, so nobody has to scroll through an undifferentiated feed to find their conversations. This structure is what replaces the manual sorting a spreadsheet forced someone to do by hand.
Before go-live, decide exactly how many users need day-one access and what your standard message templates should say. In one implementation, an agency confirmed five initial users and requested minimal, warm templates for both the portal responder and the out-of-hours auto-reply. Template messages need to be submitted to Meta for approval before they can be used, so this decision has to happen early rather than being left until launch week. Getting this agreed up front avoids a stalled go-live while templates sit in review.
A spreadsheet fails partly because it sits disconnected from the systems that actually run the business — the CRM, the DMS, the portal feed. The fix is integration, not a better spreadsheet. Integration with a CRM such as Street enables automatic message logging, so conversations are recorded against the right property or applicant without anyone re-typing them. Similarly, enabling an Alto integration preserves the conversation record directly inside the CRM, which eliminates messages being stranded on personal accounts and provides a defensible record — for example of property inclusions or commitments made to a customer — reducing dispute and liability exposure. This is the step that finally retires the manual copy-paste workflow.
With the inbox and CRM connection in place, automate the leads that generate the most manual admin. Portal and form leads from sources like Rightmove, Zoopla and web forms can trigger an instant WhatsApp message the moment they arrive, so the enquiry is engaged with while it is still warm, rather than the business racing three other agents the next morning. The same principle applies in automotive: Auto Trader, Motors and web-form enquiries can be set to trigger an instant WhatsApp reply automatically. This step alone removes the single biggest reason spreadsheets fall behind — leads arriving faster than a human can log them.
A spreadsheet has no answer for what happens to a message that arrives at 9pm on a Saturday. On the official platform, this is solved by having a bot or AI assistant greet the customer around the clock, ask qualifying questions, capture the detail, and assign the conversation to the right team so a human can pick it up with full context on the next working day. The goal is not to give an instant final answer out of hours — it is to give instant engagement, the same principle as a taxi app telling you your car is twelve minutes away rather than leaving you standing on the kerb with no information. Decide now which templates and qualifying questions your out-of-hours flow should use, since this is configured at setup rather than bolted on later.
Migrating off the spreadsheet only pays off if customers actually use the new channel, and customers will not message a business on WhatsApp unless they know the business is there. Open the channel in four places: a "Chat on WhatsApp" button on the website so a browsing customer can start a conversation instantly rather than filling in a form; QR codes in the physical world, such as in a branch window, on a For Sale board, or on a brochure; a link from the phone system so a caller sitting in a queue can press a key to switch to WhatsApp instead of hanging up; and automated triggers from portal and form leads so the business engages while interest is still warm. Each of these is a small setup task, but skipping any one of them leaves a gap the spreadsheet used to paper over manually.
With the workflow designed, the final step is formalising the commercial relationship. This typically involves a Customer Order Form and draft contract, followed by setting up or recovering Meta Business Suite access, providing an office number, and scheduling a one-time OTP phone verification call. Once the order form is returned, the provider creates the WhatsApp Business Profile, submits templates for Meta approval, enables the CRM integration, configures portal responders and website widgets, and delivers a training and onboarding session with an admin guide. On billing, a typical structure includes a one-off onboarding fee, a monthly subscription covering a set number of users, and Meta's own WhatsApp usage charges invoiced monthly in arrears as a pass-through cost with no markup.
Messages are still landing on personal phones after go-live. Check that the "Chat on WhatsApp" button, QR codes and portal automations are all live and pointing to the new business number, not an old personal one, since customers will default to whatever channel they last used.
Templates are stuck and can't be sent. Template messages need Meta approval before use, so if messages aren't sending, confirm the templates were submitted and approved as part of onboarding rather than assuming they went live automatically.
Access issues with Meta Business Suite. If Facebook or Meta access has been lost or was never properly set up, this needs to be resolved before the WhatsApp Business Profile can be created, so treat it as a blocking task early in onboarding.
Team members can't find the right conversations. If the inbox feels as unmanageable as the old spreadsheet, revisit the tagging and team-based filtering setup — conversations should be filterable by group, such as a sales progression team versus a lettings applicants team.
Moving WhatsApp orders and enquiries off a manual spreadsheet is a matter of sequencing: map every current entry point, move onto the official WhatsApp Business Platform, structure user roles and inbox filtering, connect the CRM so conversations log automatically, automate your highest-volume lead sources, decide how out-of-hours enquiries are handled, and open the channel everywhere customers already look for you. Each step replaces a piece of manual admin the spreadsheet was papering over, and together they turn scattered messages into one managed, defensible, team-accessible record.
