Before the first field
Imagine a small business owner who has read a service page and selected "Ask about a project." On the next screen, the heading says "Contact." A short sentence explaining that the form is for project inquiries would help confirm that the visitor has reached the intended place.
The visitor should also understand what to prepare. If the business wants a website address or a description of the work, say so near the relevant field. An introductory paragraph does not need to repeat the entire service page; its job is to make the immediate task clear.
While completing the form
Review the fields in the order they appear. An early request for a detailed project description may feel different from a short sequence that first establishes basic context. The appropriate order depends on the inquiry, so a review should explain its reasoning rather than prescribe the same form for every business.
On a smaller screen, inspect whether labels remain visible and instructions stay close to the fields they explain. Check the space around controls and the amount of text visible at once. A layout can appear tidy in a desktop screenshot while making the phone experience harder to follow.
At the point of sending
The button should describe the action in language that fits the page. Any nearby explanation of what happens next should reflect the business's actual process. Avoid promising a reply time unless the business has agreed to it.
This example is an interface review, not a report from user testing. The same observations would need to be made against the actual form and agreed customer task before becoming recommendations for a particular website.