Use Case

Support triage with Slack context that stays operational.

These pages exist for real buying and rollout decisions, not generic demo traffic. Each one states the pain, the workflow, the outputs, the commercial fit, and the self-host versus Cloud tradeoff explicitly.

Pain

Important support context is scattered across Slack threads, handoffs, and DMs. The cost is slow escalation and operator time spent reconstructing what already happened.

Workflow

Run slack_channel_summary on your support channels for the current state, then slack_extract_action_items for explicit owners and deadlines. The support_inbox profile organizes channels + priority customers; profile-driven structured briefs are in development.

Signals this page is relevant

  • Escalation context is spread across multiple support or shared channels
  • A human operator is rewriting the same summary or handoff note repeatedly
  • Support managers need explicit action items instead of a message dump

Repeatable workflow steps

  • Pick the support channels + priority customers that make up your support inbox.
  • Run slack_channel_summary + slack_extract_action_items to collapse the inbox into a structured brief.
  • When the scheduled morning catch-up DM ships (Pro/Team — in development), the brief will land at 8am workspace time automatically.

Named outputs

  • Open threads with ack lag
  • Owner gaps + escalations
  • Next actions per thread
  • Workflow profile: support_inbox
  • Target brief shape: support_inbox target shape: {open_threads, ack_lag, owner_gaps, escalations, next_actions}
  • Claude-first, Gemini CLI supported

What good looks like

  • Once the morning DM ships (in development), a new operator can read it and know the state of the inbox in under two minutes. Today, run slack_channel_summary at the start of every shift for the same brief.
  • Owners and deadlines are explicit instead of implied in chat.
  • Free tier is enough to validate the pattern before upgrading to Pro for unlimited.

Prompt starter

Use this as the initial request in Claude or Gemini CLI after the endpoint is connected.

Run slack_channel_summary on my support channels with focus 'blockers', then slack_extract_action_items for this morning's standup.

Anonymized example output

Summary: current state compressed for the next operator. Action items: owner + deadline when available. Decisions: commitments already made in Slack. Handoff: what the next person needs before they open the raw channel.

Plan fit

Pro is the default fit for solo support operators. Team is the fit when 2-10 people share the inbox and need synced workflow profiles.

Self-host vs Cloud

Self-host the OSS package if you want to define support_inbox profiles locally without the AI brain. Use hosted when AI summaries and action-item extraction matter more than transport ownership.

Premium fit

Pro at $19/mo is the right fit for a solo support operator running daily. Team at $49/mo flat for 5 workspaces is the fit when 2–10 people share the inbox. Ops engagement starts when the support team needs SLA, custom retention, or multi-tenant isolation.

Trust and buyer review

  • Use /status for the live hosted status contract.
  • Use the Ops engagement page for SLA, custom retention, or SOC2 questions.
  • Use the security page for buyer-facing controls, storage, and analytics disclosure.
  • Use official vs managed when the team is still deciding between Slack's official path and the managed commercial path.
Security Ops engagement Official vs managed