Managed WhatsApp automation
WhatsApp conversations that end in a completed request.
HumAI is a managed WhatsApp automation service. We design, build and run the workflow behind your WhatsApp number: answering routine questions from your approved information, collecting the details each request needs, routing it to the right person for approval and recording what happened next. It is not a do-it-yourself chatbot platform. We automate the agreed routine work and make the remaining human work easier to manage.
Meta Tech Provider · Official WhatsApp Business Platform
Meta Tech Provider · Official WhatsApp Business Platform
Your WhatsApp number stays in good standing.
HumAI is a Meta Tech Provider. We build on the official WhatsApp Business Platform, not unofficial apps or web automation, so your number isn’t exposed to the bans those tools cause. We set up opt-in, approved templates and human handover to keep your number in good standing.
What official access does and does not meanBeyond automated replies
What a managed workflow adds
Complete requests
The workflow asks only for the details that are missing, so your team receives requests it can act on without chasing.
Guided where it matters. Flexible where it helps.
Clear choices for structured steps such as a branch or a time, and natural language for everything else.
Handover with context
Exceptions, complaints and unknown questions go to the responsible person with the conversation and the details already collected.
Official platform, Meta Tech Provider
HumAI is a Meta Tech Provider. Messages run on the official WhatsApp Business Platform, not unofficial apps or web automation, so your number isn’t exposed to the bans those tools cause. Opt-in and template rules are built in.
Supported system actions
Where your system allows, requests can be checked against it or written to it. Each action is scoped and tested first.
Operated after launch
We monitor the workflow, keep approved information current and review it with you every month.
Who it’s for
Businesses that receive the same customer requests on WhatsApp every day and want them handled the same way every time, in any industry and any country. These are the industries we have written journeys for.
Service scope
What is included
Your proposal sets out the scope, term, included usage, support and exit arrangements before launch. This card shows what the solution typically includes; additional channels and operating modules are assessed around your needs.
Included journey
- Answers to routine questions from information you approve
- Collection of the details each request type needs
- A short summary the customer confirms before it is sent
- Routing to the right person, branch or queue for approval
- Status messages after the approved action succeeds
- Handover to a person on request, or whenever the workflow is unsure
Supported media
- Text messages and reply buttons
- Voice notes, tested in your languages
- Images and documents for agreed tasks
- Video and live calls need a separate scope
Languages
Arabic and English as standard. Other languages are tested and agreed before launch.
Your responsibilities
- Own the WhatsApp Business account and the phone number
- Provide and approve the information customers are given
- Name who approves requests and who takes handovers
- Tell us about changes to services, hours or prices
Not included
- Answers or advice your team has not approved
- Card payments taken inside the chat
- Messages to people who have not opted in
- Guaranteed sales, bookings or response figures
Walkthrough
One request, from first message to handover
Illustrative workflow; not a live customer record.
- 01 · Ask
A customer writes at 10pm asking whether a service is available on Saturday.
- 02 · Collect
The workflow answers from approved information and collects the name, branch and preferred time.
- 03 · Confirm
The customer checks a short summary and corrects the time before it is sent.
- 04 · Approve
Next morning a staff member sees one complete request in the queue and offers another slot.
- 05 · Exception
The customer then asks about a refund. That is outside the workflow, so it moves to a person with the full conversation.
How we work
Four stages, from real requests to monthly operation.
- 01
Map the requests
We review real WhatsApp conversations to find the requests that repeat and where they get stuck.
- 02
Agree scope and measurement
Together we decide what is automated, what is guided and what always goes to a person, and how success will be measured.
- 03
Build and test on real examples
We build the workflow and test it on your real request examples, including the awkward ones, before customers see it.
- 04
Launch, operate and review monthly
We launch, watch the queue, keep approved information current and review the results with you every month.
Honest limits
What this does not do
- It answers only from information you approve. It does not know your business on its own.
- A request collected in chat is not confirmed until your team, or a tested system action, confirms it.
- Meta’s policies, template rules and opt-in requirements apply. Official access is not immunity from account restrictions.
- Results also depend on your availability, staff response and customer choice. We commit to the agreed service and measurement, not to a number.
FAQ
Is this just another chatbot?
No. A chatbot platform gives you a tool to configure yourself. HumAI designs the whole workflow (collecting the right details, assigning responsibility, supporting approvals and recording progress) and runs it for you after launch.
Can we keep our existing WhatsApp number?
Usually, yes. The number needs to be connected to the official WhatsApp Business Platform. We check what that means for how your team uses the number today before anything changes.
Can customers type instead of tapping buttons?
Yes. The agreed workflow combines clear choices with natural requests. We test that details customers give are kept and that they can always reach a person.
What happens when it does not know the answer?
It does not guess. The conversation moves to the responsible person with the details collected so far, and the customer is told what happens next and when.
Is our WhatsApp number at risk?
Not from the tools we use. HumAI is a Meta Tech Provider and builds only on the official WhatsApp Business Platform, never on unofficial apps or web automation, which are the usual cause of banned numbers. We also set up opt-in, approved templates and human handover so your number stays in good standing.
Is this a done-for-you service?
Yes. We map your requests, build and test the workflow, launch it and keep running it, with a monthly review. Your team approves the scope, keeps business decisions and handles the requests that need a person. It is not a self-service tool you configure alone.
Does official WhatsApp access prevent restrictions?
No. Platform policies still apply. The workflow is built to respect messaging permissions, template rules and escalation, which lowers the risk but cannot remove it.
How much does it cost?
It depends on your workflow, volume, integrations and support scope. Proposals separate a one-time setup, a monthly service and usage-based WhatsApp charges set by Meta. See how pricing works for the full breakdown.
Related solutions
Customer service automation
WhatsApp plus website chat, Instagram, Messenger and Telegram, with case routing, handover and a view of the workload.
System integration
A connection assessment, agreed read and write levels, and a staff-approved process when there is no suitable API.
Operations analytics
A management view of unanswered topics, ageing approvals and branch workload, scoped to the data you have.
How pricing works
Setup, monthly operation, usage and third-party fees, explained without numbers.
Which WhatsApp request should we look at first?
Tell us what customers ask most and where requests get stuck. We will suggest one workflow worth automating first.
Talk to a person on our team about your workflow, without going through an assistant.