iWac.ai / WhatsApp Commerce & Engagement
Turn WhatsApp Conversations Into Orders, Bookings and Repeat Business.
iWac connects marketing, commerce and service in one governed WhatsApp journey, with approved content, system integration, secure payment handoff and contextual human support.
Commerce Journey Console ILLUSTRATIVE
01 Discover ENTRY Customer opens WhatsApp from a QR code, ad or invoice link.
02 Ask GROUNDED Questions answered from approved catalogue and policy content.
03 Choose SYSTEM Options presented with availability from your system of record.
04 Book or order ACTION Selection written back to the booking or order workflow.
05 Secure payment handoff SEPARATED Payment completed in your provider, never inside the chat thread.
06 Support HUMAN Follow-up, status and exceptions routed to a person with context.
Representative journey shown for review. Scenarios stay labelled as illustrative until a configured demonstration and approved customer proof are available.
Customer ownership
The customer relationship and data remain yours throughout the journey.
Consent respected
Opt-in, template and messaging rules are enforced, not worked around.
Payment separation
Money moves in your payment provider, with the chat carrying only the handoff.
Three jobs
Start with the business movement, not the bot.
01
Sell + book Move an enquiry to a confirmed order or booking inside the conversation the customer already started. 02
Support + resolve Answer status, delivery and account questions from approved sources, then escalate with context. 03
Retain + re-engage Bring customers back with permitted, relevant follow-ups tied to the last completed action. One deployment path
Design it. Connect it. Prove the customer action.
01
Design the journey
Pick one movement and write the steps, decisions and exceptions end to end.
02
Connect the systems
Catalogue, availability, order and payment boundaries are agreed before build.
03
Set the controls
Consent, templates, escalation and human authority are configured together.
04
Prove the action
Run the journey on real demand and measure the completed customer action.
Control loop
One WhatsApp journey. Your systems stay in control.
Your system of record decides
Availability, pricing and order state come from your systems — the journey never invents them.
Consent and templates enforced
Messaging follows platform policy and your own opt-in rules, with an auditable trail.
Human authority preserved
Exceptions, disputes and sensitive requests move to a named person with the full thread.
Where it stops
iWac is deliberately bounded. These stay with people and your existing systems:
Taking payment inside the chat thread
Overriding pricing, stock or policy rules
Messaging contacts without a valid opt-in
Deciding disputes, refunds or exceptions alone
Where it fits first
Where an iWac journey usually starts.
Bring one customer journey. See iWac carry it to the next action.
The demonstration is configured on your movement — catalogue, calendar or support queue — not a generic script.