Shared team inbox
Every thread in one place, open or closed, assigned to the person handling it or left to the bot, with the contact's history beside the conversation.
VISIONS Connect
Talk to every customer on WhatsApp.
A shared team inbox, bulk broadcasts, automated messages your own transactions set off, and a no-code chatbot builder, reading the same customers and invoices as the rest of your business. On the official WhatsApp Business Platform, with your own verified number.
Official Meta Cloud API, prepaid wallet in AED
Everything in the box
A WhatsApp suite, not a notification add-on.
One-to-one support, bulk campaigns and automated journeys, all tied to the customers and documents already in your ERP.
Message templates
Reusable templates with variables, submitted for WhatsApp approval and kept in step with their status on Meta's side.
Broadcasts
Send an approved template to a segment or the whole opted-in base, and watch the delivery funnel: sent, delivered, read, failed.
Contacts and segments
A saved audience is a reusable filter over the contact base by opt-in state, the module a contact came from, or a tag.
Triggers from your own data
The ERP sends the message itself. A job card marked ready messages the customer on the spot, and the overdue-invoice run chases every customer carrying a balance.
Chatbot flow builder
Draw the conversation: menus, replies and a hand-off to a person. Two starter flows ship ready to edit, a workshop booking assistant and an accounts assistant.
Prepaid wallet
Top up in AED and pay per conversation at Meta's category rates. Every debit and credit is a ledger line with a running balance, and a low-balance threshold warns you before a campaign stops.
Overview
Messages per day over the last fortnight, split inbound and outbound, and spend by Meta category over the last month.
Why it matters that it is the same system.
A standalone WhatsApp tool does not know when an invoice was raised or a job finished, so somebody has to tell it. Connect reads the same customers, invoices and job cards as the rest of VISIONS ERP, which means a message can be a consequence of work rather than another task on top of it.
It also means the awkward parts are handled where they belong. A contact carries an opt-in state, and a first inbound message is what opens the 24-hour window in which you can reply freely; outside that window a conversation has to start from an approved template. Connect tracks that window on the conversation, so your team is not guessing why a reply will not send.
What a conversation costs.
Meta prices WhatsApp per conversation, by category. Connect meters it through a prepaid wallet in AED: you top up, every message debits the balance with the category on the line, and the running balance sits on the same screen as the spend chart. There is no monthly surprise, and a low-balance threshold tells you before a broadcast runs out mid-send.
Being straight about it
Which messages send themselves today.
Automated triggers are the part buyers assume is endless, so here is the real list rather than the hopeful one.
Job card ready, live
Marking a job card completed fires the trigger and messages that customer's opted-in WhatsApp contact with the template you chose. No schedule, no scan, it happens as the status changes.
Overdue invoices, on a run
The overdue trigger is evaluated when the run happens: every customer with an overdue invoice gets your template, with their name, invoice number, balance and due date filled in.
The rest are configurable, not wired
Other events, rent due and payslip posted among them, can be set up and hold their template, but the module hook that fires them is not in yet. If one of those is why you are buying, ask us where it stands.
Start here
What it takes to go live.
Connect runs on the official WhatsApp Business Platform, so the setup is Meta's, not ours. It is a short list, but none of it is optional.
Your number
- A WhatsApp Business account
- A number that is not already on the WhatsApp app
- Verified in your own business name
Your templates
- Written with the variables you need
- Submitted for approval before you can start a conversation
- Approved templates are what broadcasts and triggers send
Your audience
- Contacts sync from the ERP
- Opt-in state per contact, and opting out is respected
- Segments by opt-in, source module or tag
Your wallet
- Prepaid balance in AED
- Charged per conversation at Meta category rates
- A low-balance threshold you set
FAQ
WhatsApp on VISIONS ERP, answered.
Does it use the official WhatsApp Business API?
Yes. Connect runs on the official WhatsApp Business Platform through the Meta Cloud API, with your own verified business number and templates approved by Meta. It is not a shared gateway or an unofficial bridge off a phone, which is the kind that gets numbers banned.
How is WhatsApp usage priced?
Meta charges per conversation, by category. Connect meters that through a prepaid wallet in AED: you top up, each message debits the balance, and every movement is a ledger line with a running balance and the category on it. You set a low-balance threshold so a campaign never stops halfway without warning.
Can the ERP send messages on its own?
Two of them today. Marking a job card ready messages that customer immediately, and the overdue-invoice trigger messages every customer carrying an overdue balance when the run happens, filling in their name, invoice number, balance and due date. Other events can be configured and hold their template, but their hooks are not live yet. Ask us where a specific one stands before you buy for it.
Can we send bulk broadcasts to our customers?
Yes. Contacts sync from the ERP, segments are saved filters over them by opt-in state, source module or tag, and a broadcast sends an approved template to a segment or to the whole opted-in base. The delivery funnel is tracked: sent, delivered, read and failed.
Can we build a chatbot without code?
Yes. The flow builder is visual: menus, automated replies and a hand-off to a person. Two starter flows come with every account, a workshop service-booking assistant and an accounts assistant, and both are switched off until you have read them, so nothing intercepts a real customer by accident.
What about the 24-hour window and opting out?
A customer messaging you opens a 24-hour window in which your team can reply freely, and Connect tracks that window on the conversation. Outside it, a conversation has to start from an approved template. Each contact carries an opt-in state and opting out is respected, which is also what the segments filter on.
Who can see and send messages?
Connect is scoped to your company like the rest of the ERP: conversations, contacts and campaigns stay inside your tenant, and role-based permissions decide who can reply and who can run a broadcast. A thread can be assigned to the person handling it so two people are not answering the same customer.
Put your customer conversation where your customers are.
Start free for 14 days, no card. Connect your number, send your first broadcast, and let a finished job tell the customer itself.