Define the timing promise
Write down which event starts the clock and which event ends it. Submission-to-delivery and delivery-to-response are different intervals. A useful service agreement states the expected timing, operating hours and exception handling.
Map the fields before delivery
List each field, its meaning, whether it is required and how it appears in the receiving system. Agree date formats, time zones and country labels. Run a controlled example through the proposed handover before accepting a large volume.
Assign ownership
Name the team or role responsible for the next step. Decide how enquiries are routed when someone is unavailable, and what happens outside staffed hours. A delivery confirmation should not be mistaken for a completed sales response.
Design for failed handovers
Agree how delivery failures are recorded and retried. A retry should preserve the enquiry reference so it does not create a duplicate. If a file is used, define the naming convention and how the receiver confirms it has been processed.
Review the workflow with evidence
Inspect delay, failed delivery, duplicate and acceptance counts. Combine those with the receiving team’s follow-up results. Change the part of the process that the evidence identifies rather than assuming every problem comes from lead volume.
Turn the checklist into a brief
Use the campaign builder to choose the category, market, quantity and fields. Add the relevant delivery or qualification requirements from this guide, then review the result before emailing it.