Tutoring center website: the link in the email

A parent fills in a request for an assessment, then gets an email that asks them to confirm. The link in that email often opens the center's student portal, which was built for students who already have an account. The parent never made a password, so they try the one they use for email, then a reset that goes to an address they cannot check on this device. The request looks sent on the site, so the owner counts it as a lead. The parent counts it as a dead end. The owner is already signed in, so that page never looks broken from inside.

• Does the request form ask for the grade and subject with a list a parent can pick from?
• Submit a request with a test address, then open the confirmation link in a private window. Does it need a password?
• Does the confirmation email name your center and say what the parent should do next?
• Does the thank you message say what happens next, and who will contact the parent?

A parent searching for tutoring rarely knows the exact subject name a center uses. They type 'math help' or 'year 9 algebra', and the page may list 'Mathematics, Grade 9' or a 'Level 3' taken from another system. A grade field that asks for a number with no words beside it asks the parent to translate their child's school into your categories. A parent can stop at that field before they ever reach the price.

Find this cause by typing a subject the way a parent would into the search, then reading the first field on the request form. If the form uses words the parent did not type, the cause is the vocabulary. If the form asks for a grade the parent must look up, the cause is the field. A simulated visitor makes the same request with a subject and grade worded the way a parent would, and records the field where it stopped.

The email is the step the owner cannot watch from inside. An owner who tests while signed in sees the confirmation link open straight to the next page, and it looks fine. A parent who is signed out lands somewhere else: a login, a reset page, or a message that the link has expired. The parent did not change the link. The site sent them to a page that assumes an account they do not have.

Check it in a private window with no saved logins. Submit a request with an address you control, open the email on a second device, and follow the link exactly as sent. Record the first page that asks for something the parent does not have. A simulated visitor runs the same route: the request, the inbox, then the link, and it reports the page where it stopped.

A simulated visitor can fill the request, read the confirmation in its inbox, and follow the link. If your request form does not show assessment times, the next real contact is a reply from a person at the center. The run ends at the confirmation page. It cannot tell you whether that reply arrives within a day, or whether the parent still wants the assessment when it does. Your own inbox is the only place that answer lives.

Use the test to find the break before a real parent does. Then book one real assessment yourself, with a name and an address you check, and follow the whole route once. Write down what you saw on each page, since the next change will be measured against that list. The test covers the path to the email. The rest of the relationship is yours to run.

A portal setting, a new scheduling add-on or a change to your email sender can send a parent to a login page again, while the request form still says the request was sent. Rerun the request, the inbox and the link after each change. Test with a fresh address every time, because an address that already has an account on your side can reach a different page and hide the problem.