Knak Is Going Omnichannel, Starting With SMS and RCS
Knak began with email and added landing pages, and this September we are extending the same production platform into cross-channel messaging, starting with SMS and RCS. This post is an early preview of what is coming: messaging built into the workflow your team already uses rather than bolted on as a separate tool, plus the road we are taking to get there.
Why messaging belongs with email and landing pages
The value of a marketing production platform was never building one email. The value is coordinating design, creation, approval, and deployment at scale, so a distributed team ships on brand without rebuilding the process for every campaign. Adding messaging makes that coordination matter even more.
Stand up a new channel as a separate tool and you inherit a second silo. That means another place to manage brand assets, another approval path, another consent and compliance regime to track, and another login for a team that already has too many. The work of keeping a single text message on brand looks small until you multiply it across regions, campaigns, and the reviewers who sign off on each one. Every disconnected channel is overhead that compounds.
Enterprise teams have been clear about what they want instead. 89% rank integration as their top priority for new technology, and 61% in the same research point to silos as the single biggest barrier to getting work done. A channel that lives outside your creation flow is a new silo by definition.
The better path is to treat every channel as a surface of the same campaign. The brand components, content, and approval pass that already produce your email and landing pages should produce your messaging too, from one shared pool. That principle sits behind everything we are building here.
Why we're adding messaging now
Messaging is where mobile attention has been moving for years, and the channel that was missing at enterprise scale has quietly become viable. RCS, the richer successor to SMS, brings branded senders, verified business profiles, images, and tap-through buttons to the native messaging app, so a text from your brand can look and behave like a small landing page. It became manageable across iPhone with iOS 18, and in the time since it has reached the large majority of US iPhones. That closes the gap that kept RCS a mostly-Android story and makes branded, rich messaging realistic for a US enterprise audience for the first time.
The honest read is that this is a trajectory, not a finished shift. Enterprise B2B messaging today still skews operational, toward reminders, alerts, and confirmations, and most of the eye-catching engagement numbers come from consumer retail. We will not dress a B2C open rate up as a B2B promise. What has genuinely changed is that the channel is now real enough to build for, and the teams that get their production process ready now will not be scrambling to assemble one when messaging becomes table stakes.
Starting with SMS and RCS
We are starting with SMS and RCS because it is the channel enterprise teams ask about most and the one that gains the most from how Knak already works. You will build a message the way you build an email in Knak today, from approved brand components, through the same review and approval pass, ready to deploy to the platforms you already send from. The message will come out on brand and compliant before it ships, produced in minutes by the people who already build your campaigns.
That matters because the usual alternative is a separate tool with its own learning curve, its own brand setup, and its own approval chain. Bringing messaging into the production layer means the skills your team already has transfer directly, and the brand and governance rules you already trust travel with the message.
Because RCS is still rolling out unevenly across carriers and devices, a message built for RCS falls back to SMS when a recipient cannot receive the richer version, so the send reaches them either way. You design for the best experience and still cover everyone. The short demo below shows the full build, start to finish.
What this means for your team
For the people who build campaigns, the change is meant to be small by design. There is no new tool to learn and no second brand library to maintain, because messaging draws on the same components and the same review flow as the email and landing pages your team already builds. That is the whole point of putting messaging in the production layer rather than beside it.
For the people who own brand and compliance, the change is that messaging stops being a blind spot. Brand rules and workflows live in the same place as everything else, so the controls you already apply to email apply to the channel sitting next to it. Adding a channel has always meant adding governance. Producing that channel from one pool is what keeps the governance from fragmenting across teams that do not talk to each other.
The road to omnichannel
SMS and RCS are the first step on a longer path. Email and landing pages are live today, messaging arrives in September, and the channels marketers ask about next, display and social ads, follow from late 2026 into 2027. The roadmap below shows where Knak is and where it is headed.
Every step on that road follows the same principle. A new channel should join the production workflow your team already runs, so a growing list of channels stays a single platform rather than a stack of disconnected tools.
Where this is headed
The goal is simple to say and hard to deliver, which is exactly why it is worth building. Produce once from a shared pool of brand assets, content, and approvals, then deploy to every channel your campaign touches, with one source of truth behind all of it. SMS and RCS are where that starts, and the road from here runs through every surface your audience is on. We will share more as September approaches. For now, see how Knak brings email and landing pages into one production workflow today.
