Lead generation networks operating workflow principles

This lead generation networks operating workflow article sets out a design framework for exceptions at hand-offs: failed records, marketing objections, uncertain origins, unclear ownership, buyer disclosure and source changes. It is not a ready-to-run procedure: for each case, identify the condition before moving a record, keep unresolved items with the named owner, and retain the evidence behind the decision. A later complete-looking record does not erase an earlier failure or grant permission to restart processing.

If a failed queue seems ready to reopen

If a failed queue appears ready to reopen, do not replace its original record or move it forward on appearance alone. Keep it held until the owner of the failed gate grants restart authority and records a decision addressing the cause that stopped processing.

Retain the failed input, decision rule, logs, affected recipients and containment start time in that record. A clean replacement would remove evidence of how the failure arose. Privacy must clear an unlawful-purpose concern, security an unresolved incident, accessibility a blocked user path, and commercial a reconciled bill.

Only after those clearances exist should the service owner coordinate the restart. Keep the initial failure trace connected to the outcome, then report that outcome through measurement and reporting. This separates approval to resume from the later work of moving the service forward.

• Rule of thumb: Clear the cause before restarting, and preserve the original failure record.

If someone objects to direct marketing or asks for a correction

If a person objects to direct marketing, stop that activity straight away and forward the objection to the suppression owner, whether it arrived in speech or writing and whichever team received it first. Do not leave the instruction with its initial recipient for action.

Follow the ICO Article 21 objection guidance, and send each complaint or correction request to the investigation and suppression owners. Keep such cases out of an unassigned general queue, and connect the handling to the data protection record so it has an accountable destination.

Deletion does not follow automatically from an objection. Retain only enough information to honour the preference against future direct marketing, and keep the suppression record after the contract ends. The investigation and suppression owners should receive complaints and correction requests instead of leaving them in an ordinary queue.

• Rule of thumb: Route objections immediately to suppression, not to an unassigned queue.

If a service request is being treated as marketing permission

If contact began with a service request, limit it to the requested work and its approved route. Completing that work does not grant general permission to promote. Assess each later promotional route separately, recording the intended recipient and the point where the information was collected.

For electronic mail, consent must identify one type of message under PECR regulation 22. Record the message type, source and notice version as evidence. Associate each transfer with the relevant disclosure policy, rather than assuming the earlier service request covers it.

• Rule of thumb: A service request authorises only its stated service route.

If a record has uncertain origins or fails an intake test

If a record has no traceable origin or fails an intake check, stop it before routing and assign a named outcome. Put an unknown source in a restricted queue rather than guessing its origin. An operations lead may release such a record only after privacy approval has been recorded.

At intake, capture an event ID, time and notice version. Check service type, geography, minimum contact data, duplicate criteria and age criteria; use a stored rule version to assign pass, fail or manual review. Do not infer an answer that is missing from the record.

Set responsibilities using the quality checklist and service standards. Keep the rule version with the decision so staff can identify which test was applied. Missing evidence remains restricted until an authorised person records the required decision and any permitted next action.

• Rule of thumb: Keep gaps in evidence in a restricted queue; never fill them by inference.

If the next gate has no clear owner

If staff cannot identify who owns the next gate, rebuild the route register with eight stages. Assign each stage one accountable owner and one recorded failure condition. Use the register to create local transition cards, rather than treating it as an unchangeable standard for every service.

For every stage, create a transition card naming its owner, allowed inputs, output, evidence event, failure queue, timing source, stop condition, recovery action and restart authority. Give each card one named owner, with responsibilities allocated through team roles.

For every contractual clock, specify its start, pause, stop, exclusions and time zone. Leave a target blank unless an approved source supports it. These details prevent staff from guessing how a clock applies to a stage or when work may resume after a pause.

• Rule of thumb: Assign each stage one owner and one explicit failure condition.

If an enquiry is about to be disclosed to a buyer

If an enquiry is next in line for a buyer, allow the transfer only after its origin and every required check have been verified. Collection must not connect straight to buyer disclosure. Keep a failed or uncertain record in a restricted queue until an authorised restart owner records a decision.

Before any transfer, check the applicable transition card and its stop condition. Capture exactly what reached the buyer and when, rather than relying on a later reconstruction from the current configuration. This leaves the evidence for the hand-off attached to the event being reviewed.

• Rule of thumb: Do not disclose an enquiry until its origin and required checks are verified.

If a source, route or agreement has changed

If a source, recipient, field, channel, complaint pattern or contract changes, review the operating rules and preserve the version that came before. Keep the version history with the events it governed so an auditor can identify which controls applied at each point.

Record precisely what the buyer received and when. Reconstructing past events from the present configuration cannot show which version applied at the time. Preserve the event evidence alongside the changed rules so the earlier and later routes remain distinguishable.

Before a marketing call, screen live-call numbers against the TPS and CTPS registers unless consent exists. Record the retention, deletion or exit decision. At contract end, send an export mismatch or live complaint to the records owner, and keep the suppression record beyond the contract end. Wider duties beyond UK GDPR Article 21 and PECR regulation 22 are mapped in the UK regulations.

• Rule of thumb: Preserve the rules and evidence that applied when each event occurred.