WhatsApp AI customer service that takes action inside the chat. Hay reads the message, pulls what it needs from your stack, and gets the job done. Often before the customer types again.
When a customer messages you on WhatsApp, they expect the same experience they get messaging anyone else. Fast, conversational, done. Most AI tools don't deliver that. They answer a question, push a knowledge base article, or collect details and promise a follow-up.
Underneath, it's still just a form with a chat bubble on top.
2B+
WhatsApp users worldwide
177
Actions Hay can take across your stack
9
Deep integrations powering them
Hay treats WhatsApp as a place where things get done. Orders get tracked. Refunds happen inside the chat. The customer never has to leave WhatsApp to get a result.
AI that executes actions, not just answers questions
Hay walks into every chat already knowing who's on the other end. Their order history, their previous tickets, the email they used at checkout. The first reply gets to the actual question.
Most WhatsApp conversations don't wrap up in a single message. Hay holds the context across replies and finishes what it started. The customer never has to repeat anything they've already said.
Tappable options for the common requests. Faster on a phone keyboard, and you don't get 'yse' instead of 'yes'. When Hay needs to confirm a refund or offer a choice, buttons keep things feeling native.
Short messages that fit a phone screen. Configure response style per channel, so WhatsApp stays casual and concise while email gets the longer version.
Assign different playbooks to WhatsApp than to web chat or email. Different tone, different return policy, even different escalation rules if you want them. The logic stays the same. The delivery adapts.
Assign a specific agent to WhatsApp, or use the same one across every channel. If your LATAM customers live in WhatsApp and your UK customers prefer email, route by channel.
Customer:
"Hey, where's my order?"
Hay:
Happy to check. What's the email you used to order?
→ Customer replies → Hay queries Shopify → Returns tracking link and ETA
Result: Resolved in under a minute, without a ticket or an agent touch.
Customer:
"The jacket I ordered doesn't fit, can I return it?"
Hay:
Sorry about that. Let me check your order... It's eligible for a full refund. Want me to process it now?
→ Checks WooCommerce → Verifies policy → Refunds via Stripe → Confirms
Result: Refund issued inside the chat. The customer never opens an email or a portal.
Customer:
"I just realised I gave the wrong shipping address, can I change it?"
Hay:
Let me check if it's still in the warehouse... it hasn't shipped yet. What's the correct address?
→ Checks Shopify fulfilment status → Updates the order → Confirms
Result: Address fixed before the parcel left the warehouse. Saved a return shipment and a redelivery fee.
Customer:
"My payment didn't go through, what happened?"
Hay:
Your card ending in 4242 was declined yesterday. Want me to send a secure link to try a different method?
→ Checks Stripe → Identifies decline reason → Sends payment link
Result: Customer retries on their own time. Revenue recovered.
AI handles a lot of WhatsApp support. It doesn't have to handle all of it. Hay routes the conversations that need a human to a human, with the full chat and customer context already loaded. You decide where the line sits.
The aim is to clear the repetitive tickets off your team's plate. Honestly, that's the whole point. They get more time for the conversations that need a person.
Two billion people use WhatsApp. A meaningful chunk of them are your customers.
Messaging means people expect a reply in minutes. Hay answers in seconds, any hour, in whichever languages you've configured.
Most WhatsApp tools create a ticket. Hay closes the loop in the chat.
Data stays in the EU. GDPR-aligned by default, the same on Solo as it is on Enterprise.
Hay doesn't charge extra for WhatsApp. It's on every plan, from Solo at €50/month up to Enterprise. You'll need a Twilio account because Twilio is Meta's BSP for the WhatsApp Business API. Twilio's roughly $0.005 per message on top of Meta's rates, billed by Twilio direct.
You'll need a WhatsApp Business account, access to Meta Business Manager, and a Twilio account (Twilio is Meta's BSP for the WhatsApp Business API). Connect the credentials in Hay's dashboard, register your sender, and switch the channel on. The Hay side is a few minutes. Twilio number provisioning and Meta Business verification can take a day or a week, depending on how clean your paperwork is. We'll walk you through it if anything's missing.
No. Hay uses playbooks written in plain language that the AI follows in context. If you want WhatsApp to sound different from your web chat or email, give it a different playbook. You won't be building if-then trees.
Most of the time, customers message you first. That opens a 24-hour window where free-form replies are allowed, and that's where Hay does its work. Inside the window, the AI handles the conversation directly. If you want to send proactive notifications outside the window, Meta requires approved templates, and that setup lives in your Meta Business Manager and Twilio account.
Not currently. On WhatsApp, Hay handles text. If a customer sends a photo or PDF, Hay will ask them to type the question or details so it can help. Media support is on our roadmap for the WhatsApp channel. If it matters to your use case, tell us and we'll factor it in.
The same actions Hay takes on any channel, just over WhatsApp instead of web chat. If Hay can refund, look up an order, or retry a failed payment from your web chat widget, it can do it from a WhatsApp message too. The integrations you've connected don't care which channel the question came from.
Only if it isn't tied to a personal WhatsApp account. If it is, you'll need to deregister it (which deletes the personal account from that number), or use a different clean number for the business. Worth checking before you start the registration. We can help you confirm which side your number's on.
Not yet. Voice notes are part of the broader WhatsApp media support we're building. Today, if a customer sends a voice message, Hay replies and asks them to type the question. We get this asked about a lot. If it matters to your team, let us know.
No, and nobody can. The WhatsApp Business API doesn't support group conversations. It's a Meta restriction that applies across every WhatsApp Business tool. Every vendor on the platform works the same way: 1-to-1 only.
Yes. EU-hosted on DigitalOcean. Conversation data, customer records, and message logs all sit in EU regions and are handled under GDPR. It's the default setup, the same on Solo as it is on Enterprise.
Either way works. Run one agent across all your channels so a customer who switches from web chat to WhatsApp keeps their context. Or give WhatsApp its own dedicated agent with a different tone or playbook. You can change the setup per channel whenever you want.
Meta applies tiered messaging limits to WhatsApp Business accounts, and the limit grows as your quality rating goes up. New accounts start small. Inbound traffic, where the customer messages first, has no daily cap, so the throttle mostly only matters for big outbound campaigns. If you're planning one and worried about hitting the ceiling, ping us and we'll look at it together.
Hay doesn't charge for WhatsApp. It's on every plan, from Solo at €50/month up to Enterprise. Twilio's roughly $0.005 per message on top of Meta's rates, billed by Twilio direct. The good news for support teams: customer-initiated conversations don't trigger Meta's template fees, so inbound stays cheap. Check Twilio's pricing page for current rates.
Start reducing repetitive tickets with AI that actually executes actions.