Thena Wants to Kill the Support Ticket, Starting Inside Slack

Ask a founder where their most important customer conversations happen, and a growing number will not point to a help desk or a support portal. They will point to a shared Slack channel - the one where a customer drops a bug report at 11pm, asks about an invoice on Tuesday, and threatens to churn on Friday. For years, that channel was a black hole. The messages arrived, someone maybe saw them, and nothing was tracked. Thena was built to close that hole.

Founded in 2022 by Ankit Saxena, Govind Kavaturi, Mike Molinet and Unmukt Raizada, Thena is an AI-first customer support platform aimed squarely at B2B teams. Its core argument is simple and a little contrarian: the ticket portal is a relic of the web-form era, and modern business customers do not want to leave the tools they already use to ask for help. So Thena moves support to them - into Slack, Microsoft Teams, email, live chat and Discord - and lets AI agents do the unglamorous work of turning a stray message into a tracked, routed, resolvable ticket.

The idea did not arrive as a whiteboard abstraction. Saxena ran enterprise post-sales at Branch, the mobile linking company, and watched customer conversations scatter across Slack, Teams and email with no system holding them together. It was, in his telling, messy, manual and unsustainable. Molinet had co-founded Branch back in 2014 and helped scale it before leaving to start Thena. When two people who have already built something at scale walk away to solve a problem they lived with, the problem is usually real.

The bet: meet customers where they already are

There is an old product lesson hiding in Thena's design. The best way to win a channel is not to build a slightly better version of the thing people avoid - it is to build inside the place they already spend all day. Legacy support tools sell you a system and quietly ask your customers to adapt to it: open the portal, create an account, file the ticket, check back later. Most B2B customers simply will not. They message you in the channel that is already open on their second monitor.

Thena's answer is to make that channel first-class. Its AI detects when a Slack message is actually a request, opens a ticket automatically, and attaches the customer context, the account history and the SLA clock. Support leads get boards, triage and CSAT scoring on top of conversations that used to vanish into thread scroll. The company connects to engineering tools like Jira and Linear, and to CRMs like Salesforce and HubSpot, so a support thread can become an engineering issue without anyone copy-pasting.

AI that is boring on purpose

Plenty of companies promise that AI will transform support. Most of the demos lean on a dazzling chatbot. Thena's pitch is more mundane, and probably more useful: detect the request, open the ticket, route it to the right person, follow up. The company talks about autonomous agents that can handle roughly half of the workload - cleaning up tickets, chasing customers for missing details, keeping boards tidy. It has shipped an AI knowledge base for branded help centers, an Agent Studio for building custom agents, and an MCP server so the system can plug into the broader AI tooling stack. It integrates with Claude directly.

The throughput claims follow from that loop. Thena says support teams using it are hitting levels of output that looked unthinkable two years ago, and it projects that support costs can shrink by close to a third while experiences improve. Numbers a vendor puts on its own site deserve a skeptic's eyebrow. But the customer evidence points the same direction. Austin Hay, co-founder of Clarify, describes a single support lead now covering hundreds of customers across Slack, email and chat - work that used to require a four-person team.

That line is worth sitting with, because it explains why Thena is not framing itself as a cheaper help desk. If support is connective tissue, then the transcript of every customer conversation is one of the richest datasets a B2B company owns - a live feed of what is breaking, what is confusing, and who is about to leave. Sitting on top of the messaging layer, Thena is positioned to turn that feed into structured signal instead of lost threads. The ticket is the byproduct; the customer intelligence is the prize.

There is also a quieter reason the boring approach matters. Support is a job where the cost of a flashy mistake is high - an over-eager bot that hallucinates a refund policy or closes a live incident does real damage. Thena's framing keeps the human in the loop where it counts and pushes the AI toward the parts of the job that are genuinely mechanical: reading a thread, recognizing a request, tagging it, nudging a customer for the missing log file. That is where most of the wasted hours actually hide, and it is a safer place to hand a machine the keys than the moment a customer is angry and a policy call is on the line.

The company it is chasing

Thena is entering a category that is neither empty nor sleepy. The incumbents span IT service management and customer communication: Microsoft, Atlassian's Jira Service Management, Oracle, the ITIL-native EasyVista, and Text, the company behind LiveChat. These are large, entrenched, and in several cases very good at what they were built for. ServiceNow, not even on Thena's named list, dominates the ITSM market outright.

Against that lineup, a roughly $7.2M seed-stage company is a rounding error. But scale is not always the advantage it looks like. The incumbents were built for the portal-and-form world, and a lot of their design assumes the customer will come to the tool. Thena's wedge is being native to the channel those tools bolt onto as an afterthought, and being AI-first rather than AI-retrofitted. The funding backs the thesis rather than proving it: roughly $2.2M in pre-seed from Pear VC and Tenacity Venture Capital, then a $5M seed co-led by Lightspeed and First Round Capital.

What you can actually do with it

Strip away the positioning and Thena is useful in a concrete way. If you run a B2B company that supports customers in shared Slack or Teams channels, it gives those conversations a spine: tickets, SLAs, ownership, CSAT and reporting, without asking anyone to change where they talk. If you are a lean team, the AI agents absorb the repetitive triage and follow-up that quietly eats a support person's day. If you are cross-functional, the Jira and Linear links mean a customer complaint can become an engineering issue in a click, with the thread attached. And if you want a branded help center, the AI knowledge base builds one from the material you already have.

The honest caveats belong here too. Thena is young, its named customer set is concentrated among developer-tool and infrastructure companies - Vercel, Mixpanel, incident.io, WorkRamp, Etsy - and the boldest efficiency numbers come from the vendor. Pricing starts around $79 per user per month, which is not a hobbyist tool. For a team drowning in untracked Slack requests, though, the math tends to work itself out fast. The question is not whether the portal era is ending. It is whether the company that replaces it will be a startup like Thena or an incumbent that finally moves into the chat window it has ignored.

Either way, the direction is set. B2B customers have already voted with their behavior - they live in messaging, and they are not going back to the form. Thena's whole company is an argument that support software should follow them there. So far, the customers who have tried it seem to agree.