Setting Up WhatsApp for a Portuguese Cleaning Service: The Ten-Week Build Guide

Week 1-2: The foundation before automation

Before enabling any WhatsApp Business Platform setup, the underlying business infrastructure needs to be solid. Cleaning services attempting to build automation on top of unresolved legal or financial questions produce workflows that break the first time a client asks a specific question.

Week 1 items: Confirm the business's activity registration with the Autoridade Tributária under the appropriate CAE code (81210 for general cleaning of buildings, or specialised codes for other cleaning categories). Confirm IVA position — regime especial de isenção under Article 53 CIVA if annual gross revenue is below the threshold, or standard IVA registration if above.

Week 2 items: Set up the Portuguese IBAN for the business (either a personal-professional account under the FOP-equivalent Portuguese structure, or a business account for larger operations). Register the business's MB WAY-enabled phone number. Set up a Google Business Profile and (if serving international clients) a website in both Portuguese and English. Prepare the aydınlatma metni equivalent — the Portuguese GDPR privacy notice covering data collection purposes, retention, and client rights.

Week 3-4: Service definitions and pricing structure

Portuguese cleaning services span several distinct categories with different operational implications: residential regular (weekly or biweekly cleans for private homes), residential one-off (end-of-tenancy, deep clean, post-renovation), Airbnb turnover cleaning (a specific and growing category in Lisboa, Porto, Cascais, and Algarve), commercial regular (offices, retail spaces), and specialised (post-construction, hoarding cleanup, biohazard).

Each category has different pricing structures, different insurance requirements, and different WhatsApp workflow needs. A cleaning service should define which categories it serves and design template flows per category.

Week 3 items: Define service categories offered. Define pricing per square metre for residential, per turnover for Airbnb, per hour or per contract for commercial. Prepare typical service descriptions for the client-facing template library.

Week 4 items: Set up cancellation policy (particularly important for Airbnb turnover work, where late cancellation costs the cleaning team the day). Set up deposit policy for first-time clients. Prepare client onboarding questionnaire (square footage, access arrangements, pet presence, specific product preferences or allergies).

The Airbnb turnover segment deserves specific attention. Airbnb hosts need reliable turnover between guests, sometimes at short notice, sometimes at unusual hours (a same-day check-out to check-in requires the clean to happen in a narrow window). WhatsApp is the host's primary contact channel for coordinating access, verifying arrival time, and confirming the clean is complete. Cleaning services serving this segment should design templates specifically for it — a residential template designed for weekly clients does not fit Airbnb operations.

Week 5-6: Payment infrastructure setup

Once services and pricing are defined, payment infrastructure gets configured.

Week 5 items: Set up MB WAY as the default payment rail. Portuguese consumer payment behaviour has consolidated substantially around MB WAY, and 60-plus percent of adult banking-app users have it. For regular residential clients, a recurring MB WAY request pattern works (weekly service means weekly payment coordination). For one-off cleans, MB WAY per-service request works.

Week 6 items: Set up SEPA transfer as the alternative rail for commercial clients (offices tend to pay by invoice on 30-day terms, requiring SEPA). Prepare invoice templates through Portal das Finanças for recibo verde generation. Confirm the electronic ledger recording process for FOP tax obligations. For services above the IVA exemption threshold, set up the 23% IVA breakdown structure on all invoices.

For Airbnb turnover, set up short-cycle payment coordination — often the Airbnb host pays weekly or monthly across multiple turnovers rather than per-clean. Automation should track cumulative service delivery against the payment cycle.

Week 7-8: WhatsApp Business Platform enablement and template design

Now the automation setup begins. Missing any of the prior six weeks' work will surface during template approval when Meta rejects wording that references undefined services or promises capabilities the business hasn't set up.

Week 7 items: Register the Meta Business Manager and connect the business phone number. Set up the WhatsApp Business Platform account through Meta's Cloud API (either directly via Meta Business Solution Provider, or through an integrator like BossBot). Configure the aydınlatma metni link in the welcome template.

Week 7 template design: First-response template for new inquiries (short, warm, service categories offered, availability check invitation, aydınlatma metni link). Booking confirmation template (service, date, time window, address confirmation, price, cancellation policy note). Day-before reminder template. On-day arrival confirmation template. Completion notification template.

Week 8 items: Submit templates for Meta approval. Utility category applies to booking-related templates; marketing category applies to promotional broadcasts. Meta's approval timeline runs several business days per template. Expect rejections on first submission for wording that doesn't meet Meta's category rules; iterate.

While awaiting template approvals, build the integration between the CRM and MB WAY payment reconciliation. Test the flow with the owner's own phone as a mock client.

Week 9: Soft launch with a small client group

Week 9 is the soft launch. Enable automated flows for a small group of the cleaning service's existing regular clients (5-10 clients typically). Explain to them what's happening — 'we're upgrading our booking system; you'll notice automatic reminders and payment requests via WhatsApp; please tell us if anything doesn't feel right'.

This client group serves as the beta test. Their feedback catches issues before full rollout: templates that read as unfriendly, payment flows that confuse, edge cases the initial design didn't handle (a client wants to change their weekly service day; a client is going on holiday and wants to pause; a client wants to add an extra deep-clean around the holidays).

Adjust the automation based on the feedback. This week's investment saves weeks of remediation later.

Week 10: Full rollout and monitoring setup

Week 10 rolls the automation out to the full client base and establishes monitoring.

Monitoring items: Weekly review of automation logs for unclear responses. Weekly review of any manual overrides where the automation failed to serve a client's need. Weekly review of failed messages (delivery failures, opt-outs, complaints). Monthly review of the templates for wording that has aged poorly or no longer reflects the service.

Enabled properly, the automation should be handling routine coordination — booking confirmations, reminders, payment requests, arrival notifications — while the owner handles the substantive client relationship work: quality assurance, complaint resolution, service expansion conversations. The system should feel like it multiplies the owner's capacity rather than replacing it.