1. Application and service status
This candidate schedule is for expressly agreed lead-related services. Availability and launch readiness must be confirmed; the website’s planning-stage lead-qualification offering is not an active promise. Specify whether the work concerns intake design, qualification rules, routing, reporting, campaign-origin inquiries or another defined activity.
“Lead” means an inquiry record matching the source and minimum information defined in the SOW. “Qualified Lead” means a record meeting the agreed criteria, not a guaranteed customer. “Conversion” means the expressly selected outcome, such as an attended estimate or accepted job; it must not be confused with a form submission.
2. Criteria and operating rules
Record approved service areas, accepted job types, capacity, exclusions, required fields, operating hours and escalation destinations. Client approves these rules and updates DealDot when operations change. A location match does not confirm job suitability, technical condition, financing eligibility or Client availability.
If Client wants purchased leads, exclusivity, replacement credits or performance pricing, the source, legal permissions and specific commercial terms must be separately accepted. None is established by this schedule. DealDot does not claim that every visitor or inquiry is genuine, reachable or ready to buy.
3. Intake and routing
The agreed work may include form planning, guided questions, service-area checks, destination mapping and a documented follow-up process. Identify each integration, destination, account owner, test case and fallback. Route only the information necessary for the stated purpose.
A successful form submission is distinct from email delivery, CRM receipt, a scheduled appointment and a sold job. Define failure detection and any included monitoring. Provider outages, spam filters, mistaken contact details or unsupported integrations can prevent a handoff. No guaranteed response time is imposed without an accepted commitment.
4. Human review and follow-up
Client handles estimates, site inspections, job acceptance, pricing, scheduling and customer service unless a separate authorized service says otherwise. Client assigns a person to review and respond to inquiries and records outcomes where reporting depends on them.
Automated classification can assist sorting but does not make a trade-safety judgment. Emergency information should use an approved, clearly disclosed route; an inquiry system is not emergency dispatch. Do not let an intake system promise a visit, scope or price beyond Client-approved authority.
5. Consent and communications
Before calls, texts, email campaigns, recording or automated outreach, identify the applicable channel permissions, lawful basis, disclosures, recipient choices and required opt-out handling. Supplying a business inquiry is not blanket consent for unrelated outreach. Client and DealDot must allocate responsibility for compliance and maintain required evidence.
This schedule does not include unsolicited messaging, purchased lists, call recording or automatic telemarketing authorization by implication. Any such feature requires a separately defined lawful scope and review of applicable provider terms and law.
6. Data quality, duplicates and measurement
Define duplicate treatment, incomplete or out-of-area records, spam, attribution windows, dispute evidence and any agreed validation procedure. If a replacement or credit rule is desired, record $LEAD_VALIDATION_RULES and $CREDIT_RULES before work begins. No default refund, replacement quota or guaranteed exclusivity is supplied.
Reporting should distinguish inquiries, qualified records, booked appointments and completed jobs. Sources may disagree and Client’s outcome reporting may be incomplete. Do not present estimated attribution as verified revenue. Lead handling can support growth but cannot guarantee customer decisions or business performance.
7. Data and access
Agree roles, data fields, recipients, access controls, retention, export and deletion instructions, using the data-processing addendum where needed. Client approves the privacy information on its own intake pages. Do not collect sensitive records unnecessary for the job inquiry.
Credentials and private customer records use an agreed secure channel. Provider usage, storage locations and training practices must be verified for the actual implementation. No client lead data is authorized for unrelated reuse merely because DealDot operates the workflow.
8. Fees, dependencies and termination
Set $PROJECT_SCOPE, $DELIVERABLES, $PRICE, $PAYMENT_SCHEDULE, $SERVICE_TERM and any $DATE. External platform fees, campaign spend and staff follow-up are separate unless expressly included. Changes to sources, criteria, integrations or capacity may change scope.
On termination, agree the routing shutdown or handover, ownership and permitted use of records, available export, retention and provider cancellations. Do not leave forms pointing to unmonitored destinations. Future leads, past conversion and uninterrupted routing are not guaranteed after service ends; transition assistance requires accepted scope.