Krisp vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Krisp's Call Center AI build-out: steady cadence, admin tools and voice translation expanding weekly.
Krisp is fully committed to the Call Center AI suite — every recent update is in that surface, none in the consumer noise-cancellation product. Voice Translation is the most active sub-area (new languages, refreshed voices, extended prompts, usage-reporting fixes), with parallel work on Accent Conversion, Agent Assist, Speech Analytics, and admin controls for team-level visibility. Releases ship in two cadences: a weekly web roll-up and a numbered desktop client (2.77.5 just landed).
The trajectory is toward an enterprise-credible BPO-grade product: admin scalability, accurate usage telemetry, and language coverage are the gates contact-center buyers run their evaluations on. Krisp is checking those boxes methodically rather than dropping headline features. The consumer-noise-suppression heritage is increasingly background context, not the active product.
Expect more Voice Translation language additions and a continued push into admin/team-management surface area. A pricing or packaging change around the call-center tiers is likely if usage reporting is stabilizing, since reliable telemetry typically precedes meter changes.
Slack rebuilds its developer platform around shipping in-channel AI agents.
Slack is well into a platform pivot, restructuring its CLI, Block Kit, and APIs around AI agent use cases. The 4.0.0 release in April formalized this with an agent-scaffolding command, sample agent apps, and a live-reloading dev workflow. Recent additions — streaming chat APIs, Card/Carousel/Alert blocks, and continued MCP server expansion — show the surface area for in-Slack agents widening fast.
The platform is shifting from 'agents can post messages' to 'agents are first-class UI citizens'. The new chat.startStream / chat.appendStream / chat.stopStream methods change what an agent reply looks like, and the Card and Carousel blocks hint at richer multi-turn agent flows. Security work on PKCE and optional scopes is keeping pace, which tells you third-party agent developers are the audience, not just first-party features.
Expect Slack to publish reference agents and likely a discovery or marketplace surface for agent apps within the next minor cycle, with streaming Block Kit becoming the canonical pattern shown in the docs.
See more alternatives to Krisp →
See more alternatives to Slack →