A customer messages your WhatsApp business number and your Aivell answers — hours, stock, prices from your knowledge base, order status from your database, in the customer's language, within a minute. Complaints and money questions go to a human. Reading and drafting happen on the box in your office.
starts when: A customer messages your business number on WhatsApp
Your customers are not composing emails. They are sending a WhatsApp message from the bus — “is the red one in stock?”, “where’s my order?” — and judging you by what happens in the next ten minutes. Answering within a minute lifts conversion by 45% or more; answering at closing time tomorrow mostly lifts your competitor’s.
For a small business the channel is a trap: the phone that owns the number goes home with someone, evenings and Saturdays pile up unanswered, and the same five questions arrive daily. The tools that promise to fix this route every customer conversation through a chatbot vendor’s cloud.
This channel is rolling out to early-access customers first — here is what it does when it reaches you:
The number stays yours, the answers come from your documents and your systems, and the thinking happens in your office — which is a strange thing to be able to say about a WhatsApp chatbot, and exactly the point.
No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:
greet within a minute, in the customer's language
answer hours, prices and stock from the knowledge base
order status? look it up in the database by the customer's number
complaints get an apology and Giulia — not an answer
never promise a discount or a refund; money is for humans
after 21:00, answer what you can and queue the rest for morning
still stuck after two tries? say so honestly and hand over
log every conversation and its outcome in the daily sheet
Connected with single-click passkeys — no copied tokens, no OAuth hell.
Every tool can be limited to exactly what this chore needs. For this one, you might set:
WhatsApp support is rolling out to early-access customers first. Tell us it matters to you and we'll put you on the list — everything else on this page is how it's built to work.
No. WhatsApp delivers the message as it always does; the reading, the database lookup and the drafted reply all happen on the box in your office. No conversation is sent to a cloud AI to be understood.
They shouldn't, and the chore makes sure of it — it answers plainly as the shop's assistant and hands over honestly when it's out of its depth. Fast and straight beats a fake first name.
The guardrails are blunt — it cannot message anyone who didn't write first, cannot change anything in your systems, and the chore forbids promising discounts or refunds. The worst case is an answer deferred to a human, not a commitment you didn't make.
Website support chat answering from your indexed manuals and policies, onboard your box — and handing off to email the moment it isn't sure.
Customers write in any language; your Aivell replies in theirs and briefs the team in yours. Translation runs onboard, so mail never leaves the office.
Evening and weekend inquiries answered on the spot by an on-premise AI colleague. Mornings start with qualified, pre-handled requests — not a backlog.
Order status, returns and price checks handled by a private AI colleague — onboard inference, so customer data never leaves your shop.
An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.
You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.
onboard inference · air-gapped · fixed monthly fee