A shared inbox, approved templates, broadcasts paced per number, journeys on a trigger, and checkout in the chat. On a number you own, as a Meta Tech Provider.
Written plainly so you can check it against your own account before you commit to anything.
Sample data throughout, from the same fictional shop that runs through this site.
Hi {{1}}, order {{2}} is on its way. Track it here.
Utility · EnglishNew in: the olive linen, cut and filmed in store. Reply STOP to opt out.
Marketing · Video headerReminder: {{1}} at {{2}}. Reply RESCHEDULE to move it.
Utility · EnglishYou asked about {{1}}. It is back in your size.
Marketing · Submitted 2d agoThe token bucket is per number, not per account, so adding a second number adds throughput instead of risking the first one.
Yes, we deliver to Pune. Standard is two to three working days, and it is free above ₹2,000.
The same olive linen jacket that runs through the rest of this site, followed through WhatsApp end to end.
The thread opens with the ad reference already attached, so the conversation knows where it came from.
message.receivedNumber, consent state and first-seen channel are written at once. No one retypes anything.
contact.createdGrounded in the catalog, not guessed. Staged in the inbox with the sources it used.
stagedOne tap. Her name goes on the message and into the audit chain with it.
approvedThe product card comes from your catalog, so price and stock are the live ones.
catalogThe order lands on her contact record and fires the event your systems listen for.
order.paidShipping template on dispatch, then a review request a week later, both consent-checked.
journeyWho approved what, when it sent, what it cost, all hash-chained so a gap is visible.
auditMessages, orders, consent, tags and owner sit on one card with the same person's Instagram and Google activity.
See the recordAny WhatsApp event can be a trigger: a keyword, an order, a form answer, an ad referral.
See Journey StudioSends, delivery, replies and orders are recorded per day by the same layer that records the other channels.
See the modelRoles decide who may send. The hash-chained log records what was sent and who said yes.
See governanceYes. uxjo replies from a shared inbox inside the customer service window, sends approved message templates outside it, runs broadcasts paced per number, and carries out journey steps. Every automated write is staged for a person to approve first.
Yes. uxjo connects to a number your business owns through the WhatsApp Business Platform, as a Meta Tech Provider. The number, its quality rating and its template approvals stay yours.
Broadcasts are paced per number by a token bucket rather than sent all at once, failed sends are retried, and a launch is blocked unless the template is approved, the audience is consent filtered and the number is inside its quality tier.
An opt-out reply is captured as consent state on the contact, not as a note someone has to read. Suppression is checked in the data layer, so it holds for a broadcast, a journey step and an API call alike, and it applies across every channel.
No. Meta bills conversations at their own rate and uxjo passes that through without a markup. Every message also carries its real cost in a ledger you can audit line by line.
Every business has a flow that is only theirs. Describe it in a message and we will map it with you, name the triggers, and tell you honestly what runs today and what does not. No form, no wait.
