Sending an enquiry from the public website — and the partner intake form

Who this guide is for: visitors and prospective customers thinking about ConvoTide (no sign-in needed), and PARTNERS registering interest through the partners page. Administrators may also read it to know exactly what a website visitor experiences.

This guide shows how a visitor's enquiry on the public pricing page and a partner's registration on the partners page travel into the business: what the form sends, what it deliberately never sends, what the honest answers look like on every path — received, already received, refused, or unreachable — and what the shipping-default site does before the intake endpoint is deployed.

About the pictures. Simulated journey, real boundaries. The screenshots were captured in an isolated local run on the guide lane's own ports (4760–4779): the real static site build (the same artifact class the release ships) served by the repo's own loopback server, submitting to the real POST /v1/leads/public-intake endpoint backed by a real throwaway PostgreSQL cluster. The businesses, people and email addresses are synthetic. This is not a live-site claim and not a deployed-endpoint claim — see What is live and what is not.

Step 0 — The shipping default: no form, no claims

Until the intake endpoint is deployed and the site is built with the intake binding, the public site renders no enquiry form at all. The pricing page's enquiry section shows contact routes — Contact our team and an email link — and nothing can be submitted, so nothing can be silently lost.

Release artifact with no intake form

This is the honest default: rather than a form that pretends, the site names the missing dependency and routes you to a human.

Step 1 — Fill the enquiry form (pricing page)

When the site is built with the intake binding configured, the enquiry form appears. It asks for the minimum — name, email, what you need — plus one separate question: whether to opt into occasional product news. The opt-in starts unchecked: not choosing it means no marketing, and the site says so after submission.

Pricing enquiry form filled

Step 2 — Submit: "Request received." only after a real 201

Pressing submit sends exactly one thing to the endpoint: { siteToken, name, email, message, consent }. The site token is a public identifier for the business — the org is resolved server-side; no business secret ever ships to the browser. When the endpoint answers 201 { captured: true, deduplicated: false }, the notice says:

Request received. Your enquiry reached the ConvoTide intake queue. A person will review it and reply to your email. You were not added to any marketing list.

Request received after a real 201

Step 3 — Submit again safely: "Already received."

Send the same enquiry twice and the endpoint answers 200 { captured: true, deduplicated: true }: the original stands, no duplicate is created, and the notice says so plainly.

Already received — honest dedupe

In this lane's run, the database truth behind those two answers was exactly one public-intake capture row and one contact for that email address.

Step 4 — The partner programme form (partners page)

The partners page has its own form with its own separate site binding: partner enquiries are attributed through the partner token, never the pricing token, and the server resolves which business each token belongs to. The programme-news opt-in there is likewise a separate, optional choice — it is not part of the enquiry itself.

Partner form filled with opt-in checked

A genuine receipt — 201 with captured: true — is acknowledged as:

Partner enquiry received. Your enquiry reached the ConvoTide intake queue. Your optional programme-news choice was recorded separately.

Partner enquiry received

Step 5 — On a phone

The same journey works at 390 px — form, submission and received notice.

Received notice at 390px

If you see an error

What you see What it means What to do
A notice saying the enquiry was NOT delivered, with your typed draft still in the form The endpoint could not be reached; nothing is claimed as sent Retry from the preserved draft — no retyping needed; the button re-enables
A refusal notice (rate limiting, validation, payload limits), each with its own wording, draft preserved The endpoint refused this submission on its own rule Follow the notice's wording (for example wait and retry after a rate limit); the draft stays for an honest retry
"Receipt could not be confirmed" (partner form) The response was not a genuine receipt shape — a wrong body, a 5xx, or an interrupted connection Never treated as received; retry from the preserved draft

Failure notice with draft preserved

What the visitor's data is and is not

What is live and what is not

What this guide does NOT claim (kept honest)

Where the receipts live

What Where
This lane's fresh journey (screenshots above) — real static artifact + real endpoint + throwaway PG + real Chromium 1440/390; 1/1 passed, 8 recorded steps services/wa-app/tests/guide-journeys-3310-public-intake.test.ts on the sibling branch; shots + public-guide-journey-steps.json under C:/CT-ZC-3310-guides/services/.lane3310-evidence/public-guide-shots/
AGOS cross-engine release-artifact matrix — enquiry + partner specs, all three release-candidate builds, all three engines — 81/81 passed (chromium 27/27, firefox 27/27, webkit 27/27), 2.4 min; native original PID 1442349 on AGOS, branch codex/zcode-3294-egrerun @ 9679ffa0b, remote logs 10.10.10.168:/home/ccsbroker/codex-qc/zc3294-egrerun-9679ffa0/ handover C:/CT-ZCODE3244/zcode-full-plan24-3244/HANDOVER3294.json
Real-endpoint behaviour over real PG (binding, dedupe, isolation, CORS, PII-safe logs) — 9/9 passed (AGOS job ZC2802-EG-RT-02) recorded in C:/CT-ZCODE3244/zcode-full-plan24-3244/RESULT.json agosRuntime
First-run failure classification (51/81, 30 contexts) and the root-cause ledger — all 30 root-caused; fixes verified by the 81/81 rerun C:/CT-ZCODE3244/zcode-full-plan24-3244/lane-3280-egfix-ledger.json; contexts preserved in …/egrt01-failures/

Honest scope note on the AGOS matrix: its browser-side submissions stub the endpoint at the browser network layer (nothing left the machine), so it proves the artifact behaviour; the endpoint behaviour is proven by the real-PG/HTTP runs (EG-RT-02 and this lane's journey).


Evidence record (kept for honesty). Written from the BATCH3310/3456 guides lane's recorded passing runs named in the receipts table above — every run is local candidate / test-substrate evidence, pending Chief acceptance and Main integration; no live-site or deployed-endpoint claim is made. Carried into this corpus from sibling branch codex/zcode-3456-guides (identical bytes on codex/zcode-3310-guides) and rewritten to this corpus's customer instruction standard on 26 October 2026; every fact, verbatim message, receipt path, PID and revision above is preserved from the source chapter.