List repeat tasks
Identify what existing customers come back to do. Distinguish a simple request from a task that genuinely needs authentication or private information.
For an Enfield Town business, returning customers often need a different route from first-time visitors. We help the website support repeat bookings, service requests or account questions without hiding the introduction for new customers.


Photo: Christine Matthews
St Andrew's Parish Church, Enfield - geograph.org.uk - 187730.jpg (Source) · CC BY-SA 2.0
Reduced-resolution copy; cropped to fit the card. Available under the stated licence.
These are the questions we would work through for this Enfield Town brief. The final scope depends on your current site and how the business operates.
Identify what existing customers come back to do. Distinguish a simple request from a task that genuinely needs authentication or private information.
Use labels customers understand, such as request support or book again. Keep the new-customer explanation available without forcing returning visitors through it.
Agree who handles repeat requests and what context they need. Avoid treating a known customer as a new sales lead by default.
Enfield Town is a specific centre within the borough of Enfield. A business serving it should keep its premises and coverage clear while recognising that not every visitor is new. We can separate introductory service information from the practical tasks existing customers return to complete. That may mean clearer navigation or a focused request form; it does not automatically require a customer account system with passwords and private records.
Our RJ Health Solution case study describes an authenticated ordering portal. It provides an example of when accounts and permissions form part of a real operational requirement, not an Enfield Town customer claim.
A returning customer may only need a clear reorder or support route on a WordPress website. Compare that simpler option with a portal before taking on extra maintenance, account recovery and data responsibilities.
Bring the three most common returning-customer tasks and show how they are handled today. Include any information staff need to recognise the customer securely.
Test the site as a new visitor and as a returning customer. Each should find an appropriate route without being forced into the other's journey.
A few details worth settling before design or development begins.
Only if there is a useful private task to perform. A clear contact or booking route may be enough and avoids unnecessary account-management work.
That needs careful scoping around identity, permissions and data handling. We would not expose private records through a public page simply for convenience.
Use the short form below, email or WhatsApp to describe the work. We review the brief remotely and agree deliverables, responsibilities and costs before starting. Any third-party subscriptions or ongoing support need to be included in that discussion.