# Lead Follow-Up Sequence Packet

Sample buyer-facing packet generated from Setup Your AI private product repositories.

Source: setupyour-agent-products
Data policy: sample fixture only; no live customer records, credentials, uploads, payment data, or private transcripts.
Approval policy: human approval is required before external sends, customer-system writes, booking holds, pricing exceptions, payment-affecting actions, legal answers, refunds, or policy exceptions.

# Lead Follow-Up Sequence: Mountain View Events

Lead: Casey <casey@example.com>
Conversion goal: Book a qualified tour without promising availability.
Follow-up window: 10 days

## Inquiry summary

- Casey asked about a September Saturday wedding for 150 guests and wants a tour.

## Approved facts

- Tours run Tuesday through Saturday.
- The venue handles weddings and private events up to 180 guests.
- Booking holds, availability, discounts, and contract terms require owner approval.

## Missing details

- exact wedding date
- preferred tour windows
- phone number

## Human-approved messages

### Message 1 - day 0

Purpose: Reply quickly and ask for the missing details.
Subject: Quick follow-up from Mountain View Events
Approval required: yes

Hi Casey, thanks for reaching out to Mountain View Events. I have this noted: Casey asked about a September Saturday wedding for 150 guests and wants a tour. Before we point you to the right next step, could you send exact wedding date, preferred tour windows, phone number? A person will review the details before anything is promised.

### Message 2 - day 3

Purpose: Nudge the lead with one useful approved fact.
Subject: Still interested in Mountain View Events?
Approval required: yes

Hi Casey, I wanted to follow up on your request for Mountain View Events. One useful detail: Tours run Tuesday through Saturday. If this still matters, reply with exact wedding date and we will route it for human review.

### Message 3 - day 10

Purpose: Close the loop without pressure and preserve the lead.
Subject: Should we close the loop?
Approval required: yes

Hi Casey, I am closing the loop on your Mountain View Events inquiry for now. If you still want help, reply here and a person can pick it back up. We will not hold dates, change a calendar, apply discounts, or update records without human approval.

## Owner tasks

- Review and approve message 1 before any external send.
- Confirm the approved fact used in message 2 is still accurate.
- Stop the sequence if the lead replies, opts out, books, or becomes risky.
- Record the outcome manually until a client-specific CRM/email integration is approved.

## Acceptance checks

- Every message is marked approvalRequired.
- The first message asks for missing details instead of inventing them.
- The sequence stops on reply, opt-out, booking, or risk escalation.
- No output claims email, CRM, calendar, booking, or payment integrations are already wired.

## Non-goals

- No autonomous external sending in v0.
- No CRM, calendar, email, SMS, booking, payment, or website write access until explicitly approved and scoped for the client.
- No availability promises, booking holds, discounts, refunds, legal answers, or contract terms beyond approved escalation language.
- No live customer data, credentials, private transcripts, or uploads stored in this reusable product repo.

## Pricing anchor

- Lead follow-up sequence pilots start around $3,500.