Skip to content

For the complete documentation index, see llms.txt.

Route and assign suggestions to the right people

A suggestion only helps if it reaches someone who can review it. By default, Promptless routes each suggestion, and the docs PR it opens, to the people closest to the change. It notifies whoever requested the work, assigns the docs PR, and credits the requester in the PR. Change those defaults in your Agent Knowledge Base to match how your team divides ownership and review. Then use the review queue in the dashboard to claim, hand off, and find suggestions.

These defaults apply until you customize them.

Notify the person who requested the change

Section titled “Notify the person who requested the change”

When Promptless announces a suggestion, it notifies the person the work came from. That might be the author of the merged pull request, the teammate who tagged Promptless in Slack, or whoever started the thread. The requester sees that the suggestion is waiting on them.

Promptless also replies where the conversation already happens. When a suggestion comes from a Slack thread, Promptless can post the update as a reply in that thread. Everyone discussing the change sees it there. A source PR in GitHub can get a comment that links the new docs PR.

When Promptless opens a docs PR, it sets an assignee so the PR lands in that person’s review queue. By default, the assignee is the person the change came from: the source PR’s author, or the teammate who requested the update in Slack. The person who changed the code or asked for the update then reviews the docs that follow. You can point PRs at an area owner or a specific teammate instead.

Usernames rarely line up across platforms. The same person might be @alice in Slack and alice-gh on GitHub. Promptless keeps a directory of the accounts each person uses, so it assigns and mentions the right account on each platform. To review or correct it, see Review accounts on the People page.

Credit the requester in the PR description

Section titled “Credit the requester in the PR description”

For a suggestion that starts from a Slack request, Promptless names the requester on a line near the top of the PR description, formatted as Requested by: <Full Name>. A reviewer who picks up the PR later knows whom to follow up with.

Promptless can hand an approved docs PR to a designated writer or reviewer. Suppose a docs PR receives an approval, and that person hasn’t approved it yet. Promptless assigns them and notifies them that the PR is ready for writer review. This handoff runs only when you name the writer or reviewer in your Knowledge Base.

Write routing and assignment preferences in plain language, and Promptless applies them. You can adjust:

  • Who gets notified. Mention the original requester, or route suggestions to an area owner based on which docs or product area the change touches.
  • Who owns the PR. Choose which teammate is assigned a docs PR.
  • How approvals hand off. Name the writer or reviewer a PR goes to once it’s approved, and how Promptless notifies them.

A preference can cross tools, such as “Assign the docs ticket in Jira to the engineer whose GitLab merge request triggered the suggestion.” Promptless knows each person’s accounts from the People directory, so you don’t need to map usernames.

Only organization admins can edit the Knowledge Base. Other members can view it.

  1. In the Promptless dashboard, open Settings and select Agent Knowledge Base.

  2. Open doc_workflow/notification_preferences.md.

  3. Add your preferences. For example:

    When a PR is approved but our lead writer, Alice, hasn't approved it, assign them and notify them for a final review.
    Route suggestions that touch the billing docs to the billing team's owner, Bob.
  4. Select Save.

For notification timing and message format, which live in the same file, see Customize notifications.

The suggestions list in the dashboard is your team’s review queue. Promptless gives each suggestion a priority and an estimated review time, and the list puts the most urgent work first.

Suggestions list with the search field, Collection, Trigger source, and Labels menus, the Has screenshots switch, status tabs, and Group and Sort controls above collapsed rows grouped into Critical, High, and Medium sections, each row showing a priority badge, docs PR chip, change size, review time, and date

As you triage, assign a suggestion to yourself or a teammate to claim it or hand it off, and adjust its priority and labels. To review a suggestion’s changes, see Review in the dashboard.

Filter the queue by status, doc collection, trigger source, label, or whether a suggestion includes screenshots. Group and sort the list to match how your team works. The page URL keeps the view, so you can share it as a link.

Search accepts free text and qualifiers such as assignee:unassigned, priority:high, labels:, docs:, and has:screenshots. To find a suggestion by pull request or merge request number, search for one of these:

  • pr:123 matches the suggestion whose docs PR is #123.
  • source-pr:123 matches suggestions triggered by source PR or MR #123.
  • #123 matches either.

Promptless archives a suggestion after 30 days of inactivity. Viewing or editing a suggestion resets the timer. To change the window or keep suggestions open indefinitely, an admin sets the archiving policy for the doc collection. See the Configuration reference for its enabled and stale_after_days fields.

You can also ask Promptless to change the policy for you, for example “@Promptless stop archiving suggestions in our docs collection.” See Ask Promptless to update your configuration.

If a suggestion is archived before you review it, contact help@gopromptless.ai to restore it.

To pull a teammate into a suggestion’s review, mention them in a line comment, an overall comment, or a reply. Type @ and pick the teammate by name or email. The mentioned person gets an email that links to that comment.

To mention someone who isn’t in your workspace yet, enter their full email address and choose the invite-and-mention option. After you confirm, Promptless invites them with collaborator access and sends the same email.

A comment can mention up to 20 people. If you mention the same person on the same suggestion again within 5 minutes, Promptless skips the second email.