One shared conversation with topic threads

The idea

Web and WhatsApp share one CEO conversation split into named threads; long threads fold into rolling summaries and every thread is searchable.

The problem
One long chat mixes topics and outgrows what a model can read.
Why it matters
Work stays grouped by topic, and the CEO reads a summary, not a replay.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • WhatsApp front door to the CEO

    The operator reaches the CEO on WhatsApp through signed webhooks from allowed senders only, with templates outside the 24-hour window and recorded delivery statuses.

  • Completion reports, digest and alert fallback

    Completion reports follow a per-conversation level, a daily digest batches status, quiet hours hold non-urgent messages, and a critical alert open 15 minutes also goes by SMS or email.

  • Front-door fast path and lane

    Status questions get answers from runtime state through templates, with no model, and a receipt goes out before any model call. A separate job lane serves what a person waits on, and casual consumer chat starts no work.

  • Many workers on one WhatsApp number

    One business number serves the team: each worker signs its messages, the operator addresses workers by name, replies stick to the last speaker, updates batch under Meta pacing, and a worker can get its own number.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.