Slack and Teams as work channels

The idea

Slack and Teams carry approvals and format posts, and the new client adds native request, review, Start and result flows with one-use personal-chat linking.

The problem
Many teams work in Slack or Teams, not WhatsApp or a console.
Why it matters
People request and decide work where their team already talks.
Where it stands
Partly built as of Approvals and posts work; the native request flows are built and switched off.

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

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

  • Approvals on web, WhatsApp, Slack and Teams

    A governed action waits for an approval that eligible people decide on the web, WhatsApp buttons or Slack/Teams direct messages; the requester never decides, and owned resources are approved by their owner.

  • Formats over the timeline, standup included

    Templates with slots turn timeline entries and state facts into a daily standup and other reports, copied as text or Markdown or posted to Slack on a schedule.

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

  • Escalation routing and reply resume

    A question goes to its addressee wherever they can be reached: a ticket, a pull request, Slack, Teams or a direct message. A reply there resolves it and resumes the item, and an answer given on the platform is posted back.

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.