A client submits a link to the company homepage when the team needs the exact page to update. The URL works. The request still needs another email before anyone can begin.
For WordPress form reference links, check address format, page relevance and access separately. Ask what each link is for, preserve the exact URL, and give staff enough context to decide whether it is the reference they need.
Ask for the page and its purpose
Label the field for the task. Page to update is more useful than Website when the team needs a particular page. Add a short instruction such as Paste the full link to the page you want changed.
Keep the visitor’s explanation beside the link. Ask What should we look at on this page? when that answer changes the review. For a design reference, ask which detail matters instead of assuming the whole site is an example to copy.
Start with one URL field and one short purpose field. If a request needs several references, give each link its own purpose. Your builder’s supported repeatable fields, separate named fields or an explicitly formatted message can work. Choose the simplest format staff can read.
- Page to change: the exact page the request concerns.
- Reference page: an example, with the relevant detail explained.
- Supporting document: what it explains and who can access it.
Separate URL format from usable access
Use your form builder’s URL field when it fits the input. Gravity Forms documents its URL validation; Contact Form 7 documents URL fields. Those checks help with the address format. They do not establish that a page is the right reference or that staff can access it.
A well-formed link may lead to a login page, a removed document or the wrong project. During first review, the person handling the request should check the destination, relevance and access before assigning dependent work. Do not ask visitors to paste passwords or access tokens into a form.
Provide a route for a private document when the business actually needs one, such as its existing approved sharing process. If access is unavailable, ask for a non-sensitive description that lets staff understand the request while access is arranged.
Preserve the exact submitted reference
Keep the original URL and the visitor’s description in the request record. Query parameters can identify an item or contain tracking details. Preserve the submitted address, then let staff decide whether any parameters can safely be removed from a working copy.
If staff later receive a corrected link, record which reference it replaces and what work the correction affects. The original submission remains useful context. A working brief should point clearly to the reference staff should use now.
Treat a submitted destination as a reference to check, even when it appears to belong to your organization. Follow the business’s ordinary safe-link procedure. A visitor’s label alone is not proof that a destination belongs to the named organization. The review brief guide explains how to separate submitted facts from staff interpretation.
Keep AI summaries honest about links
The Entry Summary action prepares a readable review aid from submitted information. If the visitor provides a URL and a description, a summary can identify that stated reference. Do not treat that as proof that the linked page was opened or its contents checked.
For example, a brief can say Visitor supplied a reference page and wants a similar navigation layout. It should not claim that the page has a particular menu unless that fact comes from information actually available to the review.
The Missing Information Review action can propose staff follow-up questions for unclear submitted information. Review the question before sending it. Neither action should be presented here as a website crawler or an automatic link-access test.
Sentient Forms supports Gravity Forms, Contact Form 7, WPForms, and Elementor Pro Forms. For after-submission review with Contact Form 7, WPForms, and Elementor Pro Forms, enable the Sentient Forms Submission Ledger. Native entry features vary by builder. Check the current plugin listing when choosing where staff will review results.
Test the references staff receive
Use fictional requests to test an exact page, a homepage instead of a page, a broken link and a private document. Include two links with different purposes. Check the saved request, any summary and the staff working record.
Staff should be able to identify the original reference, why it was supplied and what still needs checking. If a brief invents page contents or drops a link’s purpose, revise the review instructions and retest.
Choose and record a comparison window that fits the site’s request volume. Count requests that needed another message because the reference was unusable or unclear. Compare the same form and request type before and after a field change. Fewer submitted URLs alone do not show that intake improved.
Frequently asked questions
No. URL format, destination relevance and access are separate checks. A valid address can still lead to a private document or the wrong page.
Do not assume it does. A summary of submitted information is not proof that the linked page was fetched or checked. Staff should verify the reference through their normal process.
Ask for a link when it helps staff act on that request. Use a task-specific label and ask why the reference matters. Keep unrelated link fields optional or remove them.
Start with one form that receives unclear reference links. Improve the field label, submit a fictional example and check whether the review aid preserves the link and its purpose. Compare Sentient Forms review actions.
