STRAX Reach · Messaging apps
Facebook Messenger for your company page
Messages sent to your Facebook Page arrive in Reach, matched to the client when they have linked their profile and held for review when they have not.
- Page inbox in Reach
- Meta request signatures
- m.me link codes
Page messages with a client behind them
Meta sends each Page message to Reach with a signature made from your app secret. Reach verifies it, identifies the sender by their Page-scoped id and files the message in the right conversation.
Most Page messages come from people who are not yet known to you. With the link admission rule, Reach holds those messages and replies once with a request to connect their account, so strangers never reach client records.
Messenger identities are page-scoped, which means the same person has a different id for every Page. Reach stores the id for your Page only, so a client record never depends on ids issued to other companies.
Where it helps
Enquiries from the public
Prospects ask about your prepaid products on your Page and a sales agent answers from the same console as support.
Scam warnings
Point clients who report a fake page or phishing message to the right team and record the report.
Service updates
Answer questions during an outage from one place while the history stays with each client.
Branch and agent hours
Answer where and when clients can deposit cash, from the same console that handles account questions.
What you need
-
A Meta app and a Page
A Meta for Developers app with the Messenger product, connected to your company Page.
-
A Page access token
A System User token with the Page messaging permission, kept in the STRAX credential vault.
-
A public HTTPS address
Meta delivers Page messages to a verified webhook.
-
Reach Core
The records and console this channel uses.
Good to know
Messenger lets a Page reply freely within 24 hours of the person's last message. Later messages need Meta message tags, which this version does not send.
Questions
Who can message us?
Anyone who can see your Page. Choose whether Reach answers everyone, only known clients or only linked clients.
How does a client link their profile?
They open an m.me link with a code from your app or portal, and Reach connects that Page-scoped id to their record.
What is still missing?
Message tags for replies outside the window, and attachments or documents.
Can we move old Page conversations into Reach?
Reach starts recording from the moment the webhook is live. Earlier threads stay in Meta Business Suite for reference.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Messenger 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 Messenger 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 - Messenger"
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.
Messenger, Facebook and Meta 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.