Templates
The messages you can send first
Outside the 24-hour window, only pre-approved templates reach a customer. MapleChat keeps yours in sync with Meta and tells you the moment one is at risk.
Meta stays the source of truth
Templates are mirrored from the Cloud API, never invented locally. Status, quality rating and category are whatever Meta says they are — so what you see in MapleChat is what will actually send.
Synced three ways
On read, on a scheduled sweep, and in near real time from Meta webhooks. A template that changes state overnight is already correct when you open the app, and one Meta has deleted is marked as such rather than failing at send time.
Told when something breaks
Owners and admins are notified when a template is rejected, paused or disabled, and when its quality drops to yellow or red. These are the moments where reacting quickly actually changes the outcome.
Rejections explain themselves
When Meta rejects a template, its stated reason is stored alongside it and cleared once the template recovers. You are not left guessing what to change.
Recategorisation is surfaced
Meta sometimes moves a template between marketing, utility and authentication — which changes what it costs you. When that happens, the previous category is recorded and flagged rather than silently applied.
Approved components, snapshotted at send
Sending a template freezes its name, language and component structure into the message. Editing the template later never rewrites what a customer already received.
See it with your own number
Thirty days, every feature, no card required.