An article rarely answers every question. With customer comments switched on, a customer reading it in the portal's Help center can ask about it right there, under the article, and your team answers in the same place. The next customer with the same question finds the answer already on the page.
Customer comments are off for every article until a publisher turns them on, one article at a time.
Open the article in the editor and find Customer comments in the Audience panel. Switch on Allow customer comments.
Switching it off hides the thread from the portal at once. Nothing is deleted: switch it back on and every comment is still there.
Under the article, a signed-in customer sees a Comments section with the public conversation, oldest first, replies beneath the comment they answer. A customer can:
Each comment shows who wrote it:
| Written by | Shown as |
|---|---|
| A customer | Their name and their company |
| Your team | Support — staff are never named to customers |
| A customer whose personal data has been erased | Deleted user |
A comment deleted while it still has replies leaves the placeholder This comment was deleted., so the replies keep their context. An edited comment is marked edited.
Customers see only public comments. Your team's internal notes never reach the portal, even when they are replies in a public thread. A customer who is not signed in is sent to the portal sign-in page. Each customer can post up to 60 comments an hour.
Comments on articles are never emailed to customers. A customer sees an answer the next time they open the article.
Customer comments appear in the editor's Comments panel alongside your team's review comments. A customer's comment carries a Customer badge beside their name and company (hover the name for their email), so you can tell at a glance who is asking.
Your team is told when a customer comments: the article's author and the staff already taking part in the thread get an in-app notification, whatever their other notification settings.
When you write, choose who sees it:
Writing a public comment needs Send Public Replies as well as Comment on knowledge-base articles. Without it you can still answer with internal notes. A reply in an internal thread always stays internal.
Customer comments are covered by the same privacy tools as tickets:
Knowledge Base Permissions
The six Knowledge Base permissions, the Manage knowledge base role template, and exactly which controls each one unlocks.
My Work
My Work is your personal, cross-project list of the items assigned to you or that you watch — switch what it shows, act on items in place, shape and save the view, and export it.