In plain English
After a website enquiry, the business should save a stable record, send an honest acknowledgement, assign a named owner and make the next action visible. The owner should review fit, respond with useful context and record the outcome. Consent, source data, duplicate handling, backup escalation and manual recovery should remain attached to the process.
What should the website confirm immediately?
The website should confirm that the enquiry was received only after the server or lead system accepts it. Show a clear success state and a stable reference when available. The message should explain that a person will review the context and avoid implying that a booking, price, eligibility or result has already been approved. Failed submissions need an accessible error and a safe retry path.
An email acknowledgement can repeat the reference, the information received and the expected next step without exposing sensitive details. It is not a substitute for a real response. Keep templates approved and versioned, and make delivery failure visible to the team. If the automated message fails, the saved lead and manual follow-up route should still remain available.
Who should own the first useful response?
Assign the enquiry to a named person or role using the minimum reliable routing inputs, such as service, location or existing relationship. Display the owner and due action in the working system. Shared inboxes can support visibility, but they should not hide accountability. Define a backup for absence, overload, invalid contact details and uncertain routing.
A useful first response confirms the service context, asks only necessary follow-up questions and states the next step. It should match staffed hours and the complexity of the request. Sensitive advice, suitability, pricing and consequential decisions remain with an authorised person. Automation may prepare context or reminders, but the customer should not be misled about who made the decision.
How should source and consent travel with the lead?
Preserve the submitted privacy acknowledgement, optional marketing choice, source page, campaign fields and time of submission with the lead record. A request for a service response does not automatically create permission for unrelated promotional messages. The Information Regulator's direct-marketing guidance should be reviewed with qualified advice when designing electronic marketing and consent operations in South Africa.
Use campaign parameters consistently when they are appropriate, and keep unknown values as unknown. Google Analytics documents how custom campaign parameters identify referring campaigns. Those parameters are reporting inputs, not proof that one touchpoint caused a later sale. Restrict access to personal data, define retention and ensure any external processor is covered by the business's approved privacy arrangements.
Sources for this section: Guidance notes, Collect campaign data with custom URLs.
Which outcomes should close the enquiry loop?
Record whether the enquiry was contacted, suitable, quoted, won, lost, duplicated, spam or still unresolved. Use definitions the team can apply consistently and allow a note for the reason. An overdue or unassigned record is an operational exception that needs an owner, not a reporting inconvenience to hide. Review exceptions alongside response and qualification patterns.
Where the business has the required consent, controls and technical capability, later outcomes may be connected back to advertising systems. Google documents offline conversion imports for actions that happen after a click or call. Internal truth comes first: the lead record, qualification and confirmed sale should be accurate before any platform import is expected to improve reporting or optimisation.
Sources for this section: About offline conversion imports.
Official references
- Guidance notes (Information Regulator South Africa)
- Collect campaign data with custom URLs (Google Analytics Help)
- About offline conversion imports (Google Ads Help)