Back to all articlesLead capture

Keep enquiry capture available while the main form is broken

Alactic Editorial10 min read

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

When a contact form stops working, replace the dead end with one authorised, checked way to make an enquiry. Tell visitors what is unavailable, what to do instead and what they can reasonably expect next. Behind that notice, give someone responsibility for recording and reconciling incoming enquiries.

Publishing an email address is only part of the job. If nobody watches the inbox, captures the visitor’s request or transfers it into the normal queue, the failure has merely moved. A useful contact form outage fallback process connects the visitor’s next step to a record, an owner and a follow-up status.

The worksheet below shows how to do that during a temporary interruption. It covers capture continuity, not the broader technical response or a promise that another channel will always remain available.

1. Establish what is actually failing

Before changing the page, distinguish a failed submission from a delayed notification. A visitor might see an error even though a record was created. Alternatively, the page might display success while nothing reaches the team. Those situations require different reconciliation work.

Use an authorised test with clearly fictional details. Check the visitor-facing result and the destination where the enquiry should appear. If there are separate notifications, check them separately rather than treating an email alert as proof of a complete record.

  • Submission fails visibly: offer the fallback beside the form and avoid encouraging repeated attempts.
  • Submission appears successful but receipt is unconfirmed: stop displaying an unsupported success claim and check for enquiries that may already be waiting elsewhere.
  • Only notification fails: consider keeping the working form while assigning someone to inspect the actual receiving queue.
  • Scope remains uncertain: describe the uncertainty without claiming that every submission failed or succeeded.

Record when the problem was first observed. Keep that separate from the last confirmed successful submission: neither timestamp proves exactly when the interruption began. The uncertainty matters when deciding which records to review later.

2. Choose a fallback by its complete path

The best temporary channel is not necessarily the one visitors use most often. Choose the authorised option that currently works from visitor access through to staff handling. A channel is not ready just because its link opens.

Check whether a visitor can send an enquiry, whether authorised staff can retrieve it, and whether the team can record and answer it. Confirm who will monitor it and how they will hand it over when their shift ends. Avoid personal accounts or newly improvised services that have not been approved for handling enquiries.

  • Shared email: useful when visitors need to explain a request in their own words. The trade-off is inconsistent detail and the risk of replies becoming scattered across inboxes.
  • Staffed telephone line: useful for conversation and clarification. It requires a manual capture script, and it is unsuitable as the sole fallback outside staffed hours.
  • Existing business messaging channel: useful if it is authorised, monitored and appropriate for the audience. Check staff access and reply arrangements before publishing it.
  • Separate temporary form: useful for structured capture, but only if it has been checked independently. Another form using the same failing dependency may reproduce the outage.

Publish one primary fallback rather than an unexplained menu. A secondary option can help visitors who cannot use the first, but each published route needs an owner. If no authorised channel has been checked, publish an honest unavailability notice rather than directing visitors into another unknown queue.

If WhatsApp is selected, recipient permission and opt-outs still matter. For the Platform, approved templates are used to initiate conversations and outside the customer-service window; a user message opens or resets that 24-hour window. Check the current WhatsApp Business Messaging Policy for precise requirements. An inbound enquiry is not blanket permission for unrelated campaigns, and template approval does not guarantee delivery.

3. Write a notice that supports a decision

The notice should answer three questions: can I use this form, how do I contact you instead, and what happens next? Place it before visitors spend time completing fields, not only after they press Submit.

Do not claim that a message was received unless receipt is confirmed. Avoid an estimated repair time unless someone has a sound basis for publishing it. A scheduled status review is different from a restoration promise.

Fictional notice for the worked example below:

Our enquiry form is temporarily unavailable. Please email enquiries@example.invalid with a short description of what you need and how you would like us to reply. Please do not include payment details or sensitive documents. Our enquiry team checks this inbox during our published service hours. If you already submitted the form and are unsure whether it reached us, mention that in your email so we can check for a duplicate.

The example address is a placeholder, not a live contact route. In a published notice, use the checked address and link to or state the actual service hours. If a response estimate is offered, distinguish an acknowledgement from a substantive answer.

Where submission is known to be broken, disable or remove the failing action rather than leaving it as the most prominent route. Keep enough context on the page for visitors to understand that the alternative is temporary.

4. Capture the minimum needed to act

A fallback record should help the next person continue the enquiry without reconstructing the conversation. It does not need to reproduce every field in the normal form.

Use a shared, authorised record with consistent fields. If a CRM is unavailable, an approved temporary register may be appropriate, provided access is restricted to the people handling the work. Do not make a public document the collection point.

  • Temporary reference: a stable identifier used during transfer and reconciliation.
  • Received time and channel: when and where the enquiry actually arrived.
  • Contact details: only what is needed for the requested reply; a name can be optional where unnecessary.
  • Request summary: the visitor’s need, not just a label such as “new lead”.
  • Reply preference and constraints: any relevant permission, opt-out or availability information the visitor provided.
  • Owner and next action: a named handler and a concrete task.
  • Status and destination reference: what has happened and where the final record lives.

For telephone enquiries, staff can ask: “What would you like help with, what is the best way to reply, and have you already sent this request through another route?” Record the answer without demanding unrelated qualification details. Do not treat permission to answer an enquiry as permission to send marketing.

5. Filled outage worksheet: a fictional worked example

All names, times, counts, references and outcomes in this worksheet are hypothetical. They illustrate a recommended operating design, not a customer result or an existing product control. The email address uses a non-live example domain.

Interruption and fallback selection

  • Business: Northline Workspace, a fictional office-furniture supplier.
  • Observed problem: at 09:10, a test submission displayed an error and no corresponding enquiry was found in the receiving queue.
  • Last confirmed successful submission: 08:40. Review interval begins there because the exact failure time is unknown.
  • Continuity owner: Maya, enquiry coordinator. Technical repair owner is tracked separately.
  • Primary fallback: existing shared inbox, enquiries@example.invalid.
  • Availability check: an authorised external test message was received, opened by the duty handler and answered successfully at 09:18.
  • Rejected option: a spare web form, because its independence from the failed submission service had not been established.
  • Handling arrangement: Maya monitors during service hours; Joel accepts the handover before Maya leaves. Unassigned messages are checked at each handover.

Visitor notice and publication

  • Notice: the wording in the previous section, with the real checked address and actual service hours substituted before publication.
  • Placement: above the unavailable form; the submission action is disabled.
  • Published: 09:25.
  • Next status review: 11:00. This is an internal review point, not a promised repair time.
  • Page check: the notice and email link are checked on a narrow screen and with keyboard navigation.

Manual capture example

  • Temporary reference: TEMP-014.
  • Received: 10:06 through the shared inbox.
  • Contact: Ellis, replying from the originating email address; no additional telephone number requested.
  • Request: asks whether a desk range can be supplied for a planned office move.
  • Reply preference: email; visitor states that a form submission may also have been attempted.
  • Owner: Joel.
  • Next action: check for the earlier submission, then ask for the product requirements needed to answer.
  • Initial status: captured; duplicate check pending.
  • Final destination: ENQ-208, with TEMP-014 retained as the transfer reference.
  • Reconciliation result: an earlier form record was found. The email was linked to that enquiry rather than counted as a separate request; Joel remained responsible for the reply.

Restoration and reconciliation record

  • Repair reported: 13:20; fallback remains published pending checks.
  • Checks completed: valid submission reached the intended queue, invalid input produced an understandable error, and the assigned handler could retrieve the test record.
  • Normal path restored: 13:45 after checks; temporary test records marked for removal under the normal housekeeping process.
  • Fallback total: 12 received items, representing 10 distinct enquiries and 2 repeat contacts.
  • Disposition: 8 distinct enquiries became new normal records; 2 were linked to existing form records. Both repeat contacts were linked to their matching enquiry.
  • Outstanding replies: 3 distinct enquiries remained open with named owners and next actions.
  • Closure check: every received item had a recorded destination; none remained only in the temporary register.

6. Keep the fallback from becoming a second outage

During the interruption, monitor both channel health and handling progress. A working inbox with no available handler is a capacity problem, even if message receipt still works.

Use distinct statuses such as captured, assigned, awaiting information and transferred. “Seen” is not a useful substitute for a next action. If a handler cannot continue, transfer ownership explicitly rather than assuming that another person will notice.

If the fallback fails, test another authorised route before replacing the notice. Keep the original records available to authorised handlers; changing channels must not strand earlier enquiries. If no route works, state that enquiries cannot currently be submitted through the listed channels. Do not leave a failed address or link presented as a functioning alternative.

Watch for duplicates without silencing genuine new requests. A matching email address alone is not enough to merge records: compare the request, timing and conversation context. Preserve separate enquiries when the same person is asking about different matters.

7. Restore the form only after checking the whole journey

A repaired page is not necessarily a repaired capture path. Before removing the notice, verify a valid submission through to staff retrieval and assignment. Check that success wording reflects the actual result and that an invalid submission gives visitors a useful way to correct it.

For any repaired or temporary form, labels should identify controls and be programmatically associated with them, as explained in the W3C guidance on form labels. A fallback should not create a new obstacle for visitors who rely on assistive technology.

Check any routing or notification steps the team depends on, not just the first destination. Keep test entries distinguishable from real enquiries. Record the restoration time, then remove or revise temporary notices wherever they were published.

Continue watching the fallback for messages sent during the changeover. Visitors may have kept an earlier page open or saved the temporary contact details. Stop advertising the temporary route when appropriate, but do not abandon messages already arriving there.

8. Reconcile received items before closing the interruption

Restoring the form and clearing the fallback backlog are separate milestones. Reconciliation is complete when each fallback item has an accountable destination, not when every sales or service conversation has finished.

  1. Review fallback records and the normal queue across the uncertain interruption interval.
  2. Compare potential duplicates using request details, not contact identity alone.
  3. Create or link the normal record, retaining the temporary reference.
  4. Carry forward the original received time, relevant reply constraints and conversation context.
  5. Verify the destination record before marking the temporary entry transferred.
  6. Assign every unresolved enquiry an owner and next action.

Keep received-item totals separate from distinct-enquiry totals. Count differences are explainable when repeat messages and links to existing records are documented. Unexplained differences need investigation, not an adjusted total to make the worksheet balance.

For the next interruption, prepare one blank worksheet and nominate a continuity owner. The measurable readiness check is simple: that person can identify a checked authorised fallback, publish an approved notice and trace a fictional test enquiry from receipt to an owned record. That is a more useful preparation than keeping an alternative contact link with nobody responsible for what arrives.

Lead captureForm outagesEnquiry managementOperational continuity

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