WhatsApp, durable queue, multi-tenancy and Reserve with Google
WhatsApp notifications, a durable outbound queue with the outbox pattern, multi-tenant resolution, and the Reserve with Google feed.
What shipped
These releases expanded the SDK across several adapters at once:
- WhatsApp via Twilio, WhatsApp notifications and fan-out across multiple channels at the same time.
- Durable outbound queue, the outbox pattern, with at-least-once delivery and a dead-letter path for whatever couldn't get out.
- Multi-tenant resolution, identify the tenant by static config, path, host, header, or remote lookup.
- Reserve with Google, the availability feed and the SFTP publisher.
Why it matters
Reliable delivery of a notification looks simple until the network fails at the worst moment. The outbox pattern records the intent to send before attempting the send, so a failure becomes a retry, not a lost message. For a booking, the difference between "the customer was notified" and "we think they were" is the difference between an operation that trusts the system and one that double-checks everything by hand.
Multi-tenant resolution is the foundation that later made agency mode in the dashboard possible: a single SDK serving many locations, each with its own identity.