Preserve enquiry context when visitors move between pages
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A visitor selects an enquiry link on a product page, then submits through a general contact form. If the receiving team gets only a name, email address and a request for details, someone must ask which product they meant. Silently attaching an earlier product can be equally unhelpful: the visitor may have changed their mind.
The solution is a visible, editable enquiry topic, supported by clear rules about replacement and expiry. Define those rules before deciding how to build the form. The specification below shows what to carry, what to discard and how to preserve a draft without treating an old selection as a current decision.
1. Separate background from the visitor’s current subject
Three fields answer different questions:
- Entry page: Where the enquiry journey began. It provides background, not proof of current interest.
- Selected item: The product or offer the visitor deliberately chose to ask about.
- Visible topic: The subject the form currently presents for review and submission.
The selected item and visible topic must agree when submitted. The entry page may differ: someone might start with a compact machine and eventually ask about a larger model.
Give explicit choices priority over browsing. A product-specific enquiry action or a topic change inside the form establishes a selection; simply viewing another page does not. A visitor who reaches contact without selecting a topic should start with a neutral general enquiry, not an invisible guess based on their browsing.
Choose how background behaves when product context is removed. This article’s specification omits the entry page from general-enquiry submissions. That sacrifices some potentially useful background, but prevents an old product page from steering staff toward a subject the visitor has deliberately cleared.
2. Carry only information that helps someone answer
A useful context bundle contains the current topic, a readable item name, a stable item reference and any deliberately selected option that changes the request. A product enquiry can also include its entry page as clearly labelled historical background.
Names help people read the request; references distinguish similarly named items. Neither establishes that an offer is still available or that the supplied information is valid. If an item cannot be recognised at submission, ask for review rather than substituting a plausible alternative.
Avoid attaching complete navigation histories, unrelated URL parameters or whole page contents. They increase noise without necessarily clarifying the question. Keep message text separate from the topic: visitors should be able to write naturally or delete prefilled wording without accidentally removing the enquiry’s subject.
The following artifact is an operating specification, not a claim that a particular product already implements these controls. If using Alactic, check the relevant workspace and current plan for availability before choosing an implementation.
3. Reusable filled specification: a hypothetical equipment enquiry
Fictional worked example: All products, paths, references and timing choices below are hypothetical. They describe a recommended design, not Alactic customer results or existing product capabilities. Copy the field structure and replace the example values for your own journey.
Purpose, fields and ownership
- Purpose: Let visitors ask about equipment through a shared contact form without retyping its identity.
- Rule owner: Enquiry operations lead; form maintainer implements and tests the approved behaviour.
- Entry page: Compact floor scrubber,
/products/compact-floor-scrubber. Keep this origin unchanged within the draft’s journey. - Selected item: Compact floor scrubber, reference
SCR-COMPACT, established by the product-specific enquiry action. - Selected option: Battery-powered configuration, included only after deliberate selection and only while valid for the chosen item.
- Visible topic: Product enquiry — Compact floor scrubber. Display the selected option separately.
- Visitor controls: Change product; Make this a general enquiry. Preserve contact details and message text through either change.
- Product submission: Current topic, item name, item reference, valid selected option and entry-page title and path. Label the entry page as historical background, not the selected topic.
- General submission: General enquiry and the visitor’s details and message. Omit item fields, options and entry page.
Selection and navigation rules
- General contact or supporting-page navigation: Retain the current selection, subject to freshness review.
- Viewing another product: Do not replace the topic.
- Another product’s enquiry action: Replace the selected item, clear previous item options and update the visible summary. Preserve the message with a reminder to review references to the former item.
- General enquiry selected: Clear item and option fields. Exclude the entry page from the eventual submission, even if retained temporarily within the draft.
- Separate tabs: Each open form keeps its own visible selection. Another tab must not silently overwrite it.
- Unavailable item: Mark the selection as requiring review. Offer a new item or general enquiry, preserving the message. Do not silently clear the selection and submit.
Freshness, activity and precedence
- Hypothetical boundary: Require topic review after 30 minutes without qualifying activity, or on the next calendar day in the configured site time zone, whichever comes first.
- Qualifying activity: Deliberate changes to form fields or deliberate topic actions in that draft. Passive viewing, pointer movement, background refreshes and activity in another tab do not count.
- Expiry check: Check before applying a new interaction and again before submission. Typing after expiry must not silently make an old topic current.
- Review requirement: Keep the message and display the previous topic as unconfirmed. Require an explicit decision to keep it, choose another item or select general enquiry. Editing contact details or message text does not satisfy this review.
- Restored draft: Preserve its message and previous topic, but require topic review whenever a saved draft is restored, regardless of age.
- Already-open draft: Preserve its contents across inactivity or an overnight boundary, but require review before submitting. Do not reset it to general enquiry merely because the date changed.
- Genuinely new enquiry: With no draft being resumed, start neutral unless the visitor makes a new explicit product selection.
- Precedence: A fresh explicit choice resolves topic review. Otherwise, an existing or restored draft takes the preservation-and-review route; only a genuinely new enquiry takes the neutral-start route. An unavailable item cannot be reconfirmed as valid without resolving its availability.
This policy distinguishes preserving work from trusting context. A draft can retain every word while its topic remains unconfirmed. The hypothetical timing threshold should be tested against actual enquiry patterns rather than treated as a universal standard.
4. Work through a change of mind and an overnight return
Hypothetical walkthrough: A visitor begins on the compact scrubber page, selects the battery configuration and starts an enquiry. They write a question about doorway clearance, then browse a ride-on model. Browsing alone leaves the compact model selected.
The visitor then activates the ride-on model’s enquiry action. The form changes its topic to Ride-on scrubber, removes the compact model’s battery option and retains the written question. A reminder asks the visitor to check that their message still fits the new topic.
They leave the form open overnight. On returning, their message is intact, but the topic needs review because the calendar-day boundary has passed. Typing another sentence does not dismiss that requirement. They explicitly keep the ride-on topic and submit.
The resulting hypothetical handoff contains:
- Topic: Product enquiry — Ride-on scrubber.
- Item reference:
SCR-RIDEON. - Selected option: None.
- Message: The visitor’s retained and reviewed doorway-clearance question.
- Historical entry page — not selected topic: Compact floor scrubber,
/products/compact-floor-scrubber.
If the visitor instead chooses general enquiry, the handoff omits both product references and the entry page. The message remains unchanged unless the visitor edits it. This makes the removal meaningful rather than merely changing a heading while sending the old context underneath.
5. Handle incompatible options and back-button restoration
Dependent options need their own checks. An option belonging to the compact model must not survive a switch to the ride-on model merely because both have similarly named configurations. Clear incompatible options and let the visitor choose again. If an option becomes unavailable without an item change, explain what needs review rather than silently mapping it to another configuration.
Back navigation introduces a different failure: a browser may display an older version of the form. Returning to that view must not resurrect a topic the visitor already replaced. Reconcile the displayed summary with the current draft before allowing submission; if reconciliation is uncertain, request review while preserving the message.
Test both the restored display and the final handoff. A correct-looking summary is not enough if an older hidden value still determines the submitted subject.
6. Make topic review understandable and testable
Show the topic near the beginning of the form and, for longer forms, near submission. Distinguish a confirmed topic from a question asking whether an old selection still applies. Corrections should not erase unrelated fields or restart the form.
Give editable topic controls meaningful, programmatically associated labels. W3C WAI’s form-label guidance explains this association; a nearby heading is not a substitute for labelling the control itself.
Hypothetical acceptance checklist: For each case, compare what the visitor sees with the actual test submission.
- Product, then contact: A selected product remains visible after visiting a service page and opening contact.
- Browsing only: Viewing product pages without an enquiry selection produces no confirmed product topic.
- Replacement: A new product-specific enquiry action replaces the item and removes incompatible options.
- General override: Selecting general enquiry preserves the message and omits the former item, options and entry page from the payload and staff notification.
- Idle return: After the hypothetical inactivity boundary, typing in the message does not bypass topic review.
- Open overnight: A form crossing the configured date boundary retains its contents but requires explicit topic review.
- Restored old draft: Restoring a prior-day draft preserves its message and presents the old topic as unconfirmed, rather than silently confirming it or replacing it with general enquiry.
- New enquiry: A genuinely new visit without a selection or restored draft starts neutral.
- Unavailable item: Choosing general enquiry during recovery removes the unavailable item and historical entry page from submission.
- Tabs and back navigation: Neither another tab nor an older browser view silently changes the final subject.
- Recoverable submission error: Details, message and topic remain available for correction and retry.
Errors should identify the problem and a recovery action. W3C WAI’s validation guidance also distinguishes browser checks from necessary server-side validation. Validate submitted item and option values rather than trusting the visible summary alone.
7. Check the receiving team’s view and review outcomes
Lead the handoff with the final topic and message. For product enquiries, put any entry page below them with the explicit historical-background label. For general enquiries, omit it throughout the handoff, including notifications and the enquiry record. Removing it in only one destination leaves the same bias elsewhere.
Start with one product-to-contact journey. Assign an owner to approve the specification and record whether each acceptance case preserves work, permits correction and sends the final visible choice. Treat silent mismatches as defects, not harmless differences between screens.
After launch, examine enquiries where staff had to ask which product was intended or responded about a removed selection. Distinguish missing context from genuinely general questions. Those observations indicate whether to improve the selection controls, review wording or freshness boundary. The useful outcome is an accurate, minimal account of the visitor’s current request—not more background attached to every submission.
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