THE LATEST
DEC 2025 / VERINT JOINS THOMA BRAVO + CALABRIOTHE ARCHIVE / KANA’S CUSTOMER-SERVICE STORY

COMPANY / ENTERPRISE SOFTWARE

KANA taught the inbox to remember

Before customer service became a race to add channels, KANA tackled a quieter problem: keeping the answer, the customer and the conversation together.

Advertisement

The trouble with putting your company on the internet was that people could finally reach you. In the mid-1990s, Mark Gainey was exploring a sports business when conversations with sporting-goods companies kept returning to the same complaint: customer email was piling up. Some businesses were so frustrated that they were turning it off. The website worked. The relationship behind it did not.

THE STORY IN THREE LINES
  • KANA began with email and grew into software for connected customer service.
  • Its advantage was carrying knowledge and customer context between channels.
  • The results depended on integrations, clean information and changes to everyday work.

Gainey and Michael Horvath changed course. KANA, incorporated in 1996, would help companies handle the conversations their websites created. There is a pleasingly uncorporate detail here: Gainey told Entrepreneur that KANA was his dog’s name. The founders later built Strava together. First, though, they had an inbox to sort out.

A small problem with a long tail

Looking back in a Stanford talk, Gainey described investors who thought customer email was too narrow to support a company. His account makes the opportunity sound almost embarrassingly plain. Businesses were inviting messages without having systems to answer them. KANA made that neglected task its starting point, then used relationships with those customers to expand.

The eventual company sold email management, knowledge management, live chat, web self-service and case management. These are different tools, but the underlying problem is familiar. A customer asks a question online, needs a person, changes channels and discovers that the organization has forgotten everything. KANA wanted the next interaction to inherit the last one.

KANA co-founder Mark Gainey speaking in Stanford eCorner talk artwork
Before the activity feed, the inbox. Co-founder Mark Gainey revisited KANA’s narrow starting point in his 2020 Stanford talk. Image: Stanford eCorner.

The answer was already in the building

Consider Carphone Warehouse. In a 2009 CRM magazine account, the retailer’s home-grown knowledge system had become unstable and cluttered. It resembled a dumping ground for resources. Finding an answer was itself a task. The company had started using KANA for email, then added KANA IQ for knowledge management.

Anne Wood, its head of knowledge management, decided to rewrite the content rather than simply carry the old material across. The aim was a consistent voice and information people could use. Within weeks of cleaning up the knowledge base, agent productivity reportedly rose 39 percent. First-time fixes reached 89 percent, with the cleaner knowledge credited as one contributor.

“You have to put a lot of effort into making them work.”Anne Wood, Carphone Warehouse, 2009

That sentence deserves space beside the numbers. The reported improvement followed a software rollout, a content rewrite and a methodological overhaul. Treating it as a software-only result erases the useful part. A support team can copy the practice: retire confusing material, rewrite the answers and give someone responsibility for keeping them usable.

One conversation, several doors

KANA Enterprise, launched in 2013, brought agent and self-service capabilities into a broader suite. An agent desktop put the customer’s case and relevant knowledge into the working environment. Email, chat, social listening, cobrowsing and web self-service offered different entrances. Case management supplied a way to keep work moving when an inquiry needed more than one reply.

The distinction mattered in its market. Info-Tech’s 2013 evaluation singled out KANA’s ability to present knowledge in context, including customer records and outside information. Salesforce, Oracle RightNow and eGain occupied the same broader field. KANA’s argument centered on connecting service work across systems and channels, particularly for organizations with complicated processes.

Australia Direct Insurance supplied a concrete example. Its e-business team was spending time on routine requests, including address changes. A KANA deployment let customers amend details online and later added email and chat. The published case study reported eight months to launch the agent and self-service experience, including five integrations. Forty percent of costly address-change transactions moved to self-service.

The case study estimated AU$1 million in group savings from contact deflection over twelve months. Those were customer and vendor-reported results, rather than a controlled experiment. Still, the mechanism is understandable: let people complete routine changes themselves and preserve an agent’s time for work that needs judgment.

Buying the missing pieces

KANA’s reach grew partly through acquisitions. Lagan brought government service software in 2010. Overtone added customer listening in 2011. Trinicom brought a cloud offering and midsize customers in 2012; KANA Express followed. Sword Ciboodle added case-management and agent-desktop capabilities that same year. Forrester’s contemporary assessment identified the logic: KANA had strength in self-service, but less inside the contact center itself.

There were limits to the enterprise proposition. Info-Tech placed three-year ownership costs for its defined KANA Enterprise scenario between $500,000 and $1 million, using vendor-provided pricing. That historical budget range explains why the packaged Express option mattered. A small support desk with straightforward requests could struggle to justify the enterprise suite’s cost and implementation work.

2013 ENTERPRISE BUDGET SCENARIO$500k-$1m

Three-year total ownership cost in Info-Tech’s evaluation. Historical scenario, not a current price.

A useful product can still have a difficult business

KANA’s history also contains a warning against reading product usefulness as financial security. By 2009, losses, financing difficulties and a falling share price had pushed its board to consider alternatives. An Accel-KKR affiliate bought substantially all operating assets that December. The original public corporation changed its name to SWK Holdings; the software business continued under KANA.

Verint acquired that business in February 2014. The closing announcement put the cash figure at $514.2 million; its later annual report recorded adjusted net cash consideration of $516.6 million. KANA brought approximately 900 customers to a company with complementary workforce and customer-engagement tools. In 2025, Thoma Bravo acquired Verint and combined it with Calabrio.

The enduring lesson is visible without buying anything. Examine the moment when a customer changes channels. Does the history travel? Can the next person find a dependable answer? KANA’s story shows how much work sits inside those ordinary questions. The inbox was merely where the questions arrived.

Follow the conversation