Voice OpsBETA
ReceptionOS

ReceptionOS

A mind for voice ops.

Every call answered. Every lead orchestrated.

ReceptionOS is the Taskclan Engine running your front desk — voice, SMS, follow-up, and conversion agents coordinated as one. Set the goal; the engine answers, qualifies, books, and converts on its own.

— Identity
Surface
Web dashboard + voice/SMS
Audience
Service businesses
Status
In production · Beta
Domain
Voice + lead operations
Engine count
6 / 7 minds active
— Minds Awake

The hive,
shaped for voice ops.

ReceptionOS wakes 6 of the 7 AI minds in the engine. Same orchestration, different cast on stage.

M01

Perception

Active
M02

Planning

Active
M03

Voice

Active
M04

Decisioning

Active
M05

Generation

Sleeping
M06

Memory

Active
M07

Coordination

Active
— What it does

Capabilities,
running live.

Everything below is the hive at work in ReceptionOS — orchestration coordinating the active minds against the goal.

C01

AI voice agents answering 24/7.

Voice + Perception pick up every call with on-brand cloned personas. No missed calls, no after-hours gaps, no voicemail tag — just real conversations.

C02

Autonomous booking and qualification.

Planning + Decisioning qualify the lead, check the calendar, and book the appointment — mid-call, with the right window, on the right tech.

C03

Coordinated SMS, callbacks, and re-engagement.

When the call ends, Coordination keeps working — confirmations, reminders, drip sequences, win-back flows. All routed through one engine, not five tools.

C04

Real-time intelligence on every lead.

Memory + Decisioning score every interaction live. You see where revenue is coming from, where it's leaking, and what to fix — without staring at dashboards.

C05

Multi-language voice with cloned personas.

Voice handles English, Spanish, French — same brand, same warmth. The engine routes by caller language; no extra setup.

C06

Payment collection mid-conversation.

Decisioning + Voice handle deposits, holds, and full payments without escalating to a human or breaking the call flow.

— In Motion

Real moments,
real flows.

A few real scenarios where ReceptionOS fires up the hive — prompt at the top, what the engine does next.

Prompt
Caller at 9:47pm — emergency plumbing.
Engine flow
Voice picks up instantly, Perception reads urgency, Decisioning checks dispatch availability, Planning books the soonest slot. Coordination texts the tech and the customer the same minute.
Prompt
Lead from Tuesday hasn't booked yet.
Engine flow
Memory flags the cooling lead. Coordination wakes a re-engagement sequence — SMS first, then a callback from Voice if needed. Decisioning chooses the angle based on what the lead originally asked about.
Prompt
Caller wants to put down a deposit.
Engine flow
Decisioning confirms eligibility, Voice walks the caller through, Coordination logs the transaction and sends the receipt — all without a human reaching for a card reader.
— Built on the Engine

ReceptionOS is one shape of the hive.

Same orchestration layer powers Nani, ReceptionOS, and GameNova. Different surfaces. Different minds awake. One engine underneath.

— Other Shapes

Same engine. Different cast.

— Wake the Hive

Ready for
ReceptionOS?

Every call answered. Every lead orchestrated.