A shared inbox
Your whole team answers one WhatsApp number, without passing a phone around. Conversations are claimed, so two agents never send one customer two different answers.
WhatsApp Cloud APIOfficial Meta platform
Consent-firstOpt-out enforced at send time
Google CalendarTwo-way sync
Gurugram, IndiaBuilt by Oriel Inc.
Four things, done properly.
Rather than twenty, done nearly.
Broadcasts that respect consent
Send an approved template to a segment of your customers. Anyone who opted out is excluded when the audience is built — and again at the moment of sending.
Booking inside the chat
Customers pick a slot on a form inside WhatsApp. It syncs with Google Calendar both ways, and the same slot cannot be sold twice.
Reminders
“Your appointment is tomorrow at 3.” Sent 24 hours and 1 hour before — and never to someone who opted out. A booking is not consent to be marketed to.
The shared inbox
Two agents, one customer, one answer.
A conversation is claimed before it is answered — atomically, in the database. Two agents clicking “assign to me” in the same second cannot both win, so a customer never gets two different answers to one question.
And the 24-hour window is enforced: outside it, WhatsApp accepts a free-form reply and then silently never delivers it. We refuse it instead, and tell the agent to use a template.
Oriel Inc., Gurugram.
Oriel Chat Engine is built and operated by Oriel Inc., registered in India at 599, 17B, Phase 1, Surat Nagar, Gurugram, Haryana, India. We are a WhatsApp Business Solution user building on Meta’s WhatsApp Cloud API.
We are a processor, not the owner of your customers’ data. When a business uses Oriel Chat Engine, that business is the custodian of its own contacts. We hold and process that data on their instructions.
Message history is kept for 90 days and then permanently deleted. Anyone can ask us to delete their data — here is exactly how — and we complete it within 30 days.