WhatsApp Integration
The problem is that the answer sits in your ERP and the question sits on somebody's phone.
Why It Matters
There is a whole market of tools that automate WhatsApp by driving the consumer app. They work until the number is banned, usually at the worst moment.
A notification is only useful if it carries the right order number, the right amount and the right delivery date, and if the reply comes back attached to that same record.
We set up the Business API account, the sender profile and business verification.
We agree the triggers, the wording and what happens when someone replies.
Message templates are written and sent for approval, which can take a few days.
We connect to your ERP and test on real numbers before anything reaches customers.
Flows are switched on gradually, with delivery rates watched from day one.
Business API account, number registration, display name and verification handled with you.
Written to the category rules, submitted for approval and versioned when they change.
Flows fired by real document events, so nobody maintains a separate contact list.
Replies captured, matched to the record and routed to the right person or flow.
Sent, delivered, read and failed status per message, with a summary you can review.
Stop requests honoured and recorded against the contact, as the platform rules require.
The hard part is the trigger and the write-back, and that is our day job.
We will not automate a consumer number for you. The risk is not worth the saving.
We model provider and per-conversation charges against your volume before you commit.
We write to the category rules, which avoids the rejection loop most first attempts hit.
Flows go live in stages with delivery rates watched, not switched on all at once.
Yes, for anything automated. The consumer app and WhatsApp Business app cannot be integrated in a supported way, and tools that drive them risk the number being banned. We set you up on the official API through a business solution provider, which is the only route that is safe for a number you depend on.
There are three separate costs: our build, the provider platform fee, and the per-conversation charges WhatsApp itself bills. Those conversation rates vary by country and by category, and they change, so we model your expected volume against current rates during scoping rather than quoting a figure that will date.
Both. Replies are captured and written back against the right ERP record, so a customer answering a dispatch message is logged on that order rather than sitting in one person's phone. You can route inbound messages to a shared inbox, to an owner, or into an automated flow.
For any message you send outside an open conversation window, yes. WhatsApp requires those templates to be submitted and approved first. We write and submit them with you, and we design the flows so routine notifications fit the template rules rather than fighting them.
ERPNext, Odoo and most systems with a usable API. The integration reads the trigger from your ERP, such as an order confirmation or an overdue invoice, and writes the outcome back, so it works wherever those events and records can be reached.
A first set of notification flows is usually 3 to 5 weeks, including provider onboarding and template approval, which is often the slowest part and is outside our control. Two-way ordering flows take longer because they need more testing.
Related
The other services in this section, and related pages from TCB Infotech.
No commitment. A practical look at your messaging flows and running cost.
