Log WhatsApp opt-outs to Google Sheets with consent events

WavesFlo sends consent.withdrawn when someone asks to stop hearing from you, in any scope, and consent.granted when consent is recorded or restored. Each carries the subject, the scope (direct chat, group or channel), the action, the source and the evidence. Writing them to a sheet gives you a plain record that compliance, sales and support can all read. The sheet is a copy: the opt-out is respected when a message is sent whether or not you log it.

What is the log for?

• Answering a customer who says they asked to stop: you can show when, and in which scope.
• Cleaning other lists. Before a spreadsheet of contacts is imported anywhere, check it against the log.
• Seeing how often people leave after a campaign. Join the log to the Campaigns tab by date.

What should it never do?

• It should not be the only place an opt-out lives. Contacts imported from a CRM never gain consent by being imported, and an opt-out in a sheet does nothing unless something reads it.
• It should not be shared widely. A list of who asked not to be contacted is personal data.
• It should not be edited by hand. Add a Notes column for context and leave the event rows alone.

This guide describes logging, not legal advice. Rules on consent vary by country and by the kind of message; your own adviser should confirm what you must keep and for how long.

An opt-out recorded in WavesFlo is enforced at send time across every campaign, so the sheet is a record for people rather than the thing that stops a send. How campaigns handle consent and pacing is set out on the features page.