Slack vs WATI
Side-by-side trajectory, velocity, and editorial themes.
Slack is quietly rebuilding itself as a runtime for third-party agents.
Slack's developer platform has shifted its center of gravity from bots-that-reply to agents-that-act. The last month is dominated by agent primitives: apps can now receive the context a user is looking at, Slackbot can call external tools over MCP, and a dedicated agent messaging surface ships alongside steady CLI and Block Kit work.
Each release fills in a piece of an agent platform — context in, tools out, and a native place for agents to converse. Block Kit is gaining richer primitives (containers, data visualization) that read as the display layer for agent output. Three CLI releases in a month show the tooling keeping pace with the expanding surface.
Expect the next moves to connect these pieces: agent context feeding MCP tool calls, and Block Kit's new blocks becoming the standard way agents render results in-channel.
Wati floods search with Astra-AI landing pages, but ships no visible changelog.
The crawled feed is Wati's SEO and marketing content — 'best WhatsApp API platform' pages, comparisons against Meta Business Agent, and landing copy for Astra, its AI-agent product (cross-session memory, native WhatsApp voice). It reads as marketing copy, not release notes.
The messaging centers Astra as an AI-agent layer over the WhatsApp Business API — memory, voice, no-code agent building. The intent is clear, but this feed shows positioning rather than shipped changes.
Expect continued Astra-centric AI-agent messaging; without a real changelog source, product-move forecasts aren't supportable from this feed.
See more alternatives to Slack →
See more alternatives to WATI →