Back to all articlesLead capture

Confirm that an accepted enquiry reached the intended destination

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The website says the enquiry was sent, but staff cannot find it in the CRM. Start by separating what the website confirmed from what the destination can prove. A success message, an acceptance receipt, a stored enquiry and a staff notification are different pieces of evidence.

To confirm that an accepted enquiry reached its intended destination, submit a clearly marked synthetic enquiry, retain its acceptance evidence, and find the corresponding record in the exact store or inbox staff rely on. Match the test marker and important field values, not just a nearby timestamp. If the record is missing, investigate the gap before resubmitting: the original may already exist somewhere outside the current view.

The checklist below is a recommended operating practice, not a claim that any particular product provides receipts, searchable logs or reconciliation tools.

1. Define what each confirmation actually means

Ambiguous language makes missing enquiries harder to diagnose. Before testing, write down the meaning of each confirmation your current setup exposes.

  • Browser success: the page displayed a success state. Without checking its behaviour, this proves only what the visitor saw.
  • Capture acceptance: the receiving service acknowledged the submission. Establish whether that acknowledgement means it accepted the request for processing or durably stored an enquiry. Do not assume the two are equivalent.
  • Destination confirmation: the intended record store contains the enquiry, or the intended inbox contains the enquiry message, with enough detail to identify and use it.
  • Notification confirmation: an alert about the enquiry reached a staff-facing channel. This does not establish that a separate destination record exists.

A receipt identifier is useful for tracing an event, but its meaning depends on what issued it. It might identify an accepted request rather than a CRM record. Likewise, a notification containing the full enquiry text can demonstrate that the notification arrived without proving that the CRM saved anything.

If the inbox itself is the intended destination, finding the complete enquiry there can confirm arrival at that destination. Distinguish that message from a separate alert saying that an enquiry was received elsewhere.

2. Name the destination before looking for the record

“Check the CRM” is too vague for a reliable test. Specify the workspace, record type and location in which staff expect to find an enquiry. If an inbox is the destination, specify the mailbox and folder rather than an individual’s recollection of receiving an email.

Record whether a successful submission should create a new record, update an existing contact, or add an enquiry to an existing record. Otherwise, a correctly updated contact can look like a missing submission when the tester searches only for newly created contacts.

Also define the minimum useful contents. A record with the test name but no enquiry text may prove that something arrived, yet still fail the operational test. Check the fields staff need to understand and respond to the enquiry, plus any source information your process depends on.

There is a trade-off between a narrow and a broad search. The normal staff view tests whether the enquiry is readily discoverable. A broader, authorised search helps distinguish a missing record from a hidden one. Use both when necessary, but do not treat privileged visibility as proof that ordinary staff can find the enquiry.

3. Prepare a synthetic enquiry that cannot be mistaken for a customer

Use invented details and a contact address controlled by your organisation. Mark the name and message unmistakably as a test. Avoid copying a real customer’s enquiry or using a stranger’s telephone number.

Give each submission a distinct marker that can travel with the message text. If the form does not offer a reference field, put the marker in the enquiry body. A marker helps connect evidence across systems, but it is not an access credential and should contain no secrets.

Before submitting, check whether the test could trigger customer-facing responses, external messages or downstream actions. Use a suitable test environment where it answers the question, or obtain authorisation for a controlled production test. A test environment can demonstrate the method without proving that production routing works.

Fictional worked example: all identifiers, times, addresses, results and timing targets below are hypothetical. An organisation wants its website enquiry to appear in its production Sales workspace as a Website Enquiry record. An email to a shared alerts mailbox is only a notification.

  • Test name: SYNTHETIC TEST — Capture Check.
  • Reply address: a test mailbox controlled by the organisation.
  • Message: SYNTHETIC ENQUIRY — no customer action required. Marker CAPTEST-ALPHA. Please use only for authorised capture verification.
  • Expected destination: Sales workspace, Website Enquiry records.
  • Expected content: test name, controlled reply address, complete message and website source.
  • Hypothetical checking target: inspect the destination within ten minutes of submission. This is a locally chosen test target, not a delivery promise.

4. Use a filled capture-reconciliation checklist

The following fictional entries show how to link a submission to evidence and a discrepancy action. Each entry represents a separate authorised synthetic submission. Replace the values and evidence locations with those available in your setup; do not invent a receipt if the system does not expose one.

Test A: capture and notification both confirmed

  • Submission: CAPTEST-ALPHA, submitted through the published contact form at 09:10, recorded in UTC.
  • Browser evidence: success message captured in the test evidence folder.
  • Receipt evidence: acceptance reference ACK-A71, retrieved from the available submission history; its documented meaning is accepted for processing.
  • Destination evidence: Website Enquiry record ENQ-410 found in the Sales workspace at 09:12. Marker, reply address and full message match.
  • Notification evidence: matching alert found in the shared alerts inbox at 09:13.
  • Result: destination capture confirmed; notification arrival separately confirmed.
  • Discrepancy action: none. Retain evidence and handle the synthetic record under the agreed test-data cleanup process.

Test B: notification fails, but capture succeeds

  • Submission: CAPTEST-BRAVO, submitted at 10:00 UTC with the same test fields and a distinct marker.
  • Browser evidence: success message recorded.
  • Receipt evidence: acceptance reference ACK-B22, accepted for processing.
  • Destination evidence: Website Enquiry record ENQ-411 found at 10:02. All required fields match.
  • Notification evidence: no matching alert found in the shared inbox or its checked folders by 10:10; available notification history shows a failed send.
  • Result: capture confirmed; notification failure recorded. This is not a lost-enquiry case.
  • Discrepancy action: investigate the notification path separately. Do not resubmit the enquiry or create another CRM record. Verify the alert fix with a fresh, clearly marked test.

Test C: notification arrives, but destination capture is unconfirmed

  • Submission: CAPTEST-CHARLIE, submitted at 11:00 UTC.
  • Browser evidence: success message recorded.
  • Receipt evidence: acceptance reference ACK-C63, accepted for processing.
  • Destination evidence: no matching record found by 11:10 in the expected view or an authorised broader search, including existing contacts that might have been updated.
  • Notification evidence: matching alert found at 11:01.
  • Result: acceptance and notification confirmed; destination capture remains unconfirmed.
  • Discrepancy action: preserve the receipt and alert, inspect available processing evidence, and check destination configuration. Do not close the issue on the strength of the alert or immediately replay the submission.

The important feature is the evidence chain, not the checklist format. Every entry connects a unique submission to its acceptance evidence, destination outcome and next action. “Not found” includes where and when the search occurred.

5. Investigate the first unproven step

Work from the earliest reliable evidence rather than starting with whichever system staff suspect.

  1. Only browser success is available. Establish whether the receiving service has any corresponding acceptance evidence. If it does not, record acceptance as unverified. A screenshot cannot resolve that gap.
  2. Acceptance exists, but the destination record is missing. Confirm that the receipt belongs to this submission and that it refers to the intended environment. Then inspect available processing status and destination settings with an authorised operator.
  3. A record exists outside the expected view. Check workspace, filters, record type and whether an existing contact was updated. Record this as a discoverability or destination-placement issue, not automatically as capture loss.
  4. A record exists but is incomplete. Compare its fields with the synthetic submission. Preserve the mismatch and investigate where the required content stopped carrying through.
  5. The record is complete but the alert is absent. Keep capture marked as confirmed. Investigate notification evidence and mailbox handling separately.

Do not convert uncertainty into a diagnosis. If the available evidence shows acceptance but reveals nothing about subsequent processing, the accurate status is “accepted; destination unconfirmed,” not “CRM rejected it.”

A record appearing after the chosen checking target is a late observation, not proof that the original search was wrong. Update the checklist with its actual discovery time and any trustworthy creation or receipt time available. Keep the earlier finding so the delay remains visible.

6. Recover without creating a second problem

Immediate resubmission is tempting because it produces a new success message. It can also create duplicate records, repeat notifications or obscure which attempt ultimately arrived.

Before replaying an accepted submission, establish whether the original could still complete. Ask an authorised operator to examine the available evidence and decide how to handle the unresolved attempt. If a manual recovery record is necessary, document its relationship to the original submission so a later arrival can be recognised rather than mistaken for another enquiry.

For a real enquiry, preserve the content through an approved internal route while the capture issue is investigated. Record any manual entry explicitly; a manually created record does not prove that the original automated path worked. Avoid spreading customer details across screenshots, tickets and personal inboxes merely to make the investigation convenient.

After a correction, use a fresh synthetic marker. Confirm both the destination record and its required contents again. One repaired component does not establish that the entire path now works, and a successful retest does not explain what happened to the earlier attempt.

7. Close with an evidence-based result

Use outcome labels that preserve the distinction between capture and notification:

  • Capture confirmed: a matching, usable enquiry is present at the intended destination.
  • Capture incomplete: a matching record exists, but required content is missing or incorrect.
  • Destination misplaced or hidden: the record exists, but not where the agreed staff workflow expects it.
  • Capture unconfirmed: the evidence does not yet establish arrival at the destination.
  • Notification confirmed, failed or unverified: record this separately from capture.

Your next action is a bounded verification exercise: choose one live form, name its intended destination, and complete one authorised synthetic test with a unique marker. Before closing the test, record the acceptance evidence available, the matching destination record or documented search result, the required-field comparison and the notification outcome.

The measurable result is not another successful form submission. It is a submission whose journey can be reconciled—or a precisely identified evidence gap with a named investigator and an agreed next check.

Lead captureCRMContact formsReconciliation

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications