Customer support is a complete topic to talk about for any product in the market. If your product is growing, sooner rather than later you’ll need a support team in order to work with all those clients.
To manage a support team can be challenging in terms of knowledge and communication, so here are some good cases so that you can make the decision to start using a knowledge base.
Onboard new agents
Join new members to your team can be hard and it may take some time for them to start being productive. It’s completely normal and expected.
However, when we are talking about customer support teams, a good workaround can be to provide them with a complete knowledge base, so that new members can start attending simple or common requests just with the help of “live” documentation.
This will distribute the work between the team members and at the time the new members will get involved in the product knowledge.
Documentation being updated constantly
When a product is in the early stages, it’s common that the “how to” of some features changes constantly. Keep a support team updated can be challenging because it requires a lot of communication effort.
Even when we encourage teams to be in constant communication about breaking changes in the product, we also understand that that’s not possible 100% of the time, so a good knowledge base can help agents for those requests that will come in the near future.