Opportunity Relay Bilingual lead-response systems for U.S. service businesses Get a 3-point lead-flow review

Operational system · isolated public tour · no client-result claim

Bilingual Lead-Response Control Room

See how a website inquiry keeps its English or Spanish context and reaches a named owner. The isolated tour stops before customer contact; the authenticated path governs approved delivery and its receipt.

Inspect the case study
Proof type
Operational system + isolated public tour
Buyer
U.S. home and property service operator
Languages
Equivalent English / Spanish logic
Last reviewed

Isolated public tour / 01

Follow one inquiry from capture to a controlled next step.

Fictional operator: Cedar & Stone Home Services. Do not enter names, email addresses, phone numbers, or real customer details.

Quick starts

Choose the inquiry you want to inspect.

One click loads and validates the fictional event.
Or enter a bounded fictional inquiry

Markup is rejected by strict validation. Urgent wording, an unsupported area, or an ambiguous service stops for human review; no safety, price, diagnosis, or scheduling decision is made.

Current state Ready

Ready. Run a guided scenario or enter bounded fictional context.

Owner
Not assigned
Next action
Run a scenario
Due
Not started
Language
Not set
Channel
Website
Exception
None

This demo run

Transitions
0
Simulated CRM updates
0
Duplicates prevented
0
Real external effects
0
  1. 01
    Inquiry captured Waiting Language and website channel retained.
  2. 02
    Context validated Waiting Service, area, language, and message checked.
  3. 03
    Duplicate checked Waiting Stable event and idempotency keys compared.
  4. 04
    Acknowledgement proposed Waiting Bilingual draft remains unsent.
  5. 05
    Routing rule applied Waiting A visible service-area rule decides the lane.
  6. 06
    Owner assigned Waiting A named owner or review queue becomes accountable.
  7. 07
    Human approval Waiting Exceptions and external action stop for a person.
  8. 08
    CRM event simulated Waiting The public adapter records no real update.
  9. 09
    Next step recorded Waiting Status and operational due state stay visible.
  10. 10
    Audit completed Waiting Every accepted transition keeps a stable event ID.

Fictional input

Inquiry record

Event not created
Operator
Cedar & Stone Home Services
Source
Website
Language
—
Service
—
Service area
—
Idempotency key
—
Request

No inquiry loaded.

Deterministic rule

Routing decision

Fixed rule

Waiting for validated service and area context.

Assigned lane
—
Decision basis
Service + area, never language

Proposed acknowledgement

Reviewable text

Model-assisted simulation
No text has been proposed. The public demo never sends email or SMS.

Release boundary: unsent draft · human approval required · no price, diagnosis, appointment, or commitment.

Human control

Start with a fictional inquiry.

The server validates every transition before the interface changes.

Public adapter boundary

Email: no-opSMS: no-opCalendar: no-opCRM: simulated

Only the same-origin control-room API is called. It stores bounded demo context in process memory and logs no message text or personal data.

Portfolio evidence ledger

Evidence, production controls, and release assurance.

Isolated public tour · fictional or synthetic data · operational controls verified separately.

Exact role
Designed and implemented the typed state contract, shared bilingual decision logic, server validation, approved routing and templates, encrypted persistence, role-based approval, idempotency, signed downstream delivery, terminal retry handling, and a global audit-integrity root.
Human boundary
A person approves every exception and operational downstream action. Pricing, availability, diagnosis, safety, booking, customer contact, and external CRM changes remain outside the isolated public tour.

Evidence in the build

Workflow contract
10 explicit stagesThe visible path covers capture, validation, duplicate check, acknowledgement, routing, ownership, approval, delivery or isolated simulation, follow-up, and audit.
Decision parity
Shared English / Spanish rulesEquivalent inquiries produce the same owner, exception, next action, and audit decision in either language.
Transition authority
Server validatedThe interface proposes events, while the server accepts only legal transitions and returns structured recovery errors.
External action
Isolated tour · signed operationsThe public acknowledgement and CRM event are no-ops; operational approval creates one signed idempotent delivery with a durable receipt or explicit terminal failure.
Run boundary
This demo runVisible counts describe only the current browser session and never imply customer or client performance.
Commercial result
Not claimedNo booking, revenue, response-time, accuracy, safety, or labor outcome is attributed to fictional data.

Tests actually run

  1. 226/226Full unit suite

    Completed Task 01 repository run after the final server and store slice.

  2. 28/28Focused domain, API, portfolio, and deployment unit checks

    Task-specific release-candidate checks; no active-server validation was performed.

  3. 136/136Full Playwright suite

    Included flagship, no-JavaScript, keyboard, reduced-motion, mobile, and axe scenarios.

Production controls implemented

  • Encrypted SQLite workflow records survive restart with private database files, bounded retention, explicit purge, versioned backup generations, and verified off-site recovery evidence.
  • Workspace-scoped viewer, operator, reviewer, and administrator credentials use salted scrypt verification and keep read, capture, approval, rejection, retry, and delivery permissions separate.
  • Approved bilingual service catalogs, service areas, owners, queues, routing policy, and acknowledgement templates drive one deterministic decision path.
  • Before any webhook call, the service persists a delivery lease with a stable event and idempotency key; transient retries reuse the same payload and honor bounded Retry-After guidance, while permanent or exhausted failures become terminal.
  • HMAC-authenticated transition evidence and a global integrity root detect modification, reordering, or deletion; bounded logs, exact-host admission, isolated rate limits, and server-side secrets preserve accountability without exposing inquiry content.

Enforced production activation gates

  • Operational mode starts only from a validated workspace configuration with named owners, approved policies, retention, recovery objectives, and a monitored destination.
  • Credentials, encryption keys, and webhook secrets remain server-side; the fictional public tour cannot read operational records or trigger a live connector.
  • The readiness gate verifies signed activation evidence and refuses operational startup when authentication, durable audit, current off-site recovery proof, monitoring, or a required downstream destination is unavailable.

Case study / Buyer + leak

The buyer needs fewer invisible handoffs—not another inbox.

Buyer

An established U.S. home, property, maintenance, or field-service operator receiving website inquiries in English and Spanish.

Leak

Language, service context, and ownership can disappear between acknowledgement and follow-up, while retries can quietly duplicate work.

Workflow / 10 declared stages

One decision path for both languages.

  1. 01

    Inquiry captured

    Language and website channel retained.

  2. 02

    Context validated

    Service, area, language, and message checked.

  3. 03

    Duplicate checked

    Stable event and idempotency keys compared.

  4. 04

    Acknowledgement proposed

    Bilingual draft remains unsent.

  5. 05

    Routing rule applied

    A visible service-area rule decides the lane.

  6. 06

    Owner assigned

    A named owner or review queue becomes accountable.

  7. 07

    Human approval

    Exceptions and external action stop for a person.

  8. 08

    CRM event simulated

    The public adapter records no real update.

  9. 09

    Next step recorded

    Status and operational due state stay visible.

  10. 10

    Audit completed

    Every accepted transition keeps a stable event ID.

Controls

Rules decide the lane. People decide the consequence.

  • Server-validated stateIllegal and stale transitions return a code plus recovery guidance.
  • Stable identityEvent, action, audit, and idempotency IDs stay visible and retry-safe.
  • Shared bilingual logicLanguage selects text; service and area select the operational route.
  • Bounded untrusted inputStrict JSON, length, origin, content-type, rendering, and rate limits apply.
  • Human release gateNo acknowledgement or CRM action leaves the isolated public tour.

Failure modes

Exceptions stop where their owner can see them.

Missing context
Held before acknowledgement or routing.
Unsupported area
Sent to coverage review without promising service.
Ambiguous service
Sent to service triage without guessing.
Urgent wording
Escalated to a person without making a safety decision.
Model unavailable
Uses the approved unsent fallback; deterministic routing and human approval remain intact.
Simulated CRM unavailable
Stopped visibly; an explicit retry reuses the same key.

Test evidence

The claim is bounded to behavior we can reproduce.

Language parity

Equivalent English and Spanish inputs produce the same owner, rule, and next action.

Idempotent retry

Timeout and replay keep one key and no more than one simulated CRM update.

Safe failure

Invalid, hostile, oversized, rate-limited, model-down, and adapter-down paths fail visibly.

Operational delivery controls

Production mode persists the decision and delivers only after approval.

Encrypted workflow state survives restart; workspace roles control review; approved bilingual catalogs and templates drive routing; and a signed HTTPS connector records stable idempotency and durable receipts. Transient failures honor bounded Retry-After-aware backoff; permanent or exhausted failures become terminal for authorized review. An authenticated event chain and global integrity root detect modification, reordering, or deletion. The public tour remains isolated and can never invoke that connector.

Map the current lead path

Find the first controllable response gap.

Answer five operational questions before deciding whether a new workflow or integration is useful.

Get a 3-point lead-flow review