Hi everyone,
Would it be possible to link a customer relationship via the knowledgebase?
This means that if I have a customer who needs a technical how-to, hints or instructions, they can access this via their own customer knowledge base URL.
I create the path Customer > Customer A > then the article “HowToConnectVPN” in the knowledge base and want to make this only visible to customer A so that they have their own knowledge base database
-
What is your original issue/pain point you want to solve?
Improve response times for the service provider, and the customer might have to wait longer for low-priority tickets, even though this can be done independently through the knowledge base. -
Which are one or two concrete situations where this problem hurts the most?
If new employees start at a customer and are overwhelmed by the amount of information at the beginning, you can collect this again in the KnowledgeBase -
Why is it not solvable with the Zammad standard?
It’s certainly solvable, but unfortunately it doesn’t exist at the moment -
What is your expectation/what do you want to achieve?
Improving customer relationships. Save the customer’s wallet by asking recurring questions
Thanks
Richard