Harper RelayStartStart the operating snapshot

Harper Relay / Context Relay handoff

Message the desk.

You came from Context Relay. The message desk opens with multi-account support context already attached, so the team can review stale knowledge, unsafe escalation gaps, or branded support drift without turning the request back into a generic AI chat note.

Start the message Read privacy

Lead context attached

Human-aware follow-up

Personal time protected

Message desk

Route-aware notes land with context.

source route attachedlive

privacy boundary setlive

owner reply draftedlive

follow-up queuedlive

Glance state

clean handoff

nudge

report

launcher

Context Relay handoff reviews

stale docs, FAQ drift, or launch-change freshness issues

human escalation rules for policy exceptions, account disputes, or sensitive requests

Message Desk

Tell us where freshness or escalation is drifting.

Use this route-aware desk to flag stale answers, weak escalation rules, or cross-account support drift. The quickest useful note is the exact support moment where the knowledge stops being safe to reuse.

send a message

Identity

First name, last name, and email are required so the lead can be routed cleanly.

What feels off

Name the page, workflow, or handoff and keep secrets out of the message.

Human check

A bot check runs before submit; failed checks can be corrected and sent again.

Rollout context

Opened from Context Relay. Request type defaults to Workflow or module pilot and the route starts at /agency-knowledge-bot so the team can review the same rollout story you just came through.

What We Need From You

This rollout handoff collects only the account, freshness, escalation, and reply details needed to review the Context Relay path. The route stays attached, and the desk stays explicit about what is stored versus what still routes manually.

Required now: first name, last name, email, message, and human verification; /agency-knowledge-bot stays attached on arrival.

Optional context: phone, customer type, company, address, quick-note seed, and discount or phone-follow-up preferences.

First name requiredLast name requiredEmail requiredPhone optional

Message required

Add expanded details

Request type

Website or route optionalCompany optionalCustomer typeExtra detailHelpful starters

I want a phone walkthrough if the issue is easier to explain live.Send me current domain and launch discounts. If checked, add an email so we can send codes.

Human verification

Loading the human check...

Review Context Relay

Add first name, last name, email, and the message details you have now.

Attached automatically

Rollout context: attached

Current page: /contact?from=agency-knowledge-bot

A sealed route token is generated on submit for internal routing.

Behind the scenes

Your note becomes a cleaner internal handoff.

The public form stays simple. When you send it, the server quietly attaches page context, route clues, reply path, and a sealed token so the team gets a better prompt without exposing sensitive data in the page itself.

sealed routing

1. We keep the public note narrow: name, email, message, route context, and optional extras.

2. The server checks the message body for spam patterns and sensitive secrets before routing.

3. Human verification runs before submit; failed checks can be corrected and sent again.

4. The team sees a cleaner review handoff with the route token, receipt status, and site-review trigger attached.

Live Relay is online. Operators can answer in real time when staffed; if nobody is active, the note still lands in the review log.

Internal handoff

Visitor ask

Attached route and page context

Sealed context token

Generated routing prompt for the next reviewer

Strong notes usually include

the account, source set, or knowledge area where the answer drift starts

the escalation, freshness, or brand-governance rule that feels unsafe

what the operator should see first when the review lands

Best Next Moves

Start with the path that keeps the review honest.

Stay inside the Context Relay handoff unless the issue widens into broader website ownership. The fastest trusted next move is usually the one that keeps the source map, privacy path, and company context attached to the same Harper Relay story.

Review Context Relay when stale answers, escalation rules, or account drift are the real issue

Go back to the Harper Relay rollout page when you need the source-ownership, freshness, and escalation model in view before writing the note.

Open Context Relay

Check privacy notes when the hesitation is storage, tracking, or the no-secrets boundary

This keeps the route-attached desk, the current no-tracking baseline, the Supabase-or-manual fallback, and the bounded rollout handoff in one Harper Relay trust path.

Read privacy notes

Use the Harper Relay company context when the question is ownership, surface split, or how the rollout fits the broader service

That page explains why Context Relay stays a Harper Relay service surface and how it relates to the human-aware scheduling layer without turning into platform theater.

Open about context

Step up to Human-Aware Scheduling when the break is wider than support governance

Use the parent service when the issue is no longer just freshness or escalation drift and now spans page promise, proof, handoff, or ongoing upkeep.

Open scheduling