Platform · Communications
Comms Plan
How PURE sends email and SMS: one home in Supabase Edge Functions, a provider behind each channel, and compliance built into the path — not bolted on.
The path a message takes
The app calls an RPC or drops a row; an Edge Function picks it up, applies consent + rate rules, calls the provider, and writes the result to audit_log. Inbound reverses it: provider webhook Edge Function pure_poppy_inbox.
Channels & providers
| Channel | Provider | Edge function | Status |
|---|---|---|---|
| Transactional email | Resend | resend-email | Active |
| Inbound email Poppy | Mail router webhook | pure-email-in | Ready · needs MX |
| Outbound SMS | Twilio · Messaging Service + A2P 10DLC | pure-comms | Assigned · Katy |
| Bulk email | Amazon SES / Postmark | — | Evaluating |
Composio can send outbound today; inbound always needs a webhook or MX serverless endpoint. Bulk SMS routes through a Twilio Messaging Service with A2P 10DLC registration; bulk email weighs SES (cost) against Postmark (deliverability).
Domains & sender authentication
in.acquisto.biz without touching the site.acquistorealestate.com. PURE’s automated mail is isolated on acquisto.biz and never changes the Zoho domain.Compliance, built into the send
pure_rate_limits (enforcement currently off by Mike’s call). Time-of-day guards keep automated SMS inside allowed windows.audit_log with principal, channel, and result — the same ledger the health-scan cron watches.Live edge functions confirmed active: resend-email, pure-mcp. The inbound endpoint pure-email-in is deployed and waits only on the MX/DNS human step. SMS work is scheduled with Katy.