Route and assign suggestions to the right people

A suggestion only helps if it reaches someone who can review it. Promptless routes each suggestion, or the pull request it opens, to the people closest to the change: it notifies whoever requested the work, assigns the documentation PR, and credits the original requester in the PR. You shape that routing through your Agent Knowledge Base, so it follows your team’s ownership and review conventions rather than a one-size-fits-all default.

Notify the person who requested the change

When Promptless announces a suggestion, it notifies the person the work came from, whether that’s the author of the merged pull request, the teammate who tagged Promptless in Slack, or whoever started the thread. The requester sees the suggestion in the channel and knows it’s waiting on them, so the notification never lands without an owner.

Because Promptless ties each notification back to its source, it can also reply where the conversation already lives. When a suggestion comes from a Slack thread, Promptless can post the update as a reply in that thread, so everyone already discussing the change sees it in context, while a source PR in GitHub might get a comment about a new related docs PR.

Assign the documentation PR

When Promptless opens a documentation PR, it sets an assignee so the PR lands in that person’s review queue. By default, it assigns the person the change came from—the source PR’s author, or the teammate who requested the update in Slack—matching their account across GitHub and Slack. Who owns each PR is governed by your Agent Knowledge Base, so you can point PRs at an area owner or a specific teammate instead.

Assigning the PR to the requester keeps ownership continuous: whoever changed the code or asked for the update is the same person GitHub prompts to review the docs that follow.

Usernames rarely line up across platforms—the same person might be @jdoe in Slack and jane-doe on GitHub. Promptless matches accounts on a best-effort basis, so it usually connects a requester’s identities on its own. When it can’t, or when you want to be sure, add a username map to your Agent Knowledge Base that pairs each teammate’s Slack and GitHub handles. Promptless then uses that map to assign and credit the right person even when their names differ.

Credit the requester in the PR description

For a suggestion that starts from a Slack request, Promptless names the requester on a dedicated line near the top of the PR description, formatted as Requested by: <Full Name>. This shows at a glance who asked for the change, so a reviewer picking up the PR later knows who to follow up with.

Route approvals to a reviewer

Routing doesn’t stop when the PR opens. You can have Promptless hand an approved PR to a designated writer or reviewer. When a documentation PR receives an approval and that writer or reviewer hasn’t approved it themselves, Promptless sets them as an assignee and notifies them that the PR is ready for writer review. You set this handoff up in your Agent Knowledge Base, so it follows the writer or reviewer you name rather than running by default. That writer or reviewer gets a clear signal that a PR has cleared an approval and now needs their eyes, and no one has to reassign it by hand.

Customize routing in your Knowledge Base

Your Agent Knowledge Base governs routing and assignment, so you can adapt it to how your team divides ownership. Organization admins can edit these preferences directly. Other members have read-only access.

You write these preferences in plain language—not a config schema—and Promptless applies them. Common adjustments include:

Who gets notified: @mention the original requester, or route suggestions to an area owner based on which docs or product surface the change touches.
Who owns the PR: choose which teammate is assigned a documentation PR.
How approvals hand off: name the writer or reviewer a PR should route to once it’s approved, and how they’re notified.
Who’s who across platforms: map a teammate’s Slack and GitHub handles so Promptless assigns and credits the right person when their usernames differ.

For example, you might add lines like:

When a PR is approved but our lead writer (Jane) 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 (Juan).

| Person | Slack | GitHub |
| --- | --- | --- |
| Jane | @jdoe | jane-doe |
| Bill | @Bill | billhandler |

Notification and routing preferences live in the doc_workflow/notification_preferences.md file within your Knowledge Base. It’s a lightweight scaffold for your overrides, while Promptless handles the underlying templates and delivery. For the full range of notification customizations and channel configuration, see Customize notifications. To teach Promptless durable conventions from your review feedback, see Teach conventions with feedback.