The Alactic library

Lead capture guides

From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.

20 articles in Lead capture

Clear filters
Lead capture

Keep enquiry capture available while the main form is broken

A broken form needs more than an alternative email address. Use a checked fallback channel, clear visitor wording and a shared capture record, then reconcile every enquiry before closing the interruption.

10 min read
Lead capture

Confirm that an accepted enquiry reached the intended destination

A success message is not proof that an enquiry reached your CRM or inbox. Use a synthetic test and a filled reconciliation checklist to connect acceptance evidence to a destination record—and investigate gaps safely.

9 min read
Lead capture

Prevent repeat submissions when visitors are unsure a form worked

A disabled submit button is only the first safeguard. Define clear submission states, preserve the identity of an attempt, and make retries safe when the server receives a form but the visitor never sees the response.

10 min read
Lead capture

Recover form errors without erasing the visitor's answers

Specify error messages, preserved answers and recovery actions together so visitors can correct an enquiry without rebuilding it.

10 min read
Lead capture

Ask for missing enquiry details without making visitors start again

A missing detail should not mean a new form. Use a focused message brief to preserve what the visitor already submitted, clarify the one unresolved point, and recognise when capture is complete.

10 min read
Lead capture

Design save-and-resume behaviour for unfinished enquiries

Define what saving protects, how visitors return, when access expires and what turns a draft into a submitted enquiry—with a filled worksheet and release checks.

9 min read
Lead capture

Decide what makes an incomplete enquiry worth accepting

Separate missing essentials from missing detail so your form accepts clear enquiries, clarifies ambiguous requests and offers honest alternatives when a reply is not possible.

10 min read
Lead capture

Choose when phone verification is worth the extra capture step

A well-formatted number is not a verified number. Use a filled decision table to decide when a possession check is necessary, what it proves, and how to preserve enquiries when checks fail.

10 min read
Lead capture

Capture business phone extensions and alternate numbers clearly

Separate the main phone number, its extension, and an optional alternate number so staff can read what visitors supplied without guessing who owns each number.

10 min read
Lead capture

Validate international phone numbers without rejecting plausible enquiries

Separate formatting, interpretation and numbering-plan checks so uncertain phone entries can be reviewed without blocking plausible enquiries or becoming contact-ready by mistake.

9 min read
Lead capture

Decide whether a phone number must be required on an enquiry form

Require a phone number only when the selected service needs it. Use a filled decision table and acceptance tests to distinguish essential, optional, and replaceable contact details.

9 min read
Lead capture

Preserve enquiry context when visitors move between pages

Define what a shared contact form should remember, what visitors must be able to change, and how stale drafts should behave without losing their message.

9 min read
Lead capture

Handle missing and conflicting source values at form submission

Stop filling source gaps by guesswork. Define capture-time acceptance rules, preserve evidence separately, and record unknown and conflicting values as different states.

10 min read
Lead capture

Separate lead source fields that answer different capture questions

Keep submission channel, observed arrival context and self-reported discovery separate, with clear rules for missing answers, rejected tags and collection methods.

9 min read
Lead capture

Choose an accessible alternative to a form control that blocks enquiries

Review enquiry controls for keyboard operation, clear labels and recoverable errors. Use a filled checklist to decide what passes, what needs revision and how blocked visitors can still get in touch.

9 min read
Lead capture

Make mobile enquiry forms usable without a perfect connection

Specify how a mobile enquiry form handles keyboards, errors, saved answers and uncertain submissions. Use a filled hypothetical acceptance checklist to plan device tests and decide what must change before release.

10 min read
Lead capture

Write enquiry form labels that prevent ambiguous answers

Turn vague fields such as Contact, Location and Requirements into clear requests, with a filled copy review and correction messages that match actual validation.

9 min read
Lead capture

Choose a single-page or multi-step enquiry form

A multi-step form does not remove work; it changes where users encounter it. Use a filled decision table and step map to choose a structure that handles dependencies, interruptions and recovery.

10 min read
Lead capture

Decide when an enquiry form should use conditional questions

Use conditional sections when an answer makes later questions genuinely irrelevant. This worked branch map shows what to require, what to clear when answers change, and how to test every reachable submission path.

10 min read
Lead capture

Choose which fields belong on the first enquiry form

Use a filled field-decision worksheet to decide what to require, make optional, defer or remove—and test whether your team can handle the resulting enquiries.

9 min read

Turn a guide into a working customer journey.

Explore the tools and services behind the operating process.

Explore Communications