Slack has become the place where modern teams talk, make decisions, share updates, ask for help, and solve problems in real time. That speed is useful, but it also creates a hidden problem. Support requests get buried in channels. Customer questions disappear inside long threads. Internal teams jump between DMs, mentions, and half-finished conversations. By the time someone tries to measure what actually happened, the work is scattered across too many messages.
That is the kind of mess Tom Bachant is trying to clean up with Unthread.
Bachant, the cofounder and CEO of Unthread, has focused the company on a simple but important idea: support should happen where people already work, but it still needs structure. Instead of forcing teams to leave Slack and move into a separate helpdesk for every small issue, Unthread turns Slack conversations into organized support workflows. It captures requests, creates tickets, routes work, suggests answers, and helps teams understand the patterns behind recurring problems.
The result is a product story that feels very relevant right now. Companies want faster support, but they do not want more operational clutter. They want AI, but they want it connected to real work, not floating around as another isolated chatbot. Tom Bachant’s success with Unthread comes from connecting those needs in a practical way.
Who Is Tom Bachant?
Tom Bachant is a startup founder with a background in building software for real operational problems. Before Unthread, he founded Dashride, a mobility software company that was later acquired by Cruise in 2018. That earlier experience matters because it shows a pattern in his work. Bachant is not only interested in software that looks polished on the surface. He tends to focus on systems that help teams manage complexity behind the scenes.
With Unthread, that complexity lives inside workplace communication.
Modern teams already rely heavily on Slack, especially in fast-moving technology companies, B2B SaaS businesses, customer success teams, IT departments, and HR teams. The challenge is that Slack was built for conversation, not always for accountability. When a request comes in, someone may reply quickly, but the team still needs to know who owns it, whether it was resolved, how long it took, and whether the same issue is happening again and again.
Bachant’s founder insight was to see that support was already moving into Slack. The opportunity was not to pull people away from that behavior. The opportunity was to make that behavior more organized, measurable, and intelligent.
What Is Unthread?
Unthread is an AI-powered helpdesk built natively into Slack. It helps companies turn Slack messages into support tickets, automate common answers, route requests to the right people, and track support work without forcing every conversation into a separate system from the start.
The product is especially useful for teams that already handle support through Slack. That can include customer support in shared Slack channels, IT requests from employees, HR questions about onboarding or benefits, or customer success teams managing enterprise accounts. In all of these cases, the first message often arrives in Slack before it becomes an official ticket.
Unthread gives those messages structure.
A customer might ask for help in a shared channel. An employee might ask IT for access to a tool. A new hire might ask HR about a policy. A customer success manager might flag a product issue. Without a system, those requests can depend on whoever notices them first. With Unthread, the conversation can become a tracked support item with ownership, status, context, and a path to resolution.
That is where the AI side becomes more useful. Unthread is not just using AI to generate replies. It is using AI inside a workflow where the answer, the ticket, the routing, and the resolution process are connected.
Why Slack-Based Support Became So Messy
Slack changed how teams communicate because it made work faster and more informal. Instead of waiting for emails or filling out forms, people could ask for help in a channel and get a response quickly. For small teams, that can feel efficient. Everyone sees what is happening. Someone jumps in. The issue gets handled.
But as a company grows, the same habit becomes harder to manage.
A support request in a channel can look like a normal message. A serious product issue can be buried under casual discussion. A customer question can become a long thread with multiple people replying at different times. A teammate might take ownership in a DM, leaving everyone else without visibility. Managers may know that support feels busy, but not know which requests are taking the longest or which issues are repeated every week.
The problem is not that Slack is bad for support. The problem is that Slack alone does not give support teams enough structure.
Traditional helpdesks solve part of this problem by creating tickets, queues, categories, response time tracking, and reporting. But those systems can feel separate from where the work is already happening. Teams end up switching between Slack and a ticketing platform, copying context from one place to another, or asking people to submit requests through a process they do not naturally use.
That gap is exactly where Unthread fits. It does not treat Slack as noise to escape. It treats Slack as the starting point for smarter support.
How Tom Bachant Found the Opportunity Inside the Chaos
Many startup ideas come from noticing a workflow that people are already doing manually. Tom Bachant’s work with Unthread follows that pattern. Teams were already using Slack to support customers and employees. The problem was that they were doing it in a way that was hard to scale.
For B2B companies, shared Slack channels have become a common way to support important customers. They feel personal and direct. Customers like having quick access to the team. The company gets a closer relationship with the account. But the model creates pressure as more customers, more channels, and more requests enter the system.
A founder can look at that and see two options. One option is to tell companies to stop using Slack for support. The other is to accept that Slack is where the relationship already lives and build a better layer around it.
Bachant chose the second path.
That decision is important because it makes Unthread feel aligned with real user behavior. People do not want another tool simply because it exists. They want a product that removes friction from the way they already work. Unthread’s strength is that it does not ask teams to abandon their communication habits. It helps those habits become more reliable.
How Unthread Turns Slack Conversations Into Smarter Support
Unthread’s value becomes clearer when you look at the support workflow step by step. A message comes into Slack. Instead of staying as an untracked comment, it can become an organized support request. The platform can help identify what the request is about, assign or route it, suggest a response, and keep the team aware of progress.
Capturing Requests Where They Happen
The first advantage is intake. Support systems often fail when people do not use the official process. Employees keep asking IT questions in Slack. Customers keep posting in shared channels. Team members keep tagging whoever they know personally.
Unthread works with that behavior instead of fighting it. The request can start in Slack, where the user is already comfortable asking for help. This makes the process feel lighter for the person asking the question while still giving the support team a more structured way to manage it.
Turning Messages Into Tickets
A Slack message is easy to send, but it is not enough on its own. A support team needs to know what the request is, who owns it, how urgent it is, whether it has been answered, and when it was resolved.
Unthread helps turn those conversations into tickets. That means the message gets a support identity. It becomes something the team can track instead of something people hope they remember. This is especially valuable when multiple team members are involved, because it reduces the risk of duplicate work or missed follow-ups.
Using AI to Generate Helpful Answers
AI becomes useful when it saves people from repeating the same answer all day. In support environments, many questions follow familiar patterns. Someone asks about access. A customer asks about a known issue. An employee needs a policy link. A team member wants a quick troubleshooting step.
Unthread can use AI to help generate answers for those common requests. The goal is not to make every support interaction feel automated or cold. The goal is to give teams a faster starting point, reduce repetitive work, and let humans focus on issues that need judgment.
Routing Work to the Right Human
Good support is not only about answering fast. It is also about getting the request to the right person. Some issues belong with IT. Some belong with HR. Some need customer success. Some need engineering. Some can be handled by an AI agent, while others need a human who understands the full context.
Unthread’s routing function matters because it helps prevent requests from bouncing around. When support work is scattered across Slack, ownership can become unclear. A smarter workflow gives the request a destination.
Tracking Patterns Teams Usually Miss
One of the most valuable parts of structured support is pattern recognition. A single request may look small, but repeated requests can reveal a bigger problem. If customers keep asking the same onboarding question, the documentation may need improvement. If employees keep asking for access to the same tool, the internal process may be too slow. If product issues keep appearing in customer channels, the support team may be seeing early warning signs before leadership does.
Unthread can help teams move from individual messages to useful support data. That is where Slack support becomes more than a communication channel. It becomes a source of operational insight.
Why Unthread Is More Than Another AI Chatbot
The AI market is crowded with products that promise faster answers. Some are helpful, but many feel like a thin chatbot layer placed on top of an existing workflow. Unthread’s angle is different because it is not only about generating text. It is about connecting AI to the messy process of support work.
A support request does not end when an answer is written. Someone has to decide whether the issue is solved. Someone may need to escalate it. Another system may need to be updated. A customer may need a follow-up. A manager may need to know whether the team is falling behind.
That is why workflow matters.
Unthread sits at the intersection of conversation, ticketing, automation, and human support. It uses AI where AI can help, but the bigger product idea is about making support accountable inside the place where teams already talk. That makes it more practical than a generic bot that can answer questions but cannot manage the full support lifecycle.
The Customer Support Problem Unthread Is Solving
For many B2B companies, customer support no longer happens only through email or a portal. High-value customers may have shared Slack channels with the vendor’s support, customer success, or product team. This creates a more personal experience, but it can also become chaotic.
A customer might post a bug report. A product manager might reply. A support rep might add context. An engineer might ask a follow-up question. Then the thread gets quiet. Was it resolved? Did anyone create a ticket? Did the customer get a clear answer? Did the issue show up again with another account?
Without structure, shared Slack support can become a liability. It feels responsive in the moment, but it becomes harder to manage as the company scales.
Unthread helps by bringing helpdesk discipline into that environment. The customer still gets the convenience of Slack, while the company gets a clearer way to track and resolve requests. That combination is important for customer trust. People do not only want fast replies. They want confidence that their issue will not disappear after the first response.
How Unthread Helps IT and HR Teams Work Faster
The same problem appears inside companies as well. IT and HR teams are often flooded with small but important requests. Someone needs access to a software tool. Someone has a laptop issue. A new employee has onboarding questions. A team member wants to understand a policy. A manager needs help with an internal process.
Many of these requests arrive in Slack because Slack is the easiest place to ask. But when every request comes through a channel, support teams can spend too much time sorting, repeating, and chasing context.
Unthread gives internal teams a way to handle these requests with less friction. The employee can ask in Slack, while the support team gets ticketing, routing, automation, and visibility behind the scenes. AI can help answer repetitive questions, and human agents can focus on the requests that need care, judgment, or deeper problem-solving.
For growing companies, that balance matters. Internal support should feel easy for employees, but it should not become invisible labor for the teams responsible for handling it.
Tom Bachant’s Success With Unthread
Tom Bachant’s success with Unthread comes from building around a problem that is easy to recognize but hard to solve well. Slack support looks simple from the outside. A message comes in, and someone replies. But beneath that simple exchange are questions of ownership, speed, visibility, customer experience, internal efficiency, and long-term learning.
Unthread has gained attention because it addresses that deeper layer. The company joined Y Combinator’s Summer 2022 batch and has positioned itself in the growing space between AI, service management, customer support, and workplace collaboration. Public coverage has also highlighted Unthread’s funding, its Slack-native approach, and its work with teams that need faster support operations.
The achievement is not only that Bachant attached AI to Slack. The stronger story is that he found a way to make AI useful inside a support workflow that companies already rely on. That is a much harder and more valuable problem than simply building a bot that can answer a few questions.
Why Unthread Fits the Future of Work
The future of work is not just remote or hybrid. It is also conversational. More decisions, requests, and updates happen inside tools like Slack and Microsoft Teams. People expect quick responses because the workplace itself has become more real-time.
At the same time, companies cannot afford to let every request become a manual interruption. Support teams need systems that keep work moving without burying people under repetitive tasks. Leaders need visibility into what is happening. Customers and employees need answers that feel fast and reliable.
Unthread fits this shift because it treats communication tools as part of the operating system of the company. Slack is not only a place to chat. It is where problems appear, where customers ask for help, where employees need support, and where teams coordinate responses.
AI becomes more valuable when it is connected to that environment. It can read context, suggest answers, trigger workflows, route requests, and help teams see what is happening across many conversations. That is the real promise of AI in support. Not replacing every person, but helping support teams work with more clarity and less chaos.
What Makes Tom Bachant’s Approach Different
A lot of founders build AI products around the technology first. They start with what the model can do, then search for a use case. Tom Bachant’s approach with Unthread feels more grounded because the pain point comes first.
The pain is obvious to anyone who has worked in a busy Slack environment. Too many requests. Too little ownership. Too much context switching. Too many repeated questions. Too many important issues hiding inside informal conversations.
Unthread responds to that pain with a product that feels practical. It does not ask teams to completely change how they work. It does not treat AI as magic. It uses AI as part of a larger support system that includes tickets, workflows, routing, escalation, and reporting.
That matters because business software succeeds when it fits into the rhythm of a team. If a product demands too much behavior change, adoption becomes difficult. If it solves a painful problem inside an existing workflow, it has a better chance of becoming part of daily operations.
Lessons Other Founders Can Learn From Tom Bachant and Unthread
Tom Bachant’s Unthread story offers useful lessons for other founders, especially those building in AI, SaaS, customer support, or workplace productivity.
The first lesson is to look for pain inside tools people already use. Slack is already central to many teams, which means the problems inside Slack are also central. Founders do not always need to invent a brand-new behavior. Sometimes the better opportunity is to improve a behavior that is already happening every day.
The second lesson is to make AI practical. AI is strongest when it is attached to a real workflow. In Unthread’s case, that workflow is support intake, ticket creation, routing, response generation, escalation, and resolution tracking. The AI has a job to do, and that job is tied to business value.
The third lesson is to build for scale before the pain becomes unmanageable. Slack-based support may work fine when a company has a few customers or a small internal team. But as the number of channels, employees, and requests grows, the old way starts to break. Unthread is built for that moment when informal support needs real structure.
The fourth lesson is to serve both frontline teams and managers. A support rep wants less repetitive work. A customer success manager wants cleaner follow-ups. An IT team wants better routing. A leader wants visibility and reporting. Strong workflow software often wins because it helps multiple layers of the organization at once.
Why Tom Bachant’s Unthread Story Matters Now
Tom Bachant’s work with Unthread matters because it reflects a bigger change in how companies think about support. Support is no longer limited to a ticket portal or email inbox. It happens in the flow of work. It happens in Slack channels, customer communities, internal messages, and real-time conversations.
That shift creates both opportunity and pressure. The companies that manage conversational support well can feel faster, more personal, and more responsive. The companies that do not manage it well can lose track of issues, frustrate customers, and overload their teams.
Unthread is built for that new reality. It turns Slack from a place where support requests can disappear into a place where support can be captured, automated, routed, and improved. For Tom Bachant, that is the central achievement. He is not just building another helpdesk. He is building a smarter layer for the way modern teams already communicate.
