Collect product inquiries and read your inbox
Connect a product to a native inquiry form and review the visitor's message, contact details and selected options in your site inbox.
An inquiry keeps a visitor's question with the product and options they were viewing. Visitors submit through your published form. You review the saved message in the site's inbox and decide how to respond.
This workflow does not place an order, reserve stock or send an automatic notification email. Plan to check your inbox regularly.
Before starting, prepare a product, a short list of information you need from visitors, and an appropriate notice explaining how your business will use that information. You need permission to edit and publish the product and form page and to read submissions.
Connect or create an inquiry page
Open the product's Inquiries section. Under Product inquiries, the Inquiry form list shows suitable published forms in the same site and language.
Choose an existing form, or enter a New inquiry page path, such as /product-inquiry, and select Create inquiry page draft. Save the product to keep the connection. A new draft is not yet ready for visitors.
Choose Edit inquiry page. The new page uses three editable blocks: PageHeader, InquiryProductSummary, and CustomerForm. Review the heading, form fields, information-use notice and submit action. Keep the fields limited to what you need to answer the inquiry. Make sure the form is enabled for product inquiries.
The default fields include an optional name, an email address and a question. Adjust them to fit your business and review any required acknowledgement deliberately. Use a plain field label such as “Name”; the form supplies its own required or optional indicator. A visitor's form acknowledgement is separate from the merchant's LitPage account terms.
Publish the inquiry page. Return to the product and select Refresh inquiry pages. Wait for Ready — form published, then save and publish the product. You can reuse a suitable form for several products; each inquiry carries the selected product's context.
Submit a test inquiry
Open the live product outside the editor and select a valid option combination. Follow its inquiry action. The form should show the intended product and selection, with a link back to the product.
First submit the empty form to check required-field and acknowledgement messages, and confirm that focus moves to the field needing attention. Then use fictional details for the test, such as the name “Demo reader” and [email protected]. Write a question that helps you identify this test later. Do not use a real customer's information for testing or documentation images.
Submit once and wait for the confirmed success message. Only a confirmed server response means the inquiry was received. If a network request fails, review the retained input and retry deliberately rather than assuming the first click succeeded.
The inquiry carries the selected product and options into the form. The contact details and question shown here are fictional.
Review the message
Return to your site in Builder and open Form submissions. Open the test record and check the contact details, question and product-option snapshot.
The snapshot records the inquiry context at submission time. Later changes to the product do not rewrite that historical record. A previously selected option can therefore differ from the product's current configuration without the inquiry being wrong.
Copy email copies the address to your clipboard. It does not send a message or change the record. Record details contains technical identifiers useful for support; keep that area out of public screenshots.
The inbox keeps the product selection with the submitted message. This record contains demonstration data only.
These screenshots show a fictional English inquiry captured in v0.7.8. The version text and inbox count belong to that example.
Check each published language
Connect the product to an inquiry page in the same language. Translate the page heading, product and option names, form labels, information-use notice, button and success message. These are authored content; creating a second language does not translate them for you.
Test English and Simplified Chinese pages independently, starting from each actual public product URL. Check the selected-product summary, required and optional indicators, validation messages, success message and link back to the product. In Form submissions, confirm that the saved question and selected-option labels match that language.
Resolve common setup problems
- Not connected: select an inquiry form or create and publish one.
- Draft needs publishing or Selected form is not ready: save the product connection, open the inquiry page, check the language and form settings, publish it, then refresh the product's inquiry list.
- Inquiry form status unavailable: retry Refresh inquiry pages after the connection is available. Do not treat an unchecked form as ready.
- A direct form link asks for product context: return to the product and use its inquiry action. Do not manually construct a contextual URL.
- No email notification arrived: check Form submissions; automatic notification emails are not part of this workflow.
Promote the normal product URL. A product-context inquiry page is not a long-term SEO landing page: it is kept out of the sitemap and is marked not to be indexed. Use collections and guides to help visitors discover products, then let the product action take them to the form.