WATI vs Slack
Side-by-side trajectory, velocity, and editorial themes.
SEO feed repositions Wati around Astra, its no-code WhatsApp agent builder
Wati's public feed is dominated by SEO answer-posts centered on Astra, its no-code agent builder for deploying AI agents across WhatsApp, web, and voice with CRM sync. None are dated release notes; the observable signal is a marketing push, not a changelog.
The content consistently frames Astra as the product's center of gravity — bridging prototype tools like Cursor and Claude to production WhatsApp, and syncing leads into HubSpot and Salesforce. The arc visible here is positioning, not shipping cadence; whether these capabilities are newly shipped or repackaged is not determinable from the posts.
Expect continued Astra-centric content emphasizing no-code multi-channel deployment and CRM integration; confirming real releases needs an actual changelog feed.
Slack's developer platform is reorganizing around agents, MCP, and streaming Block Kit surfaces.
Slack's platform work over the past quarter centers on agent development and richer app surfaces. The CLI 4.x line ships agent scaffolding, the Slack MCP server keeps gaining tools, and Block Kit has added streaming APIs plus new block types (cards, carousels, data tables). Security plumbing like PKCE and optional OAuth scopes rounds out a platform being hardened for third-party AI apps.
The direction is to make Slack the surface where AI agents are built, deployed, and rendered. Streaming APIs and new Block Kit blocks exist to host conversational and agent UIs natively, while the MCP server turns Slack into an addressable tool for external agents. Expect continued cadence on both the developer tooling and the runtime surface.
Next likely moves are more MCP server tools and additional streaming-oriented Block Kit components as the agent-app surface matures.
See more alternatives to WATI →
See more alternatives to Slack →