Nooshin Alibhai put a house on the help desk

Before Nooshin Alibhai asked other people to put money into Supportbench, she put a house into it. She and her husband, co-founder Eric Klimuk, sold their home to help finance the business. They had two young children. A customer support company is an unlikely destination for the proceeds of a family property sale. Then again, most people would prefer their software ambitions to come with a spare bedroom.

That decision gives Alibhai's story its scale. The business concerns the apparently small things: a request answered, a problem assigned, a customer remembered. The commitment behind it was considerable. As Supportbench's co-founder and CEO, based in the Vancouver area, she has built her work around a proposition that deserves more attention than its rather sensible vocabulary usually attracts: the people handling customer problems ought to have the information and authority to do something useful with them.

Her professional background includes sales, operations, event planning and entrepreneurship. These are occupations in which a plan eventually has to survive contact with another person. A timetable, a promise and a customer all have their own ideas about what should happen next. Supportbench brings those concerns into software for businesses serving other businesses.

A partnership with a dance floor in its past

Alibhai and Klimuk met through Latin dancing. She enjoys dancing; he has described salsa as an important influence in his life. Long before there was a software company to run together, there was that shared interest. It is an agreeably human beginning for a business whose working vocabulary includes escalations and service-level agreements.

The distinction between their backgrounds matters. Klimuk brought experience of enterprise support, including work at Sophos and HP. He had built an internal system at Sophos to address problems he encountered running support. Alibhai brought the commercial and operational perspective. Their partnership joined a problem experienced from inside a support organization with the work of making a company around a solution.

There is a temptation to turn the dancing into a management theory. Better to leave it as a detail of their actual lives. The two founders also enjoy spending time with family and friends away from startup work. Neither a marriage nor a hobby needs to become a lesson in productivity to deserve a place in a business story.

Alibhai became Supportbench's first investor. Her stated motivation included equity: giving growing companies access to the sort of capable tools available to larger enterprises. In that formulation, fairness has a practical expression. It can mean what a smaller team is allowed to do with the software it can afford.

The account behind the email

Supportbench's market is B2B customer support. Its organizing concern is the relationship behind an incoming request. An employee asking for help belongs to an account, and that account brings a history, a contract and expectations that may involve several teams. Treating the message as a self-contained object strips away precisely the context that could help someone answer it well.

The company's current account of its purpose describes long-running issues, coordination across departments and commitments that vary by customer. It emphasizes making that context visible and letting support leaders control how work moves. For Alibhai, the business case follows from taking the support department's daily work seriously. Someone needs to know who owns a case, what has already been tried and what the customer was promised.

This helps explain why her work repeatedly returns to information that is easy to scatter. A customer record in one place, a technical conversation in another, a resolution remembered by one colleague: each may be useful on its own. Joining them changes the next conversation. The attraction of that idea is wonderfully ordinary. Nobody enjoys explaining the same problem twice, especially to a company that has already sent an invoice.

When a customer buys you time

An enterprise client arrived among Supportbench's first 25 customers. Alibhai and Klimuk have described the operating budget that relationship provided and the freedom it gave them when choosing investors and advisers. After the sale of their house, this was another kind of financing event: a customer paying for the work.

By May 2022, StandUp Ventures had publicly announced its investment alongside N49P, Liquid2 Ventures and operator angels. StandUp's description of Alibhai emphasized resourcefulness, ambition and integrity. Those are the investor's judgments, and they belong alongside the concrete decision to back her company.

StandUp's investment argument centered on the demands of B2B relationships and the importance of retaining customers in recurring-revenue businesses. The fit is clear. A subscription creates another occasion for a customer to decide whether to stay. Support has a part in that decision, even when its contribution is less visible than the original sale.

A closed case can still have work to do

Alibhai's published writing provides a view of the problems she wants the business to address. In October 2023, she argued for bringing fragmented support tools together. The concern was practical: switching systems, searching for information and training people to navigate the resulting collection. Buying a tool is easier than making several tools cooperate.

By March 2026, an article under her byline examined converting solved tickets into knowledge base articles. The premise is simple. A team has already spent time understanding a problem and working out an answer. Keeping the result buried in a case history makes the next person start further back than necessary.

The workflow described there uses AI to draft an article from the case, with people reviewing and refining it before publication. That human step matters. A resolved request contains the evidence of what happened; a useful explanation still needs someone to check that it will make sense to the next reader. A well-kept answer can have a longer working life than the ticket that produced it.

Another March 2026 article looks at storing non-standard customer details in data tables. Renewal dates, stakeholder lists and contract terms are hardly glamorous subjects. They are also the details a team needs when the customer relationship refuses to fit a tidy form. Alibhai's public work keeps returning to such particulars. The ambition is visible in what the software is asked to remember.

“For organizations where support quality and accuracy are paramount, simply automating agents away isn’t the goal.”

Nooshin Alibhai

That statement appears in a February 2026 business-case guide published by Supportbench. The guide positions AI as assistance for agents and asks buyers to connect operational improvements to business outcomes. The emphasis suits a founder whose work crosses sales and operations: explain the problem, show what would improve and give the person approving the purchase a reason to believe the change is worthwhile.

Who gets the next difficult email?

Her February 2026 writing on shared inboxes takes up an even more familiar problem: a request can be visible to everybody while belonging to nobody. The article calls for assignment rules, fallback arrangements, monitoring and feedback from agents. Automation still needs a responsible owner. An inbox full of witnesses is a poor substitute for someone taking the case.

A March 2026 article on dynamic service-level agreements takes the same concern into response deadlines. It describes adjusting priorities using account context, issue complexity and changes in a conversation. The underlying management question is familiar: which request needs attention now? A queue can tell a team what arrived first. Deciding what matters most requires more information. In Alibhai's public account of the work, the system should help make that information available, rather than leaving each agent to reconstruct the circumstances. The point is to give a team a repeatable way to respond when several customers need different things at once.

In a separate piece on outage communications, her advice includes prompt acknowledgment, consistent updates and clear expectations. These are modest instructions with consequences. A technical team may be working intensely while the customer experiences silence. Communicating the work is part of serving the customer, rather than a decorative activity to attempt once the difficult work is over.

Her Helpdesk Efficiency Analyzer, published in April 2026, turns attention to tickets per agent, resolution time and escalation rate. The accompanying explanation encourages managers to use those measures to investigate workload and process. It offers a useful view of the CEO's public priorities: make the work visible enough that someone can decide what to change.

The word she chose

Asked for a word in a 2022 conversation about customer experience, Alibhai chose “Insight.” It is a revealing choice for someone selling software into a department often measured by the number of things it has finished. There is value in what a support team learns while doing the finishing.

The house sale is the dramatic event in her story. The longer project is quieter: helping the people answering customers retain what they learn, find what they need and act with a fuller understanding of the relationship. It asks executives to listen to a part of the company that spends its working day hearing where the promises become difficult.

Alibhai's work gives that department a claim on the business conversation. A customer problem can tell a company something worth knowing. Her bet is that the answer deserves somewhere better to live than an overlooked email.