Routeless has implemented WhatsApp Business messaging through Twilio rather than a direct Meta Cloud API client. Verified workflows deliver lead alerts and booked-call summaries, receive inbound WhatsApp messages, and classify template or service-window failures. The provider distinction matters because credentials, sender onboarding, webhook verification, and error behavior belong to the Twilio transport used in production.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Real Estate Nemo, Routeless, Routeless Platform, and Routeless Core contain Twilio-backed WhatsApp senders, inbound handlers, template configuration, signature validation, and provider-error classification.
The evidence is intentionally limited to WhatsApp Business messaging through Twilio. It does not claim a direct Meta WhatsApp Cloud API client, Embedded Signup, or Meta partnership.
A Calendly booking or routed lead is converted into a concise operator brief and sent to the configured WhatsApp destination through Twilio.
Evidence: Verified in the Real Estate Nemo and Routeless Core booking-notification workflow.
The Twilio webhook verifies the request signature, normalizes the WhatsApp address and message, resolves the business context, and hands the event to the platform CRM.
Evidence: Verified in Routeless Platform channel and CRM inbound services.
Automation workers use an approved template when configured and classify Twilio's out-of-session error as a permanent workflow failure rather than repeatedly sending free-form text.
Evidence: Verified in Routeless Platform WhatsApp automation and notification-service code.
The verified transport uses Twilio account credentials and a WhatsApp-enabled sender. Inbound webhook requests are validated with Twilio's X-Twilio-Signature. No direct Meta Cloud API token or WhatsApp Business Account client is claimed on this page.
Twilio credentials and the WhatsApp sender stay in server-side configuration. Client and browser code do not receive the provider credential.
Invalid signatures are rejected. Missing sender configuration stops the attempt before delivery. Invalid destinations, opted-out recipients, and out-of-session free-form messages are treated as permanent failures.
A live workflow that carries audience, venture, form, and booking context into WhatsApp call summaries.
No. Routeless's verified implementation uses Twilio as the WhatsApp Business provider. A direct Meta Cloud API connection has a different token, phone-number, webhook, and business-onboarding model and is not claimed here.
Yes. Real Estate Nemo combines booking and lead context into an operator summary delivered through WhatsApp. The workflow can include deduplication, template selection, delivery status, and a fallback channel.
WhatsApp limits business-initiated free-form messaging outside the customer-service window. Approved templates let the business reopen contact for defined use cases. The application must choose the correct content path before sending.
No. Routeless can prepare the integration, submit compatible content, and handle rejection states, but template and sender approval are controlled by the provider and Meta.
WhatsApp Business official site. The WhatsApp Business name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.