Integration
Property buyers in the Gulf answer WhatsApp and ignore email. Treasury is built around that, from the first tier, without a middleman holding your thread.
The claim
Every WhatsApp goes out under the brand that owns the client, and every reply lands back on that client's record.
Today
What exists now
- Click to chat
- One tap from a client's record opens WhatsApp with the message already written. Nothing is copied and pasted, so nothing is sent to the wrong person.
- Personalised templates
- A template is written once for a brand and fills in the name, the property and the sign-off as it opens. Templates belong to one brand and are never shared into another by accident.
- The reference code
- A WhatsApp button on your website prints a short code into the message. When it arrives, the anonymous visit and the named person become one record, and the site is told which person the visit turned out to be.
- The inbound bridge
- Replies come back through a webhook and are logged as activities on the right client, in the right brand, matched on the number rather than guessed.
- STOP is an opt-out
- A reply of STOP suppresses that number immediately and everywhere in the brand, including any sequence it was in.
- Sequences
- Multi-step follow-ups that stop the moment somebody replies, so nobody is chased after they have answered.
- Metered per brand
- Every send is recorded against the brand that sent it, so one client's volume is never billed to another.
Plainly
What this is not, yet
This is not an official WhatsApp Business Platform inbox. Treasury is not a Meta business solution provider, so there is no approved template library, no broadcast campaign, and no shared team inbox inside the product.
An official Cloud API channel, with template submission and approval, sitting under the sequences and automations that already exist, is planned. There is no date and we will not invent one. If an official inbox is the thing you are buying, say so on the first call and we will tell you plainly where it is.
Why it matters
The thread belongs to the record
A WhatsApp conversation held in somebody's personal phone is a conversation the business loses when that person leaves. Bridged through a third-party tool, it is a conversation a third party keeps.
In Treasury the message and the reply sit on the client record, inside the brand that owns them, next to the stage, the deal, the viewing and the follow-up. When an agent leaves, the history stays.
Asked and answered
Questions
- Do I need a WhatsApp Business API account?
- No. Click to chat works from any WhatsApp number your team already uses, which is why it works on the first tier and on the first day.
- Are replies logged automatically?
- Yes, through the inbound bridge. A reply is matched to the client by number and written onto their timeline in the brand that owns them.
- Can I send the same message to 500 people?
- No, and you should not want to on an unofficial channel. Sequences send one person at a time, on a schedule, and stop when somebody answers.
- Is WhatsApp on the entry plan?
- Yes, from EUR 19 a month. HubSpot puts it on the third tier and Pipedrive on the second, both per seat.
Request access
Tell us how many brands you run and who needs to see them. We will walk you through the system with your names in it, not ours.
We reply within one working day. Already a customer? Sign in at app.treasurycrm.com.