Back to Blog Home

How Kipwise helps ZenMarket share knowledge with remote customer support reps

How Kipwise helps ZenMarket share knowledge with remote customer support reps

The biggest problem with ZenMarket’s old documentation tool was that search did not work in Japanese, and Kipwise’s does. If your team writes in more than one language, we recommend testing search in each of them before you compare any other feature. A wiki that cannot find what people wrote in one of your languages makes writing in that language pointless, as ZenMarket found with Bitrix24.

ZenMarket is an international e-commerce company focusing on proxy purchasing services. It helps clients shop on Japanese e-commerce sites, consolidates their purchases at the warehouse and ships them to the destination they choose.

A fast-growing remote support team needed a way to share changes and onboard new teammates

ZenMarket had around 80 full-time staff onsite and 270 part-time workers and independent contractors. Its main operation was in Osaka, Japan, with IT and customer support staff working remotely from other countries.

The company keeps changing the way it works, and teammates found it hard to keep up with the why, how and when of each change. Changes used to be shared in Slack, but new teammates were joining every day, and it was unrealistic to expect them to read the manuals and the Slack messages that were posted before they arrived.

Many support staff were overseas, so ZenMarket also needed a way to train support reps remotely. Before Kipwise it used either a Microsoft Office document, which it never managed to keep up to date, or a Google Doc, which was easy to update but raised security questions when shared with people outside its Google Workspace.

The previous documentation tool did not offer good multilingual search

ZenMarket had used Bitrix24 for a couple of years. It covers many things, and documentation is only one of them: it also handles task tracking, presence tracking, CRM and more. ZenMarket used few of these functions, because a more specialized tool already handled its tasks, so Bitrix24 had become a waste.

The team also found the information structure counterintuitive. The biggest issue was that searching in Japanese did not work, which made documenting anything pointless for a team working in at least two languages, English and Japanese.

Why ZenMarket chose Kipwise as their solution

Olga Pokrovska, Operations Manager at ZenMarket, researched a number of solutions and chose Kipwise for the reasons below.

Multilingual search

ZenMarket has content in both English and Japanese. Olga considered many options during the buying process, and most of them did not support multilingual search. Bitrix24 offers a Japanese interface, but its search did not actually work for Japanese. Olga is impressed by how well Kipwise searches Japanese content.

A Japanese interface does not mean Japanese search works, so test search with a page you wrote yourself. Search for one word from the middle of a sentence, in each language you use. Japanese and Chinese are written without spaces between words, so a search that only matches whole space-separated words can pass an English test and still find nothing in Japanese.

Slack integration for remote teams

ZenMarket relies heavily on Slack, especially to communicate with remote workers overseas, so reaching team knowledge directly in Slack helps. The team also likes that the Kipwise login through Slack works for single-channel guests, so those people can open Kipwise without another account to remember.

Permission control with user groups

Teams in different locations need different information. With Kipwise, ZenMarket sets permissions by user group to control which content is shared company-wide and which only with a certain team. Keeping information in Kipwise also adds security, because it is not accessible from everywhere on the internet.

Very fast and responsive customer support

Olga said Kipwise’s customer support is very fast and responsive, and that the ZenMarket team, who work in customer support themselves, feel they always have someone to count on when they need help with the product.

Fewer repeated questions for managers

ZenMarket’s teammates agree that a central source of information is convenient, because they no longer need to ask a superior every time. As the team grows, managers cannot answer questions one by one. So when an issue arises, Olga always tries to turn it into a Kipwise article, and the next time it comes up, teammates can refer back to it.

We recommend making that a rule: a question is not closed until its answer is linked to a page. Turning an issue into an article works best at the moment someone already has the answer in hand, and a documentation clean-up planned for later is easy to postpone.

Automatic reminders keep content up to date

Olga also likes Kipwise’s built-in content review flow, where the system automatically reminds content creators to check and update their content at regular intervals. It is easy to create new content and just as easy to sweep outdated content under the rug, so the regular reminders help the team.

Building a search-first culture in the team

Olga’s view is that a knowledge base is useless if you do not fill it with content and encourage people to use it. The company needs a culture of “look for it first” and “here is the information we have”. In customer support, the team works Kipwise into onboarding and staff education as much as possible, and the Admin department keeps necessary information up to date and points people to it whenever needed.

Kipwise also has built-in features that help teams build a search-first culture. For more tips, see our post Turn Kipwise into the Google for your team - How to build a search-first culture in the team.

Related posts

Your team’s knowledge, answered in Slack

Add the Kipwise Agent. It answers from your pages with the source, and asks before it changes anything. 7-day trial, no card needed.