One bot platform, many specialist workflows.

Heyaro does not run 50 separate little apps. It runs one controlled platform where each incoming event becomes a tracked job with routing, approval, and logs.

Plan the first workflow Open private lab

Flow

From customer message to approved action.

The production version keeps the same approval-first behaviour as the demos, but adds queues, saved runs, owner review, and real integrations.

IntakeRouterQueueWorkerApprovalLog

System parts

The pieces needed for real customers.

Intake layer

Forms, email, chat, missed-call webhooks, booking tools, WhatsApp, and CRM events create bot jobs.

Router

The Enquiry Router classifies the message and chooses Quote, Booking, Receptionist, FAQ, Admin, or another specialist workflow.

Queue

Jobs can run concurrently without losing tenant context, status, payload, or approval state.

Workers

Each bot extracts fields, writes owner summaries, prepares draft replies, and creates integration payloads.

Approval dashboard

Owners review, edit, approve, reject, or escalate before customer-facing commitments are sent.

Audit log

Every input, route, draft, approval, and integration handoff is recorded for debugging and trust.

Scale

What happens when 50 bots run at once?

They become 50 jobs in the same platform, not 50 separate systems. Each job carries tenant ID, bot type, payload, status, result, approval state, and integration target.

Tenant config controls business rules
Queue controls load and retries
Approval controls customer-facing risk
Logs make failures visible