STRAX Reach · Messaging apps
WhatsApp through a 360dialog number
Companies that onboarded WhatsApp through 360dialog keep that number and hub, and answer every chat from the Reach console.
- 360dialog channel key
- Template messages
- wa.me link codes
A partner-hosted number with the same client history
360dialog relays WhatsApp messages in the Cloud API shape, so Reach reads them the same way it reads Meta's own. The webhook address carries a callback token you choose, and Reach rejects any call without it.
Replies and templates go out through the 360dialog API with your channel key. Templates use the same name, language and parameters form as the Meta package, which makes switching providers later a settings change for your applications.
Choosing 360dialog usually comes down to onboarding speed and local support. Reach does not mind which partner holds the number: contacts, link codes and the console behave exactly as they do with the Meta package, and your applications call the same interface.
Where it helps
Fraud checks
Ask a client to confirm or reject a flagged transaction and let the fraud team see the reply beside the alert.
KYC document requests
Request an ID copy or proof of address and keep the request, reminders and reply together on the client record.
Merchant support
Merchants on your payment network write in on WhatsApp and reach the same support team as your consumer clients.
Settlement notices for merchants
Tell a merchant that the day's settlement has been paid, with the batch reference for their reconciliation.
What you need
-
A 360dialog channel
A number onboarded in the 360dialog Hub, or a sandbox key for testing.
-
The channel API key
Sent by Reach as the key header on every call and stored only in the STRAX credential vault.
-
A public HTTPS address
Needed for the inbound webhook, which Reach registers with 360dialog for you.
-
Reach Core
The contacts, conversations and console this channel files into.
Good to know
The 24-hour customer-service window applies here as well. Messages to clients who have been quiet longer must use an approved template.
Questions
Do we need a Meta app as well?
No. 360dialog holds the Meta relationship for the number; Reach only needs the channel key and your callback token.
Can we test with the sandbox?
Yes, register the sandbox key, run the webhook registration workflow and send a message from the sandbox test number.
What is still missing?
Documents, media and delivery statuses are not handled yet; text and templates are.
Can we move a number from 360dialog to the Meta Cloud API later?
Yes, install the other WhatsApp package, move the number, and disable this channel. Client identities stay on their records because both packages use the same WhatsApp id.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add WhatsApp via 360dialog to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Global variable | 1 |
| Workflow | 3 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the WhatsApp via 360dialog channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - WhatsApp 360dialog"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
WhatsApp and 360dialog are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.