Hi Phaneedra,
If I add the additional backslashes it renders as \\server\folder, which is how I am handling currently and I would just set it and forget it, but the issue is that we display both the messaging and knowledge channel in our Messenger Configuration so our customers can access the library if they don't want to chat with the digital bot.
So, for now, I am stuck leaving the knowledge article as " \\server\folder " to render correctly in the Knowledge library and building out a full intent for that particular query that displays the same information in a communicate object with a " \\\\server\\folder " so it renders correctly if queried in the bot interaction.
Thanks,
Nicole
------------------------------
Nicole VanWie
UC Engineer
------------------------------
Original Message:
Sent: 07-09-2026 02:04
From: Phaneendra Avatapalli
Subject: Architect rendering of backslashes from a knowledge article
Hi Nicole,
Interesting issue. I haven't come across this before, but it looks like the Digital Bot may be treating the leading double backslash as an escape sequence when rendering the response.
Just out of curiosity, have you tried escaping the path with additional backslashes (for example, \\\\server\\folder) to see if it preserves the UNC path when rendered by the bot?
I'd be interested to know whether that changes the output, or if the bot still normalizes it to a single leading backslash.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------