I have a problem of the need to ensure that a user doesn't miss a webpage crucial for what I assume as a constructive usage of another web page.
Personal example of this problem
My website contains a
pricelist webpage and a
contact webpage containing a simple contact form, which contains the following mandatory fields:
- Type of service in which the inquirer is interested (selected from a selection list of up to five options)
Possible solutions for this problem
1. Noting that prices are available in pricelist before each form submission
This is the simplest solution I know of and took it so far:
Each selection option in the select list of my contact form contains a parenthesis note according to which price is available in price list:
VARIABLE message = "price is available in price list"
Per variable call in each job description line:
- Job 1 (price is available in price list)
- Job 2 (price is available in price list)
- Job 3 (price is available in price list)
- Job 4 (price is available in price list)
- Job 5 (price is available in price list)
The main problem with this approach is that it might feel absurd to a customer although I personally assume a customer who really needs some proposed job wouldn't care from it much and would inquire anyway but I have no objective evidence for this assumption
2. Uniting two webpages
Similar to what I understood from Stephen Ostermiller's comments, this is problematic in this case, because, even if the contact form is under the pricelist:
- A potential customer might want to know prices without contacting → not knowing prices are in the contact webpage which may cause stress when visiting that web page.
- If a potential customer clicked on a contact and then percepted a pricelist it might confuse that potential customer
- A link such as "prices and contact is quite long and possible very not intuitive
My pricelist page contains notes about international payment options and some other notes which makes the page a bit longer than just a table of prices and is also splitted to three chapters, each one dealing with another type of service; henceforth, I consider it a crucial webpage and would like any potential customer to use it
Setphen Ostermiller commented:
Somebody could explain how to pull information from a centralized database into two different pages or say how to set up AJAX calls to get the information from one page to the other.
If this is still relevant after the massive edit of this question, I would welcome an answer further explaining what is proposed to be done --- what is proposed to be presented in two different ways for a potential customer, via two different Ajax calls, as a solution to the problem.
How to ensure a user doesn't miss a webpage crucial for constructive usage of another webpage?