Sending settings: email and WhatsApp, tested before you need them

1. Email. Settings › Sending › Email: from name, from address, SMTP host, port, username, password — from your email provider (Google Workspace, Microsoft 365, your host's mail). The platform sends as you, not as Premises, so replies come to you and your domain's reputation is yours.
2. DNS. The page checks your domain's SPF, DKIM and DMARC records and shows what is missing, with the exact record to add at your registrar. Inherited DMARC set to quarantine with no SPF is the common trap — your first invoice goes to spam. Fix the records, re-check, wait for green.
3. WhatsApp. Hand-off (default): the platform prepares the message and the link, your phone's WhatsApp opens with it, you press send. Works today, from your number, nothing to approve. Business API: messages go automatically from a verified business number; needs a Meta business account, a phone number not used on the app, and message templates approved by Meta — a week of admin, then hands-free sending.
4. Templates. Invoice, reminder 1–3, portal invite, receipt, proposal, notice — each with fields. The shipped ones are short and polite; put them in your voice, in the language your tenants use, and keep the fields.
5. Test. Send all tests to me: an email, a WhatsApp hand-off, a test invoice PDF, each template rendered. Open every one on your phone. Scan the QR codes. The nightly run's Send automatically option stays disabled until the tests have passed once.

Per place

A workspace with an association and a building can send from two addresses and two WhatsApp numbers: set the overrides on each place. The tests run per place.

When something fails later

Bounces and failed sends land in the Inbox with the reason; the tenant's row shows the last delivery status per channel. A provider password change is the usual cause; the Health card on Settings › Automation shows sending failures in the last 24 hours before tenants start asking.