Slack vs Deepgram
Side-by-side trajectory, velocity, and editorial themes.
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.
Diarization v2 lands with a 3.3× human-eval edge — Deepgram's contact-center push gets sharper.
Deepgram is shipping in two coordinated lanes: deeper transcription quality (Nova-3 multilingual numerals, Gujarati, profanity filtering across 50+ languages) and a maturing Voice Agent API (managed LLM swaps, third-party TTS controls). The new opt-in diarize_model=v2 brings a new architecture preferred 3.3× over v1 in human eval, with the biggest gains on contact-center audio. Self-hosted images and multi-language SDKs are released on a tight, predictable cadence.
The arc is consolidating around enterprise contact-center workloads: better speaker separation, safer outputs via profanity redaction, and richer language coverage are exactly the gates that block call-center adoption. Voice Agent is becoming a managed-LLM thin layer where customers pick the brain (OpenAI, removed Llama Nemotron) while Deepgram owns ears and mouth. Expect diarize_model=v2 to become the default once telemetry catches up.
Likely next: v2 diarization promoted to default for diarize=true, and a streaming version of the same architecture to extend the contact-center story to live transcription. More managed-LLM additions in Voice Agent, plus continued language fill-in for Nova-3.
See more alternatives to Slack →
See more alternatives to Deepgram →