Key takeaways
- Google's Sheets API appends values to the next row of a table, which suits one row per WhatsApp request.
- Google Forms can store responses in a linked Google Sheet, a simple way to collect website leads and their opt-in together.
- Protecting a sheet stops accidental edits, but Google says it shouldn't be used as a security measure.
- A phone number in your sheet isn't opt-in: marketing messages need consent collected in a way Meta accepts.
What can WhatsApp do with Google Sheets?
Two things: write and read. WhatsApp requests can land in the sheet as rows, and the sheet can hold the information answers come from, such as products or schedules. Start with the first if your leads are scattered across several phones.
| Use | What goes in the sheet | Who uses it |
|---|---|---|
| New leads | Name, number, request, source and date | Sales follow-up |
| Orders taken on WhatsApp | Items, address, delivery day and status | Operations |
| Requests that need a person | The question, its owner and status | Team lead |
| Products or schedules | Items and times the answers come from | Whoever answers customers |
What are the ways to get WhatsApp requests into a sheet?
Two for WhatsApp itself, plus a form for your website. Someone copies each chat into the sheet, or a provider on the API adds each request as a row, while a Google Form on your website feeds the same sheet. Google's Sheets API appends values to the next row of a table, which is how one request becomes one row.
| Way | Effort | Watch for |
|---|---|---|
| Copy by hand from the WhatsApp Business app | Every chat, by hand | Typos and missed chats on busy days |
| Google Form on your website, linked to a sheet | Set up once | It only catches people who fill in the form |
| WhatsApp Business API with a provider | Set up and tested once | Agree the columns and who may edit them |
The Leak Audit is free, with no obligation. Within 72 hours of the discovery meeting and receipt of the agreed information, we map how customers reach you today, show the gaps the evidence supports, prioritise next steps and demonstrate one agreed workflow in a test environment. You keep the report, and if you don't need us, it says so.
How should the sheet be set up before you connect it?
Fix the columns first, then lock them. New rows go to the next row of the table, starting from its first column, so a renamed or moved column can send the next rows to the wrong place.
- One row per request, with fixed headers: date, name, number, request, source, owner and status.
- Protect the header row and any formulas. Google says protection isn't a security measure, so share the file only with people who need it.
- Give edit access to the few people who fix mistakes, because only editors can see the version history.
- Keep card numbers and national ID numbers out of the chat and out of the sheet.
Is a phone number in your sheet permission to message?
No. Meta requires opt-in before a business messages people on WhatsApp. A lead who asked about a price gets an answer in the same chat, but a campaign to the whole sheet needs consent first.
Collect opt-in in a way Meta accepts, such as a website form, SMS, a phone menu or in person, clearly stating your business name and that the person is opting in.
Add an opt-in column with the date and the source, so whoever sends a campaign can filter on it.
Where HumAI comes in, and when you don't need us
HumAI comes in when leads arrive faster than someone can copy them. After assessment and testing, we connect your sheet, so new WhatsApp requests become rows with the customer's details. Requests that need a person reach your team in the Inbox. We run it for you after assessment and testing, so every request lands in the sheet without anyone copying it by hand.
Picture a training centre in Cairo whose course enquiries reach three phones. Each evening someone copies the day's chats into a shared sheet, and the messages that arrive late at night wait until the next day.
We agree the columns and the scope with you, test what happens when the sheet is slow or unavailable, and keep the sheet as your record. When a sheet stops being enough, we connect CRMs such as HubSpot, Salesforce and Zoho CRM, after assessment and testing.
We work only on the official WhatsApp Business Platform, not unofficial apps or WhatsApp Web automation, so your number isn't exposed to the bans those tools cause. Meta's policies apply to every business number, and no provider can promise a number won't be banned.
You don't need us if a handful of chats a day reach one phone. Copy them into the sheet by hand, and add a Google Form to your website for the leads that come from there.
Related
Questions owners ask
Is Google Sheets enough, or do I need a CRM?
A sheet is enough while one team follows up leads and the columns stay simple. Move to a CRM when you need reminders per lead, several pipelines or a full history per customer. HumAI isn't a CRM vendor; we connect the one you choose, after assessment and testing.
What if someone deletes a row by mistake?
Anyone with edit access can open the version history and restore an earlier version. Google warns that restoring clears the cell-by-cell edit history for changes made before the restore, so look through the history before you restore. Protecting key columns cuts down on these mistakes.
Does a Google Form on my website count as opt-in?
Only if it says so. Meta's examples of accepted opt-in include a website, and the wording must clearly state your business name and that the person is opting in to receive messages. A contact form that only asks for a number collects a lead, not consent.
Can one sheet serve several branches?
Yes. Add a branch column, so each team filters its own rows, and keep one set of headers for every branch. In HumAI's Inbox, requests can also be routed by branch, so each team sees its own chats.