Agents don’t wait to be prompted.
The Dispatch Inbox: work waiting for you.
Dispatch finds the work, drafts the fix, and puts it in front of the right person. You keep the approve moment.
No credit card needed ✦ Free plan available
Inbox
4 items need you · 1 in progress
Last crawl: yourcompany.com today
Findings with a drafted fix ready3
Checks that fail on a governed page. Draft fix files a change request with the fix already written.
yourcompany.com · 3 findings
- HighScore dropped84 to 58
AEO score dropped from 84 to 58 on /pricing
/pricing · seen 2h ago
What Dispatch will ask the agent to do
Review /pricing: its AEO score dropped from 84 to 58 since the last crawl. Failing now: structured data (json-ld), canonical url. Compare the page's head metadata and structured data with the last deployed version and restore what was removed or broken. Do not change the visible content beyond what is needed to recover the score.
Draft fixDismissOpen page - MediumCheck failing
Missing meta description on /about
/about · seen 2h ago
No meta description found
What Dispatch will ask the agent to do
Add a meta description to /about (currently missing). Summarize the page in 140 to 160 characters, lead with the primary keyword, and make it a complete sentence. Do not change any other metadata.
Draft fixDismissOpen page - LowOrphaned page
/blog/launch-notes dropped out of the sitemap
/blog/launch-notes · seen 1d ago
What Dispatch will ask the agent to do
/blog/launch-notes no longer appears in the sitemap. Confirm whether it was removed on purpose. If it was not, restore the page and its sitemap entry; if it was, add a permanent redirect from /blog/launch-notes to the closest replacement page so existing links and citations keep resolving. Do not change other pages.
Draft fixDismissOpen page
How the Inbox fills itself
Every governed page, measured on a schedule. Every slip, drafted as a fix.
Nobody has to remember to check. Dispatch re-crawls every page you govern, keeps the score history, and opens a finding the moment something that used to pass now fails. Each finding carries a drafted change request, in plain language, that an agent can execute as written.
Scheduled crawls
Every page of every governed site, re-crawled daily or weekly per site. Each crawl scores the page and writes the score to its history.
Score history
A per-page record of every crawl, so a regression is a fact with a date on it rather than a feeling that something changed.
Failing checks
A check that fails opens a finding: title, meta description, H1, canonical, structured data, social tags, indexability, or HTTP status.
Score drops
A page that loses ten points or more since the last crawl opens a finding, with severity rising as the drop widens.
Crawl errors
A page that stops answering, or answers with anything other than a 200, opens a high-severity finding on its own.
Orphaned pages
A page that falls out of the sitemap opens a finding that asks whether it moved, and drafts the redirect if it did.
The Inbox as it renders in production. Open a finding to read the exact request Dispatch drafted for the agent.
Inbox
3 items need you · 1 in progress
Last crawl: yourcompany.com today
Findings with a drafted fix ready2
Checks that fail on a governed page. Draft fix files a change request with the fix already written.
yourcompany.com · 2 findings
- HighScore dropped84 to 58
AEO score dropped from 84 to 58 on /pricing
/pricing · seen 2h ago
What Dispatch will ask the agent to do
Review /pricing: its AEO score dropped from 84 to 58 since the last crawl. Failing now: structured data (json-ld), canonical url. Compare the page's head metadata and structured data with the last deployed version and restore what was removed or broken. Do not change the visible content beyond what is needed to recover the score.
Draft fixDismissOpen page - MediumCheck failing
Missing meta description on /about
/about · seen 2h ago
No meta description found
What Dispatch will ask the agent to do
Add a meta description to /about (currently missing). Summarize the page in 140 to 160 characters, lead with the primary keyword, and make it a complete sentence. Do not change any other metadata.
Draft fixDismissOpen page
Draft fix opens a request that is already written.
A finding is not a to-do. It is the request, prefilled: the page, the intent, and the risk tier Dispatch suggests. From there it runs the same governed loop as any request a person writes: agent handoff with your approved context, preview, role-gated approval, live, restorable.
Draft fix, from the Inbox
One click files a change request with the finding’s drafted intent, the page route, and the suggested risk tier. Dispatch generates the agent handoff prompt with the page’s source files and your approved context attached, and the finding is marked as drafted so nobody files it twice.
- Open to every member; dismissing a finding is an approver decision
- A finding closes on its own when the check passes on a later crawl
- Slipped pages and in-progress work sit in the same view, so the Inbox is the whole day
Note to request, from any page
Every governed page has a detail view with its check list, its score history, its findings, and a box for what should change. Write the note; Dispatch drafts the request with the page context attached and opens it.
What should change on this page?
Dispatch appends the page route, current title, and failing checks so the agent works from the page as it was last crawled.
Risk tier
Standard: normal reviewDecide how much runs without you.
Autonomy is a policy on the site, not a mode of the product. Turn it up for the work that is safe to ship on its own, and keep the gate on the work that is not.
- Low-risk auto-approve, on the record. When it is on, a low-risk request that reaches preview-ready is approved by the site’s policy. The approval names the policy as the actor, the activity feed logs it, and the notification says what shipped.
- A second approver for high risk. Pricing, legal, navigation, forms: high-risk requests need two distinct approvers, and the person who filed the request cannot be one of them. The database enforces it.
- Restore in one click. Whatever a policy or a person approved, an owner or admin can put the site back to any prior version with history preserved. Autonomy is safe because it is reversible.
Policies
What Dispatch may do for this site without waiting on a person.
Auto-approve low-risk requests
Low-risk requests go live without waiting for a reviewer. Everything stays on the record and can be restored.
Scheduled crawl
Dispatch re-crawls this site’s pages, keeps score history, and flags what slipped.
Dispatch APP 9:14 AM
Preview ready for review on yourcompany.com
req-3f9a12c4: Add a meta description to /about
By Dispatch (drafted from a finding)
Next step: Review the preview and approve or send back
Page: /about · Low risk
The request: Add a meta description to /about (currently missing). Summarize the page in 140 to 160 characters, lead with the primary keyword, and make it a complete sentence. Do not change any other metadata.
The message is the brief, not a link to one.
When a request reaches preview-ready, is sent back, is approved, or goes live, the Slack message and the email say what changed, which page, how risky, and the one thing to do next. An approver can decide from the channel.
- Slack goes to a channel you choose per site; email goes to everyone who can approve. Both open the preview and the request in one tap.
- Deliveries are queued and retried, so a slow channel never holds the change that triggered them.
Everyone opens Dispatch to their own work.
Approvers
land on the Inbox
Owners and admins open Dispatch to the page where approvals, findings, and slipped pages are waiting. Nothing to hunt for.
Operators
land on requests
Editors who run the agent open to the requests they filed and the fixes they drafted, with the handoff prompt one click away.
Owners
land on the overview
Organization owners open to the dashboard, where the Inbox strip shows counts by section and the way in.
Definition
What is proactive website governance?
Proactive website governance is the practice of continuously measuring every page of a website, detecting what slipped or fails, drafting the fix as a governed change request with the page context attached, and routing it to the person with authority to approve it, so that people keep the decision while the system takes over initiation.
Dispatch governs the work; your coding agent, repository, and host execute it. What the management layer is
Inbox questions, answered.
Quick answers on running a website that AI agents build and your team governs. More in the Knowledge Center.
The Inbox is the page in Dispatch where work waits for you. It holds change requests with a preview ready for your approval, findings from the scheduled crawl of every governed page (each with a drafted fix), pages whose score slipped since the last crawl, and the work you have in flight. Approvers land on it after login. Dispatch finds the work, drafts the fix, and puts it in front of the right person; you keep the approve moment.
You already own the tools. Dispatch makes them manageable.
The agent, the repository, the host, and the framework are yours. What the Inbox adds is production capacity without a developer queue: the fixes arrive drafted, and your team keeps the approve moment.
Everything on this page is in production now. Read the changelog