On this page

What customer comments are for#

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.

Turning comments on for an article#

Open the article in the editor and find Customer comments in the Audience panel. Switch on Allow customer comments.

  • Changing it needs Publish knowledge-base articles. Without it the switch is disabled, and reviewers who only comment see it as Allowed or Off.
  • The thread appears only on articles customers can already read: published, set to Portal, not inside an internal-only category, and shared with the customer's company. You can switch it on while the article is still internal; it takes effect when the article goes to the portal.
  • Archived articles cannot change the setting.

Switching it off hides the thread from the portal at once, along with the highlights of comments pinned to the article's words. Nothing is deleted: switch it back on and every comment, and every highlight, is still there.

What customers see#

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:

  • Post a comment, or Reply to one.
  • Edit or Delete their own comments. Other people's comments cannot be changed.

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.

When your team answers publicly, the customers taking part in that thread are emailed the answer and can reply by email. See Email replies to customers.

Pinning a comment to words#

A customer can tie a comment to the exact words of the article it is about, instead of describing where they are:

  1. Select the words in the article. A Comment on this button appears just below them.
  2. Click it. The comment box shows Commenting on: followed by the words; Remove beside it goes back to a comment on the whole article.
  3. Write the comment and click Post comment.

The words are then highlighted in the article. Clicking highlighted words scrolls to their comment, and each pinned comment shows the words it quotes with Show in text, which scrolls back to them. Only a new comment can be pinned, not a reply. If the selection is too long, the button reads Select fewer words to comment on them. If the words changed since the customer opened the article, they see That text has changed. Select it again.

Customers see highlights only for public comments, yours and theirs. Your team's internal notes, pinned or not, never reach the portal, and nor do their highlights.

Deleting a pinned comment, by the customer or by your team, removes its highlight from the article as well, unless the comment still has replies.

When pinned words are later deleted or reworded in the editor, the comment stays in the portal thread and says Passage removed in place of the quote, so customers are never shown words that are no longer in the article. Your team still sees the old quote in the editor. See Pinning a comment to words in the article for how pins follow edits and how your team pins its own comments.

Answering in the article editor#

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. A comment a customer pinned to words is highlighted in the editor and numbered in the sidebar, like your own team's pinned comments.

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:

  • Internal note — staff only. This is always where the box starts, for a new comment and for every reply, so going public is always a deliberate choice.
  • Public comment — shown on the portal under the article, as Support, and emailed to the customers in the thread (see below). If customer comments are still off for the article, the box warns that customers will see it once they are turned on.

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.

Email replies to customers#

When someone on your team posts a public reply in a customer's thread, each customer taking part in that thread gets an email with the reply. It says your organization replied to their comment on the article, naming it, links to the conversation on the article in their portal, and says You can reply to this email to answer on the article. Internal notes are never emailed.

The email is sent only while all of these hold:

  • Service Desk and the portal's Help center are on, and headless mode is off.
  • The article is still published, set to Portal, shared with the customer's company, and has Allow customer comments on.
  • The thread itself is public, and the customer is active, not blocked or erased.

A large thread emails its first 25 customers, in the order they joined.

When a customer replies by email#

The customer's answer is posted on the article thread as their public reply, exactly as if they had written it in the portal. It never opens a ticket. A resolved thread is reopened. The quoted earlier email is left out. Attachments are not posted: the reply goes up without them, and the customer gets an automatic note saying they can add files in the Help center.

A colleague from the same company can reply too, if their email passed DMARC. They are added to the desk with that company once the reply is posted; a company whose portal is Invite only accepts only colleagues already on the desk.

If the reply cannot be posted, because the Help center is closed, comments were switched off or the thread is gone, or the sender is not taking part, the sender gets one automatic note saying why (at most one a day for each thread and reason). Nothing is posted.

Held, rejected and undelivered email#

  • A reply caught by your mail checks waits in Held for review, where its About column names the article. Recover posts it on the thread, never as a ticket; if the article can no longer take it, recovery is refused with the reason and the message stays held.
  • A reply that was turned away is listed on Rejected mail with a link to its article.
  • If your reply's email bounces, or the customer marks it as spam, you get an alert in the app and by email linking to the article, and your reply shows a warning icon: Failed to deliver to the customer.

Privacy: erasure and merging requesters#

Customer comments are covered by the same privacy tools as tickets:

  • Anonymizing a requester removes their name and the words of their comments, including from your team's notifications and the words quoted on comments they pinned. Their comments then show as Deleted user, and they can no longer edit or delete them.
  • Merging two requesters moves their article comments to the surviving requester along with their tickets.

See Requesters and companies.

Powered by DevStride