Stackable Labs:
Why Zendesk Messenger needs a customer experience layer
Customers bring real problems to the messenger: an order, a booking, an approval. Stackable Messenger lets brands answer with live data and one-click actions beside the conversation, not just more text inside it.
Brands obsess over customer experience everywhere else. The website is designed down to the pixel, the app is tested screen by screen, even the packaging gets a mood board. Then a customer opens the chat window and lands in a plain text box that has barely changed in fifteen years, other than becoming more automated.
In May we launched Stackable Labs to change that, starting with Zendesk Messenger. This is the why behind it, and what Stackable Messenger actually does.
Messaging became the front door
Messaging is now where a large share of support starts, and for many brands it is the only live conversation they have with a customer before or after a purchase. AI has made those conversations faster and cheaper to run at scale. What it has not changed is their shape: a question goes in as text, and an answer comes back as text.
That works for "what are your hours". It works much less well for the questions customers actually bring:
- Where is my order?
- Can I rebook this flight?
- Can you approve this for me?
- I need to return one item from this order, not the whole thing.
Each of those is about a specific thing the brand already knows about: an order, a reservation, an account, a subscription. The customer wants to see it and do something with it. Instead they describe it, wait while someone (or something) looks it up, and read a paragraph back.
What we kept hearing
We came to this from agnoStack, which since 2019 has put commerce data and actions in front of support agents inside Zendesk for hundreds of retailers. Once the order is in the ticket, agents stop copying email addresses between tabs and start resolving things.
The request we kept getting from those same brands was the customer-facing version of it: can we make the messenger feel like our product? For a long time the honest answer was "sort of". You could theme a widget. You could not put your own interface in it.
An experience layer, not another chatbot
Stackable Messenger adds a layer of extensions around Zendesk Messenger. The conversation, the routing and Zendesk's AI agents stay exactly where they are. Alongside them, a brand can surface interactive, fully branded UI that:
- Shows context before anyone types. Recent orders, an open reservation, an account balance, the last conversation. The customer arrives and the relevant thing is already there.
- Lets customers act. Start a return, pick a new delivery window, submit a form, approve a request, without being walked through it one message at a time.
- Looks like the brand. Your colors, your logo, your layout. It should feel like part of your product, not a generic grey bubble with your name on it.
We think of every extension as a composition of those three ideas: contextual, actionable and on brand. They apply well beyond eCommerce, too: travel, healthcare, SaaS and financial services all have the same pattern of a conversation about one specific thing.
Built for brands, developers and partners
Stackable is a platform, so it works a little differently depending on who you are:
- Brands can browse the Stackable Marketplace and install pre-built extensions without writing code, then configure them for their own messenger.
- Developers get an SDK, a component library and developer documentation for building their own extensions, plus Stackable AI Studio, which turns a description of the experience you want into a working extension you can iterate on against a live preview.
- Technology partners build once and reach every brand on the platform through the marketplace, with no per-customer scaffolding or rebuilds.
Launch partners already building on Stackable include Stylo, ShadowRock, Cordial, SnapCall, Optimate.me, Rivo, Ventrica and Menze, alongside agnoStack itself.
Why it matters now
For two decades, customer experience was the thing every company said set it apart. Then AI chat arrived, and much of the industry quietly accepted that flatter and faster was good enough as long as it was automated. We don't think it is.
What AI really unlocks is instant context and immediate action in the moment a customer needs them. That belongs in the messenger, on the brand's terms, not buried several turns deep in a conversation. Stackable Messenger is how we are putting the experience back into customer experience.
Getting started
Stackable Messenger is available now for Zendesk Messenger. You can get started for free, see it in action on the demo, or head to the developer docs to build your first extension. If you're curious how extensions work under the hood, and where agnoStack fits in next, that's the subject of our engineering post on Stackable Extensions.
