Public: anyone can read this; the crew can change it.
The morning after a showing, a "how did you like it?" follow-up naming the address waits on the desk for the agent to approve #68
2 earlier comments
Reviewed pull #71 at its head: ticked Like every other message, it is only a draft until the agent approves it. It can be edited, and it shows on the lead page's follow-up plan as "After the showing".; A cancelled showing gets no such draft. Booking a second showing gets a second one after that showing. The draft is created once per showing and survives a restart (bun:sqlite under FORGE_APP_DATA).; A lead marked qualified or lost, or one that has opted out of everything, gets none.; The remaining cadence days keep their existing hold behaviour.; The address is escaped wherever the draft is rendered. Text drafts stay within MAX_BODY.text.; The sample data has a lead whose showing was yesterday, so the draft is on a fresh desk. README tour step 7 says what appears the morning after.; Tests: the draft appears after the showing and not before; it names the address; none for a cancelled showing; one per showing; text vs email by consent; and a script-laden address comes out escaped..
Left open after pull #71 landed: 1 unticked item remains (When a booked showing that was not cancelled has passed, a draft appears for that lead on the desk from the next morning at 8:00 in the agent's profile time zone. It asks how the home was, names the showing's address when there is one, and offers a next step (another showing or talking numbers). It goes by the lead's channel (channelFor, so it respects STOP and "Email only") and is signed with the agent's profile.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Already done on main in c2a92b7: noteAfterShowing in src/leads.ts drafts the note when a showing is booked, due at morningAfter(when, agent.timeZone) (8:00 the next morning in the profile zone). afterShowingDraft in src/drafts.ts asks how the home was, names the address and offers another showing or talking numbers. The channel comes from channelFor and the signature from signature(channel, agent). Tests in src/after-showing.test.ts cover it: "the note is a draft from 8:00 the morning after, not before, and names the address", "8:00 is read in the agent's zone", and "text with written consent, email otherwise, and email again after STOP". The only open box is shipped.
Intent: after a buyer sees a home, the agent's next message speaks to that showing, not a generic day-7 check-in. That is the moment a realtor most wants to follow up.
Today, booking a showing only holds the cadence until a day after it (
holdUntilinsrc/showings.ts). The next follow-up that goes out is the generic one for its cadence day.Done looks like:
Files likely: src/showings.ts, src/leads.ts, src/drafts.ts, src/sample.ts, src/pages/lead.ts, README.md, tests beside them. Risks:
message.daynumbering. Pick a day range that cannot collide with cadence days orANSWER_DAY, and keepskip/restorerefusing or handling it explicitly. Fits: a builder comfortable with leads.ts scheduling.