Skip to content
Help Center
Submit a request Sign in

Flag an article for update and resolve suggestions

Article suggestions turn an agent’s discovery into a visible maintenance request. Use them for an incorrect step, an outdated control, a missing scenario, or an unclear explanation. This feedback process is separate from submitting a new article version for publication review.

At a glance

For: agents, knowledge contributors, and suggestion reviewers. Applies to: Supportbench Core.

Start here: Open an article → Flag for update or Suggestions

Submit a useful suggestion  ·  Review and close the request  ·  Understand the permissions and messages  ·  Submit feedback that an author can act on  ·  Common problems

Submit a useful suggestion

  1. Open the article and choose Flag for update. If it already has an open suggestion, use View / add feedback to add evidence to that request.
  2. Select the configured Reason for update. Identify the exact step or claim, what happened, and the corrected behavior or safe reproduction if known.
  3. Keep the initial explanation within the form’s limit. Do not paste credentials, private customer logs, or unrelated case history.
  4. Choose Flag for update to save. Review the resulting request in Suggestions.
  5. If a closed request does not cover a distinct remaining problem, use Start a new suggestion.

Make the request actionable

“Step 3 says choose the old menu name. In Core, the command is in the activity toolbar; the remaining steps work.” is more useful than “This article is bad.” Include enough context for a reviewer to reproduce the mismatch without needing the customer’s private data.

Review and close the request

  1. Open the article’s Suggestions tab and choose Review suggestion on the current request.
  2. Choose the appropriate state: New, In Progress, Done / Completed, or Rejected. Mark work in progress when someone is actually responsible for the correction.
  3. Use a private Reviewer note for internal review context. Use Message to requester for the explanation the requester should receive; a rejection requires that message.
  4. Choose Update. A closing message is delivered in Supportbench and can be emailed when the requester’s email alerts are enabled.
  5. When a correction was needed, verify the resulting article version. Closing a suggestion does not itself prove that the article body was corrected and published.

Understand the permissions and messages

CapabilityPurpose
Flag articles for reviewSubmit a content-maintenance suggestion.
Administer flagged articlesReview and manage suggestions.
Article editing/publishingChange and publish the article itself; these are separate capabilities.

Only one open suggestion is maintained for an article, so add relevant evidence to the existing discussion. A private reviewer note is not included in the closure notification; do not put private reasoning into the requester message expecting it to remain internal.

Submit feedback that an author can act on

A useful suggestion says exactly where the reader became stuck and what a successful article would explain. It is more helpful than “this article is bad,” and it does not require the requester to know the final fix.

Example: missing terminal instructions

“In the Supportbench MCP Codex setup article, the step says to run a CLI command. I am helping a first-time Windows user. The article does not explain that the command goes into PowerShell, how to open it, or that Codex CLI must be installed. Please add those prerequisites, the expected result after Enter, and recovery for ‘codex is not recognized.’ The server URL/token distinction should remain explicit.”

For a wrong product step, include the article ID/title, heading or step number, the relevant Core screen/version, expected versus actual result, and redacted evidence. Do not attach a screenshot containing a token or customer record merely to prove that a label differs.

  1. Open the article and use Flag for update when available. Review any existing open suggestion first so the same issue is not fragmented.
  2. Describe the specific gap and desired reader outcome, then submit.
  3. The reviewer reads the full context, checks the current product and either makes the correction or explains why it is not appropriate.
  4. When closing the request, provide a clear requester-facing result, such as “Added Windows terminal prerequisites and a command-not-found recovery step; please retry the procedure.”
  5. If rejecting it, explain the relevant reason and the appropriate route. Avoid private internal commentary in a message the requester receives.

A closed suggestion is not proof that retrieval improved. If the original problem was “Co-Pilot cannot find this answer,” repeat the original query and follow-up after the article update.

Common problems

ProblemChecks and correction
Flag for update is missingCheck the relevant role permission and article access.
There is already an open requestUse View / add feedback and add the missing evidence.
A reviewer cannot reject the requestProvide the required Message to requester.
The requester still sees incorrect contentCheck whether the corrected version actually completed authoring review and publication.
The same issue returns repeatedlyImprove the procedure’s verification step and maintenance ownership, rather than only closing repeated suggestions.

Include the exact passage and originating ticket — upcoming, not deployed

Release status: This enhancement has been implemented and validated locally but is not deployed yet. The following steps describe the upcoming release and may not be available in your workspace.

A selected passage is a read-only copy of the article text you want a reviewer to examine. It stays beside your explanation in the suggestion, even if the article later changes. Use it when a particular step, label or claim needs correction. Whole-article feedback remains available without selecting text.

Before you begin

You need access to the article, Knowledge Base availability and the Flag articles for review role permission. A new suggestion also needs a configured reason. Ticket-origin feedback requires access to that ticket. Permission to administer or read suggestions does not grant permission to submit them. Passage and ticket controls appear only when this enhancement is available for your account; there is no new activation setting.

Send a precise update request

  1. Open the article in its reader or in a ticket’s Knowledge drawer. Select the relevant text in the article body, up to 4,000 characters. Select text before opening the feedback form.
  2. Choose the existing Flag for update action, or View / add feedback when a suggestion is already open.
  3. Check Selected passage. Long quotes are collapsed to four lines; choose Show more to inspect the rest, then Show less to collapse it. Use Remove selected passage if it is not relevant. The snapshot label and language identify the captured context; the quoted copy does not edit the article.
  4. When starting from a ticket, check the compact ticket badge. The reference is included by default. Choose Remove source ticket if the reference is unnecessary. Ticket messages are not copied into your feedback.
  5. For a new suggestion, choose Reason for update. In Add information, explain what is wrong, the observed result and the expected correction. Existing suggestions accept additional information without changing their original reason or explanation.
  6. Choose Flag for update for a new request or Add information for a follow-up. Wait for Saved. and verify the quote and explanation in the resulting card.

Worked example

While helping a customer in ticket c-100, you find an article that says “Choose Account settings, then Payment gateway.” The control is now under Integrations. Select that sentence, open Flag for update, keep the ticket reference and choose the appropriate configured reason. Write: “The Payment gateway control is under Integrations for our current administrator role. Please update this step and verify the menu label.” The reviewer receives the exact old wording, your explanation and an authorized link to the originating ticket.

Review the context without losing the discussion

Read each quote beside the explanation in its Original suggestion or Additional information card. Each contribution keeps its own context; later feedback does not overwrite earlier evidence. Open the ticket link only when needed. If you cannot access that ticket, the card says Source ticket unavailable and does not reveal its identifier or title. Draft passages remain subject to draft access; restricted evidence displays Selected passage unavailable. An authorized snapshot remains historical evidence, not a guarantee that the current article still contains the quoted wording.

Recover from a problem

  • The passage changed or is unavailable: your explanation stays in the form. Remove the selected passage and submit whole-article feedback, or select the current text and try again. Do not assume the earlier wording is still current.
  • A save result is uncertain: choose Retry previous save to resolve that same submission. The retry retains its original target and receipt, so a successful first request is not turned into an additional contribution. Confirm the previous save before submitting further changes.
  • Another suggestion is already open: read it first. Your text and context are retained; explicitly choose the offered action to add them to that request. The system never appends them automatically.
  • Context becomes unavailable: keep the form open and retry after service is restored, or explicitly remove its passage and ticket reference to send ordinary feedback. Submitted context is not silently dropped.
  • Permission changed while the form was open: submission is checked again on the server. Ask your administrator to confirm the role and article/ticket access; reopening the form does not bypass those checks.
  • Working on a small screen: scroll the discussion or form body to inspect long content. The primary action remains reachable, and the reason selector stays in the owning dialog.

Keep private customer details out of the explanation and quote. Context is not added to existing notification emails. Closing a suggestion still does not publish an article correction; complete the normal editing and publication workflow and verify the resulting article separately.

Flag a passage for an internal update review

Release status. Coming soon — not deployed yet. These passage actions and markers will become available after the matching release and verification for your account.

Use passage feedback when an instruction needs correcting and a reviewer needs to know exactly which wording you mean. This feature is available in the internal article reader and Ticket Knowledge drawer only. You must have article and Division access, Knowledge Base availability and the Flag articles for review permission. Configured reasons are required when starting a new suggestion.

Customer-facing portals never show passage flags, request counts or feedback. An agent with the required permission can flag an article in the internal application even when that article is also published publicly. Feedback details, restricted draft history and originating ticket links retain their separate access checks.

  1. Open the article inside the agent application, either directly or from the Ticket Knowledge drawer.
  2. Select the exact wording, or use the flag beside a paragraph, list item or section heading. The action becomes visible on hover or keyboard focus and is available on touch screens. A heading action captures its section up to the next heading of equal or higher level.
  3. Check the Selected passage quote and section name. Expand a long quote with Show more. Remove an unwanted passage before selecting another. Sections longer than 4,000 characters require a shorter selection. Your explanation remains in the form.
  4. Keep or remove the originating ticket badge. Choose a reason for a new suggestion, explain the correction and select Flag for update. If a suggestion already exists, read it and explicitly add your information to that thread.
  5. After a confirmed save, look for the passage flag marked Update requested. Open Update requests to navigate passage feedback, whole-article requests and contributions whose wording cannot be located.

Example and expected result

An article tells agents to choose Account settings to configure a payment gateway. Select that sentence and explain that the current menu is Integrations. The reviewer sees the saved quote beside your explanation, with an authorized ticket link when included. The original quote remains in the discussion after the article changes. The marker stays attached only while the wording and section can be located unambiguously.

Review and recovery

All contributions belong to the existing article-level suggestion. New and In progress suggestions keep their markers. Completing or rejecting that suggestion clears its active markers while preserving history. Flags inside overlapping passages share a marker. Ordinary whole-article feedback has no passage location.

Passage could not be located means the wording was changed, removed, repeated ambiguously or is unavailable in the displayed locale. Open the authorized feedback history to inspect its original snapshot. Do not assume the marker has moved to equivalent wording.

If a save is unconfirmed, use Retry previous save to resolve the same submission. If content changed before submission, keep your explanation, remove the stale quote and select current wording. If controls disappear, ask an administrator to verify the flagging permission, article access and account capability. Existing review-history access is separate from permission to submit new flags.

Was this article helpful?