Slack agent
Known limitations
What the Slack agent does not do today, so you can set expectations with customers accurately.
Known limitations
These describe the product on main today. Set expectations from this list rather than from older plans.
Product scope
- Private Messages only. Business requests run only in the person's one-to-one Messages conversation. Channel mentions get a private nudge, and partner-mapped channel handling is not reachable from Slack.
- Diagnose is not saved. Slack shows the dormant list but cannot save a diagnosis, so recommended next actions normally do not appear.
- No staff actions. Programme go-live and Riley publishing are refused in Slack. Brief promotion is not available from Slack either.
- Partner figures are read-only. Revenue, leads, trials and activations come from PartnerStack.
- Single suggested prompt. The agent view offers Help only. Help then lists examples that match the person's access.
- Large drafts. A draft too large to review in Slack must be reviewed in Activate. Partner branding must be saved in Activate.
Depends on the environment
- Default is read-only. Revenue logging, brief creation, setup, decisions and dispatch need the confirmed-writes runtime. Generation also needs paid generation and matching generation accounting.
- Existing links keep their scopes. Moving an environment from read-only to writes does not upgrade existing links. People must reconnect.
- Production. The repo's production sync workflow carries no Slack settings. Check with engineering before promising Slack to a production customer.
Commercial
- Stripe is off. Online purchase and collection exist but are disabled by default. Launch billing is finance-issued invoices from usage reports.
- No automatic refill or renewal. Credit ends with its period.
- Holds. Each call holds a worst-case amount first, so small allocations are refused even if some credit remains.
Operations
- Configuration needs a restart. Runtime settings are read when the API starts.
- Installation state capacity. Public install state is bounded per Redis; heavy anonymous install traffic can hit that ceiling.
- Uncertain writes are not retried. If a write's outcome is unknown, the agent says so and the person checks before repeating.