Example: business readiness pulse
An assessment page scored by a pinned instrument version, where every participant is emailed their own snapshot report and can opt in to send a copy to their advisor.
The business: an advisory programme that assesses the businesses it supports across several readiness dimensions. The questionnaire is already a published instrument, so the scoring is not something the page invents — the page's job is to collect the answers, hand them to the instrument, and send each participant their own snapshot report.
The goal: one public assessment page, scored by a pinned instrument version, where every participant gets a personalised report by email and the programme team gets the run.
This is one of three conversion page examples. It needs instruments, which are set up under Settings → Instruments; see Instruments overview if your organization hasn't published one yet.
This is the page shape to copy whenever the result is the deliverable — the submitter is owed something back, not just routed to somebody internally.
Fields and scoring — the instrument owns the maths
Form tab for the questions. Scoring tab stays off and reads Scoring · 0:
qualification scoring and an instrument are two different scorers, and this page
uses the instrument. Turning both on means two answers to "how did they do".
Each question that feeds the instrument needs a Field ID matching the input you will map it to. Name them deliberately now — after publish, renaming one is a change publish makes you approve.
Bind the instrument
Handoff tab, under Submission binding → Instrument, beneath the confirmation settings.
- Instrument version — pick the published version. The page pins that exact version, so a later publication cannot change what past and future submissions are scored against without you deciding to move.
- Fill every input — one row per declared input, one source each: a form field on this page, or a page value such as the page slug, the submission id, or a pinned programme or cohort key.
- Fix anything flagged. Problems are stated beside the input they belong to — "The form has no field called consent", "The answer type does not match what score expects."
The pinned instrument counts as a destination, so a page that creates a lead and
scores with an instrument reads Handoff · 2 even before any routing switch is
on. See Score a conversion page submission with an
instrument for what happens when the
pinned version is later retired.
Publish first — the snapshot email needs a live page
The Snapshot email section appears on the Handoff tab only once the page is live and bound to a supported instrument. It is not a draft field: it is the live page's own setting, the same one the Details screen edits, on the same row. Editing it in the builder and editing it on Settings → Conversion Pages → your page → Overview are the same edit — there is no draft copy to publish and no second version to keep in step.
So the order is: bind the instrument, publish the page, then come back to Handoff and set up the email.
Snapshot email
Handoff tab, below Submission routing, on the live page.
-
Enable Email participants their snapshot.
-
Write the Email subject, Introduction, and Closing. These are the participant-facing wrapper around the report.
-
Under the advanced fields, write the dynamic paragraphs. They are templates, not fixed sentences, and the fallbacks exist because a real result does not always have a clear winner:
Field Used when Support heading / Priority support paragraph Normal case — names the lowest-scoring dimensions that need development Support paragraph when all dimensions show strength Nothing is lagging enough to single out Strengths heading / Strengths paragraph Normal case — names the highest-scoring dimensions Strengths when all dimensions are at an early stage Scores are level and early; there is no differentiated strength to name Strengths when all dimensions are balanced at a later stage Scores are level but mature Strengths when no priority dimension needs support Strengths exist but nothing needs singling out for support Write every one of them. The fallbacks are what a participant reads when their results are flat, which is exactly the participant most likely to conclude the report is generic.
-
Save email draft, choose a completed submission, then Preview email and Preview PDF. Previews send nothing.
-
Publish email template.
Editing this wording changes presentation only. It never changes a score, a dimension classification, or what consent allows the report to include.
What publishing the email template does and does not reach
Publishing applies to future submissions. Reports already prepared keep the copy and appearance they were prepared with, so a participant who asks about the report they received last month is asking about a document that still exists as they received it.
If you are also changing the report's branding — logo, colours, font, section headings — publish the appearance first on the instrument's Snapshot format card, then publish the page's email template, so the template captures the appearance you intend. See Customize the instrument snapshot report.
The confirmation screen is a different setting
The screen the participant sees the moment they submit is not part of the snapshot email. It is on the Page tab under After submitting, and an authored ending for the submission's outcome takes precedence over the page's general thank-you message on the Details screen's Page content.
Two surfaces, two edits — the confirmation screen is instant, the snapshot arrives by email once the report is prepared. Say so in the confirmation copy, or the participant reads silence as a failure and submits again.
An optional copy, only with permission
In Snapshot email, add up to five named recipients — a programme manager, an advisor — and enable Offer participants an optional copy to these recipients.
The assessment then shows those names and addresses with an unchecked optional consent checkbox, and the copy is sent by BCC only when the participant agrees. This is a separate permission from the participant's own report. Change the list and the participant must review it again before the next send.
A week later
The programme lead opens the page's Submissions tab and finds each response, the run it produced, and the record it created. On a run, the Snapshot email card states delivery — prepared, accepted by the email provider, or needing attention with the reason beside it — and Download snapshot PDF produces exactly what the participant received.
A participant who never saw their report is answered from that card, not from a guess about whether email works.