When does a prospect get the application link?

Raised 2026-08-25 off the Daniel Brehm conversation (Zillow lead asked "send me an application", Clara pivoted to a tour and never sent it). Pick one — each person's answer is saved separately.

Where things stand today (verified):

The link fires automatically once, ~2h after a tour is booked (not held), then the post-tour chase restates it +1d/+3d/+7d (#4413).
#4147 added a no-tour path: an explicit "I want to apply" gets the link with no tour at all.
The leasing prompt treats "share the link" and "pivot to a tour" as alternatives — no tour-first gate exists in code.

Fede, Jul 19: "regardless we should always send it if asked."
Gera, Aug 25: "IIRC we've always required tours to be held before we give them applications."

The tension: a tour-first gate protects the leasing funnel (a toured prospect converts better, and a tour lets us qualify before screening fees); send-on-ask respects explicit intent and never loses a hot lead who just wants to apply now.

Your call

A — Send on ask, always current code intent

Anyone who explicitly asks for the application gets the link in that reply, tour or no tour. Clara still pitches the tour alongside. Daniel's conversation was a miss under this policy.

B1 — Tour must be BOOKED first

No link until a tour is on the calendar. An "I want to apply" gets a warm tour pitch; the link fires on booking (today's ~2h post-booking automation becomes the only path). Daniel's conversation was correct under this policy.

B2 — Tour must be HELD first

Strictest gate: the link only goes out after the prospect actually shows up. Requires moving the automation trigger from booking to tour completion. Remote/out-of-state applicants would need a virtual tour or a PM exception.

C — Pitch the tour, but include the link when asked

Middle path: an explicit application ask gets BOTH in one reply — "here's the application; most people like to tour first, want me to set one up?" Tour stays the lead CTA; the explicit ask is never refused.

Notes / conditions

What happens after you answer

Pick	Follow-up work
A	Fix the Daniel-class miss: eval case + prompt nudge so an explicit ask always sends (extends #4147's intent to every entry path).
B1 / B2	New prompt rule + gate in the send path, eval cases both directions, and an ADR pinning the policy. B2 also moves the automation trigger.
C	Prompt rewrite of the ask-handling rule + eval cases; smallest code delta.
Any	Separate but related: Camellia's configured "application link" is camelliadenver.com/#floor-plans — a site anchor, not a real apply portal. Needs a real URL regardless of the pick.