Harper Relay / Lead Manager

Catch the lead before the business leaks revenue.

Lead Manager gives owner-led teams a command layer for the messy middle: capture the lead, create the contact, collect proof, schedule the next action, keep billing visible, and hand the owner a ranked brief instead of another inbox storm.

lead source attached
context and proof captured
schedule and invoice routed
follow-up queued by industry

Built for the industries where missed calls, slow follow-up, fuzzy intake, and billing drift quietly cost money. Property management is one view; your version can be tuned to your market.

H

Industry Lead Command

Lead, action, invoice, follow-up digest

owner protected

Lead manager

First contact becomes a clean next step.

lead capturedlive
fit scoredlive
repair scheduledlive
invoice watchedlive

Glance state

24

new leads

01

nudge

02

report

03

launcher

qualified leads

12

source, intent, and fit attached

actions routed

5

issues triaged, windows attached

owner runway

3.8 hrs

calls, invoices, and follow-ups handled before review

ContactNeedStatus

Alex Johnson

Initial call - Home-service lead needs photos, location, and a booked estimate window.

Estimate

Qualified

Samantha Lee

Text inquiry - Return question answered and follow-up queued before checkout abandonment.

Cart

Scheduled

Marcus Williams

Resident call - Vendor invoice matched to work record and awaiting approval.

Invoice

Approval

Taylor Brown

Renewal form - Premium concern routed to licensed review before client shops away.

Retention

Follow-up

Pipeline running

1

call captured and contact record created

2

intent, proof, access, and constraints collected

3

urgency scored and next action window booked

4

invoice matched to work record for owner approval

5

follow-up sent when the timing is right

6

digest ranked by money, urgency, and trust risk

Manager brief

Online store: return question answered, cart saved. Contractor: estimate photos collected. Agency: renewal review queued.

Call
Contact
Schedule
Invoice

Lead Command Standard

Make the money path obvious before the owner ever opens the inbox.

The value is not another place to type notes. It is the discipline of knowing what came in, what it is worth, what is missing, who owns the next step, and what can move without you.

01 / Capture

Every inquiry lands with source, urgency, service fit, and contact intent already attached.

Lead Manager turns calls, forms, texts, referrals, and stray email into one qualified lead record so the first real reply starts with context instead of detective work.

02 / Qualify

The system separates real opportunities from low-fit noise before they steal the day.

Budget clues, timing, job details, location, prior relationship, and urgency all shape the next route: book, request evidence, nurture, decline, or send to a human.

03 / Context

Missing details get collected while the owner stays focused somewhere else.

The assistant asks for photos, documents, preferred windows, decision makers, location, and constraints, then keeps those answers attached to the lead instead of buried in chat.

04 / Route

Qualified leads move toward the right next action without waiting for a manual inbox sweep.

Follow-up, scheduling, estimates, request routing, and escalation all use the same lead state so people are not re-explaining what the system already learned.

05 / Digest

When the owner comes back, the business is summarized by money, urgency, and trust risk.

Instead of a pile of messages, Lead Manager gives a ranked list: hot leads, blocked deals, promised callbacks, waiting evidence, and actions already completed.

CRM flow demo

Watch a contact move from first call to scheduled action, invoice, and follow-up.

Property management still gets the clearest repair-and-occupancy view, but the same flow can become estimate recovery for a contractor, consult intake for a law office, cart rescue for an online store, event-change control for a caterer, or renewal retention for an insurance agency.

Initial call

A prospect asks for pricing while another customer needs support.

The system creates the contact, attaches source and intent, and keeps the opportunity moving without hiding the support or delivery risk.

Repair triage

Photos, documents, access notes, and rules get collected before action.

Job evidence, client constraints, access details, and owner approval limits stay pinned to the same CRM record.

Scheduled work

The next action is booked, the client is updated, and the follow-up stays coordinated.

Scheduling rules keep urgent work moving while sales, service, or retention follow-up waits for the right moment.

Invoice and follow-up

The owner gets approval-ready money and next-step follow-up in one brief.

Invoices, service status, consultations, renewals, carts, and appointment risk are grouped into a ranked operating snapshot.

Business Impact

A lead system should feel like revenue protection, not inbox decoration.

The live readout still matters, but it belongs under the business promise: faster first response, less context loss, cleaner follow-up, and a ranked owner brief that makes the next action obvious.

Observed live

Live check

route-aware desk, privacy, and company context

Host

harperrelay.com

Trust routes

/request-portal, /contact?from=request-portal, /privacy?from=request-portal, /about?from=request-portal

Latest desk receipt

pilot-mode follow-up queued

Tracking baseline

no non-essential cookies intentionally set

Sensitive data

passwords and payment details stay out of the desk note

This is the trust layer under the pitch: route-attached handoff, clear data boundaries, and no claims beyond what the public surface can honestly support today.

Desk route

200 on Harper Relay host

/contact?from=request-portal#message-desk

The message desk opens with Lead Manager context already attached.

The shared desk keeps /request-portal in the lead-flow context and opens with Workflow or module pilot already selected instead of restarting the handoff as generic company contact.

Collection note

named before submit

required vs optional fields

The live desk states the narrow handoff before anyone sends the message.

The desk asks for first name, last name, email, message, and human verification, keeps identity, company, address, route, and message details scoped to the handoff, and names the no-secrets boundary before submit instead of burying it in policy copy.

Sensitive data

stated before submit

message body stays high-level

Passwords, payment details, and private secrets stay out of the desk note.

The Lead Manager handoff tells buyers to name the missing file, access gap, or human owner and let Harper Relay route the secure next step, rather than dropping raw credentials into the public message body.

Desk receipt

202 pilot-mode receipt

POST /api/contact-requests via /contact?from=request-portal

A live test note stayed honest when storage was unavailable on this run.

When storage is unavailable, a valid Lead Manager test note returns the pilot-mode receipt instead of claiming the note has been stored. That keeps the shared desk aligned with the privacy note and the bounded no-login preview when manual follow-up is the truthful outcome.

Tracking baseline

stated in live desk and privacy notes

no non-essential cookies intentionally set

Cookie handling is disclosed before the lead-flow path turns into a launch claim.

The Lead Manager handoff says no non-essential marketing or analytics cookies are intentionally shipped in the current build. If that changes later, consent handling needs to move with the product before the trust path expands.

Storage path

200 on Harper Relay host

/privacy?from=request-portal

The storage and fallback story stays explicit in the trust route.

Privacy notes still say contact requests may write to Supabase when storage is live and otherwise fall back to manual pilot handling, while staying clear that Lead Manager does not create a separate hidden queue on the public site.

Company loop

200 on Harper Relay host

/about?from=request-portal

About keeps the Harper Relay company story attached to the module.

The company context route frames Lead Manager as Harper Relay lead-command work when buyers sanity-check who is behind the workflow.

Connected Operating Layer

Lead Manager becomes more valuable when it knows the rest of the business.

The clearest view is any business where one lead touches scheduling, billing, proof, follow-up, reviews, and owner approval. Property management gets a full lane below, but it is one industry view inside a broader revenue-protection system.

Human-aware scheduling

Qualified leads can move directly into protected scheduling windows.

A hot lead should not require the owner to break dinner, a meeting, or deep work just to suggest three times. Lead Manager hands scheduling the context it needs to offer clean windows.

See scheduling layer

Context Relay

Follow-up stays personal because the important details travel with the lead.

The system remembers budget, objection, timing, urgency, prior promises, and human boundaries so the next message feels informed instead of automated in the worst way.

Open Context Relay

Scenario demos

The same command layer powers emergency, sales, service, and real-life interruption flows.

Lead Manager is one expression of the broader Harper Relay idea: the system catches the trigger, gathers evidence, routes action, and gives the owner a ranked digest when they return.

Try scenario demos

Industry operating views

The small slips are where the business leaks.

Harper Relay starts as a general business operating layer. Each industry view is just a sharper version of the same promise: catch the missed signal, keep follow-up moving, protect ratings, keep money coming in, and make the next action available from your phone.

Owner-led teams

Leads, billing, scheduling, service, and reviews stay visible from the phone.

Missed calls, quote context, client updates, repair or delivery evidence, invoice approval, payment questions, handoffs, and review moments are the pieces that usually scatter.

Harper Relay captures the signal, keeps billing tasks glanceable, routes client conversations through a consistent natural-language engine, and tracks the work against standards so vendors, staff, and follow-up stay accountable.

Property management

Vacancy, turns, resident updates, repairs, and reviews become one operating lane.

Leave dates, unit marketing, resident updates, repair evidence, contractor accountability, invoice approval, and review moments are the property-specific pieces that usually scatter.

When a tenant has a leave date, Harper Relay can start the marketing path, keep make-ready tasks visible, route resident conversations calmly, and track turns against unit-ready standards so occupancy keeps moving.

Real estate teams

Lead follow-up and transaction details stop depending on memory.

Agents often lose momentum in delayed follow-up, scattered buyer/seller preferences, unsigned documents, inspection notes, and post-close referral touchpoints.

The system captures inquiry source, price point, preferred communication, showing context, transaction deadlines, and next touch so the client feels guided without the agent babysitting every reminder.

Home service operators

Missed calls become estimates, schedules, invoices, and review requests.

During busy field days, calls, photos, quote context, arrival windows, parts notes, invoice follow-up, and review requests are the first things to drift.

Harper Relay collects job evidence, scores urgency, confirms location and access, proposes service windows, queues estimate or invoice follow-up, and asks for the review while the job is still fresh.

Online stores

Cart hesitation, returns, shipping questions, and support tickets become revenue signals.

Stores often let return anxiety, shipping uncertainty, sizing questions, order-status issues, refunds, and abandoned carts sit in separate tools until the customer has already left.

Harper Relay answers published policy, routes exceptions, tags the actual objection, queues follow-up by concern, and shows owners where product pages or checkout are leaking trust.

Law and professional firms

Intake, consultation, retainer, document, and billing tasks stay in one lane.

Small firms often let missed-call intake, conflict details, consultation scheduling, engagement letters, retainer follow-up, time capture, and invoice clarity slip during client work.

Harper Relay turns inquiries into structured intake records, queues the next client touch, keeps billing tasks visible, and gives the professional a ranked review list before a good matter goes cold.

Catering companies

Event changes, guest counts, dietary needs, and deposits stay tied together.

Caterers lose margin and calm when guest-count changes, access windows, allergies, menu substitutions, staffing notes, deposits, and final invoices scatter across calls and texts.

Harper Relay captures the change, checks capacity and menu rules, drafts the quote delta, requests owner approval only when needed, and sends a clean client confirmation.

Insurance agencies

Renewal concerns and quote starts become retention work before clients shop away.

Agencies often let premium-increase questions, missing documents, quote follow-up, payment-plan questions, and policy review requests wait behind producer appointments.

Harper Relay collects policy context, keeps licensed-review boundaries clear, routes churn-risk renewals, and gives the agency a ranked retention queue without making coverage promises.

Verified Inputs

/request-portal stays attached when the Lead Manager desk opens
workflow or module pilot is already selected in the live form
required vs optional fields are stated before submit
passwords, payment data, and private secrets are kept out of the public note
the live desk repeats the no-tracking baseline before submit
privacy and about routes keep the Harper Relay Lead Manager context intact

Boundaries

client logins, lead vaults, or portal screenshots that are not actually live
autonomous triage claims that outrun operator reality
project-management language that turns a service module into platform sludge
hidden routing limits or buried privacy notes near the CTA

Start Here

Stop letting leads rent space in your personal life.

Give Harper Relay the recurring lead paths that currently depend on you being awake, available, and emotionally ready to chase details. The system can qualify, collect, route, and summarize before you decide where your attention goes next.

lead capturefit scoringcontext collectionowner digest

Prepare This

the lead sources that currently get missed or answered late
the questions you ask every qualified prospect anyway
the signals that separate hot revenue from low-fit noise
the decisions that still need owner or manager approval

Trust Notes

Requests route through /contact?from=request-portal#message-desk; this page does not add a separate public login, lead vault, or hidden queue.
Privacy at /privacy?from=request-portal describes the current contact and audit storage routes plus the server-side fallback behavior.
Do not send passwords, payment card numbers, or private secrets through /contact?from=request-portal#message-desk; use the note to flag the access gap so Harper Relay can route the secure next step.
No non-essential marketing or analytics cookies are intentionally shipped in the current build, so the lead-flow path can stay clear about the current consent baseline without adding a consent pattern the product does not need yet.
About context at /about?from=request-portal keeps the same Harper Relay company story in view if the buyer checks who is behind the workflow.
The broader direct public privacy-request owner is still a site-level trust task, so this page stays honest about what is live today while the lead-flow layer keeps improving.
Review the scheduling layer