Copartum
Messaging Overview
Optional template module. Messaging stays disabled until the matching environment is configured.
What the template supports
The repo includes optional inbound and outbound messaging paths for household updates, memory capture, reminders, and agent-assisted logging. None of these flows are required for the core web app.
Provider model
The current codebase is centered on WhatsApp/Kapso, with some legacy compatibility paths for SMS-shaped payloads. Replace this page if you change providers or remove messaging from your deployment.
How access works
Each linked sender is mapped to a household context before messages are accepted. Access is optional and independent from access to the core web app.
Access setup details: /messaging-access
Before enabling in production
- Replace this page with provider-accurate consent and opt-out language.
- Review outbound-template and webhook rules for the provider you choose.
- Keep messaging disabled until the required env vars are configured.