WhatsApp front door to the CEO

The idea

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.

The problem
Owners want to run the team from their phone.
Why it matters
Requests, status, decisions and controls work from a normal WhatsApp chat.
Where it stands
In production as of

Recorded evidence

  • Local run on the real backend · Linked identity, activation

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

  • One shared conversation with topic threads

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

  • 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.

  • Business-only WhatsApp guards

    The crew runs only on the customer's own number, answers clear consumer-assistant use with one scoped reply, discloses it is AI, and keeps WhatsApp content out of other orgs and shared outputs.

  • Simplified channel-first client

    A separate, simpler client at its own address, built from the same image and database, sets up channels fast: readiness first, saved preferences and an optional web drill-down.

  • Flow signal triage

    Ideas, requests and problems arrive as signals. Rules decide each signal at once, using the triage employee's accepted lessons, while System One is measured next to them. Each decision becomes held work or started work.

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.