Customer.io vs Repurpose.io

Customer.io came out of a summer wave carrying more than ten features, and the ones that matter reshape what a message can be triggered by and what it can know: geofences make physical location a native trigger, and reusable knowledge sources give LLM actions a workspace-scoped context layer. The newest release moves the AI agent out of the product entirely, into Slack, where it can be mentioned in a thread or handed work directly.

Two patterns run in parallel. One absorbs things customers previously bolted on — third-party geofencing, per-prompt context pasting — and makes each a configurable primitive. The other, newer one changes where the product is operated from: after building the agent and giving it a knowledge layer, Customer.io is now placing it in the collaboration tool teams already sit in. Delivery control has followed its own line, with per-channel rate limits and wait-before-continuing giving operators throttles they would otherwise build around.

The Slack app is rolling out through late August, so the near-term signal is what the agent is permitted to do there rather than answer. Given that knowledge sources were already extended to the Agent on release, expect the Slack surface to inherit that context layer rather than get its own.