Reply forms

Any claimed page can collect replies. Mark a plain HTML form with one attribute — Pagelive wires the submit handling, spam protection, storage, and notification when the page is served.

+ +

Reply forms

1. Mark the form

Add data-pagelive to any <form> in your page's HTML. No action, no endpoint, no key, no script of your own.

Marked reply form

<form data-pagelive data-pagelive-success="✓ Got it — we'll be in touch.">
  <label>Your name <input name="name" required></label>
  <label>Decision
    <select name="decision">
      <option>Let's proceed</option>
      <option>Book a call first</option>
    </select>
  </label>
  <label>Notes <textarea name="notes"></textarea></label>
  <button type="submit">Send reply</button>
</form>

Field name attributes become the reply's keys — name them clearly.
data-pagelive-success (optional) sets the message shown in place of the form after a successful submit.
Text inputs, selects, textareas, radios, checkboxes all work. File uploads are not captured.

+ +

Reply forms

2. Publish

Publish the page from the dashboard or from Claude. The form works the moment the page is live. Claimed pages only: anonymous quick-publish pages can't collect replies — there's no owner to deliver them to. Claim the page first.

+ +

Reply forms

3. Read the replies

Email — you get one the moment each reply arrives, with the full submission.
Dashboard — the page's manage view has a Replies section (newest first).
From Claude / agents — the connector's list_form_submissions tool returns them as structured data: "Did anyone reply to the proposal?"

+ +

Settings

Capture is on by default for marked forms. Turn it off per page in the dashboard (the page's Replies tab) — no need to edit the HTML.
Don't want to write the form yourself? The same tab has a copy-paste AI prompt — give it to Claude with the Pagelive connector and it wires the form into your page and republishes it.
Checkbox groups and multi-selects work: repeated field names arrive as one comma-joined value.

+ +

Limits & privacy

Spam protection is automatic: a hidden honeypot, same-origin checks, per-visitor and per-page rate limits, and a size cap (up to 40 fields, ~16 KB per reply).
Replies are stored privately with your page — never indexed, never used to train AI, never shared. Visitor IPs are salted-hashed, never stored raw; location is coarse country only. See the privacy policy.
The person replying needs no account and no login.

Live example: a demo proposal with a reply form · Feature overview: Reply forms