Answers the basics
Hours, service areas, availability, menus, booking questions, quote prep, pickup/delivery notes, and repeated FAQs.
Wira Business
Customers message. Wira gets the next step ready.
Hosted Wira is for a business number: useful first replies, detail collection, owner handoff, monitoring, and a draft-first launch path. Payment starts provisioning; setup finishes after the number, business facts, and launch rules are confirmed.
What this is
A customer-message desk, not ChatGPT on WhatsApp.
Collects useful details
Customer name, need, timing, location, preferred contact, and the facts the owner needs before replying.
Hands off safely
Draft-first at launch, owner escalation for unclear promises, and no card numbers, passwords, or sensitive credentials in chat.
What gets built
The hosted lane has real parts.
| Part | Included in base | Extra when needed |
|---|---|---|
| WhatsApp lane | Cloud API path or verified channel plan for the business number | Meta template delivery charges and provider/BSP fees |
| Runtime | Hosted service, monitoring, health checks, and update path | Higher-volume infrastructure or dedicated compliance requirements |
| Assistant brain | Business context, prompt tuning, approval policy, and memory setup | Premium model budget, heavy retrieval, or custom data connectors |
| Phone/SMS/voice | Scoped only if useful | Twilio number/SMS, Vapi/voice minutes, call routing |
| Owner handoff | Lead summary and next-action packet | CRM, POS, booking, inventory, or payment integrations |
After payment
Four steps before customers feel it.
Provision
Stripe confirmation starts the hosted resource path and operator alert.
Map the business
We collect the business name, common questions, policies, and first workflow.
Connect WhatsApp
We confirm the number: Cloud API, verified channel plan, or provider option.
Launch narrow
First live customer messages create drafts. Auto-send expands after review.
Tool readiness
Connect only what helps the handoff.
The first channel.
Bring the current customer number, who controls it, and whether it already sits in a Meta Business account.
The reply map.
Hours, services, locations, price ranges, refund rules, booking rules, menus, links, and escalation lines.
The next step.
Add Stripe, Square, invoice, order form, or deposit links only when the chat should send customers there.
The second wave.
Add these after the first WhatsApp workflow is clean, unless the business already depends on them.
Customer view
They message the business.
The customer sees the business WhatsApp display name. Wira is the admin/product layer. Hermes is not shown in customer chat.
Launch checks
- Webhook challenge and signed inbound message pass.
- Business prompt uses the client display name.
- Draft creation works for the first workflow.
- Owner approves one outbound send before wider automation.
Best practices
We start narrow on purpose.
Launch safe
- Start draft-first for new leads.
- Write the quote/refund/escalation rules before automation widens.
- Keep the owner-visible handoff simple.
- Review real conversations before adding more autonomy.
Do not use Wira for
- Card numbers, bank details, passwords, or private credentials.
- Final legal, medical, or regulated advice.
- Refund disputes without a written policy.
- One-off promises the owner has not approved.
Scope it
Tell Nia what the business actually needs to answer.
Use this if you want the number, provider path, approval rules, and add-ons checked before payment. If you already know you want hosted Wira, the buy button starts the payment-confirmed setup path.
If the business also needs a better website, order form, quote path, or payment handoff, say that here. Wira works best when there is a real business surface behind it.