Lead Packet Template

This packet prepares a lead-routing handoff. It does not prove that a CRM record was created, updated, messaged, or confirmed.

Packet summary

Use this template to prepare a clean lead-routing packet before an approved handoff step. The packet is a preparation artifact only. It does not execute a webhook, submit a form, create a CRM record, send a message, schedule an appointment, or confirm customer contact.

Required fields

packet_id
created_at
source_system
source_url
shopper_name
contact
lead_context
routing
consent_or_contact_note
validation_status
downstream_status

Optional fields

Optional context fields include:

selected_unit
inventory_url
store_or_location_preference
utm_content
utm_term
Any blank contact value that was not supplied by the shopper

Do not invent optional values. Use empty strings when a value is not supplied.

Missing field checklist

Before marking a packet ready_for_handoff, check:

Packet ID is present.
Created timestamp is present.
Source system is present.
Source URL is present.
Shopper name field is present.
Contact object is present.
Lead context object is present.
Routing object is present.
Consent or contact note is present.
Validation status is present.
Downstream status is present.

Validation checklist

Customer-facing URLs point to https://www.pricerightrv.com/.
Agent hub URLs are used only as source or reference links.
validation_status uses a defined status value.
downstream_status uses a defined status value.
Inventory URL is not treated as proof of availability.
UTM values do not contain private customer information.
No CRM, form, message, appointment, or downstream completion is claimed without direct evidence.

Downstream handoff note

Preparing this packet does not send it anywhere. A separate, approved action is required for CRM mutation, form submission, webhook execution, message sending, appointment scheduling, or any other downstream action.

Status definitions

draft: Packet is being prepared and may be incomplete.
ready_for_handoff: Required packet fields are present and the packet is ready for a later approved handoff step.
blocked_missing_required_fields: Packet cannot be handed off because required fields are missing.
awaiting_downstream_confirmation: Handoff was attempted and downstream confirmation is pending.
downstream_confirmed: Downstream system directly confirmed the relevant action.
failed_downstream: Downstream handoff or confirmation failed.
not_sent: No downstream transfer has occurred.
handed_off: Packet was transferred, but confirmation is not yet available.
confirmed: Downstream action was confirmed by direct evidence.
failed: Downstream transfer or confirmation failed.

Last updated: 2026-06-10T10:49:04Z

# Lead Packet Template This packet prepares a lead-routing handoff. It does not prove that a CRM record was created, updated, messaged, or confirmed. ## Packet summary Use this template to prepare a clean lead-routing packet before an approved handoff step. The packet is a preparation artifact only. It does not execute a webhook, submit a form, create a CRM record, send a message, schedule an appointment, or confirm customer contact. ## Required fields - `packet_id` - `created_at` - `source_system` - `source_url` - `shopper_name` - `contact` - `lead_context` - `routing` - `consent_or_contact_note` - `validation_status` - `downstream_status` ## Optional fields Optional context fields include: - `selected_unit` - `inventory_url` - `store_or_location_preference` - `utm_content` - `utm_term` - Any blank contact value that was not supplied by the shopper Do not invent optional values. Use empty strings when a value is not supplied. ## Missing field checklist Before marking a packet `ready_for_handoff`, check: - Packet ID is present. - Created timestamp is present. - Source system is present. - Source URL is present. - Shopper name field is present. - Contact object is present. - Lead context object is present. - Routing object is present. - Consent or contact note is present. - Validation status is present. - Downstream status is present. ## Validation checklist - Customer-facing URLs point to `https://www.pricerightrv.com/`. - Agent hub URLs are used only as source or reference links. - `validation_status` uses a defined status value. - `downstream_status` uses a defined status value. - Inventory URL is not treated as proof of availability. - UTM values do not contain private customer information. - No CRM, form, message, appointment, or downstream completion is claimed without direct evidence. ## Downstream handoff note Preparing this packet does not send it anywhere. A separate, approved action is required for CRM mutation, form submission, webhook execution, message sending, appointment scheduling, or any other downstream action. ## Status definitions - `draft`: Packet is being prepared and may be incomplete. - `ready_for_handoff`: Required packet fields are present and the packet is ready for a later approved handoff step. - `blocked_missing_required_fields`: Packet cannot be handed off because required fields are missing. - `awaiting_downstream_confirmation`: Handoff was attempted and downstream confirmation is pending. - `downstream_confirmed`: Downstream system directly confirmed the relevant action. - `failed_downstream`: Downstream handoff or confirmation failed. - `not_sent`: No downstream transfer has occurred. - `handed_off`: Packet was transferred, but confirmation is not yet available. - `confirmed`: Downstream action was confirmed by direct evidence. - `failed`: Downstream transfer or confirmation failed. Last updated: 2026-06-10T10:49:04Z