← Back to home
Comparison · Comms

SlickText vs Slack

Side-by-side trajectory, velocity, and editorial themes.

S3.8

SlickText adds RCS, pushing past plain SMS into verified, branded business messaging.

◆ Current state

SlickText runs a heavy SEO content engine — templates, listicles, vertical guides, awards posts — but the substantive product move is the addition of basic RCS messaging, bringing verified business identity and richer formatting to a platform built on plain SMS. Everything else in the recent feed is marketing and category positioning.

◆ Where it's heading

The product is broadening from SMS-only toward a multi-format messaging stack where channel trust and branding matter. RCS gives SlickText a credible answer to the deliverability and impersonation problems that plain text marketing can't solve on its own, and slots it against enterprise rivals it keeps writing comparison content about.

◆ Prediction

Expect RCS to move from 'basic' to feature-complete — branded sender profiles, rich cards, and read receipts — and to become a headline differentiator in the comparison content SlickText already publishes against Attentive and EZ Texting.

Slack logo
Slack
COMMSCOLLAB
6.3

Slack's developer platform is reorganizing around agents, MCP, and streaming Block Kit surfaces.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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 SlickText
See more alternatives to Slack