Completion reports, digest and alert fallback

The idea

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.

The problem
Owners were either flooded or missed urgent problems.
Why it matters
Routine news is batched while urgent issues still reach a person.
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.

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

  • Automations from one sentence

    A message with timing words becomes a card (what, when, next three runs, who, credits); Start creates a schedule or event trigger whose runs report back to the asker.

  • Phone line, SMS, calls and voice notes

    The org gets one number for SMS and calls with signed webhooks and an AI disclosure on calls, and WhatsApp voice notes are transcribed and routed like text.

  • A receipt for every task

    Every finished task gets a sealed receipt: what was done, which checks ran and how they ended, the time and the cost, built from records the platform already keeps.

    Recorded walkthrough

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.