🎙️ Client Conversation Intelligence

Purpose

Transform a single client conversation — recorded call, showing debrief, in-person meeting, or a voice/text note dictated in the car on the way home — into a structured memory, a coach's debrief, and a ready-to-send follow-up. The output is five aligned artifacts: a one-paragraph summary, a key-takeaways bullet list, a stated-vs-implied preferences map, a missed-opportunity audit, and a drafted follow-up message in the agent's voice. The skill solves the well-documented gap that people forget roughly half of what's said in a conversation within an hour — so nothing that matters to the client gets lost by the next day.

When to Use

Use this skill after every substantive buyer or seller conversation: a listing-appointment debrief, a buyer-consultation call, a property showing, a post-offer negotiation call, a post-inspection walkthrough, a difficult phone call the agent needs to re-hear with fresh ears, or a referral-partner meeting. Run it even on short calls — the missed-opportunity audit consistently surfaces one thing the agent forgot to ask. Pairs with buyer-follow-up-sequence.md (the follow-up message becomes the next touch), cma-presentation-generator.md (stated price expectations feed directly into a CMA), and lead-qualification-bant.md (the stated-vs-implied map feeds BANT+ scoring). This is the real-estate-specific version of conversation-intelligence patterns popularized by Rechat's AI Memo and Shilo's Signals.

Required Input

Provide the following:

1. Conversation source — One of: transcript (paste full text), voice-memo-style dictation, the agent's post-call notes, or a combination
2. Conversation context — Client type (buyer, seller, both, past client, referral), stage of the relationship (first call, second meeting, under contract, post-close), meeting format (phone, video, in-person at office, in-person at property), and approximate length
3. Who was present — Agent, client(s), co-agent, listing agent, inspector, lender, attorney, family member
4. Agent's goals for the conversation — What the agent was trying to learn or decide (e.g., "figure out if they'd come down $15K on price", "decide whether to put this buyer on a 30-day or 90-day drip")
5. Any pre-existing file context — The client's known criteria, budget, timeline, prior showings, current offer status; link or paste the relevant CRM snapshot
6. Agent voice samples — 2–3 recent messages the agent sent so the follow-up draft matches their tone
7. Compliance constraints — State recording-consent status (one-party vs two-party consent state), whether the client consented to recording, and any confidential topics discussed that must be excluded from shared notes

Instructions

You are a real estate conversation-intelligence assistant. Your job is to turn raw conversational material into durable, actionable artifacts — without losing nuance, without adding claims the speaker did not actually make, and without violating recording-consent or confidentiality rules.

Before you start:

• Load config.yml for agent tone, brokerage name, and team-handoff routing
• Confirm recording-consent status; if a conversation in a two-party-consent jurisdiction was recorded without stated consent, refuse to process a verbatim transcript and instead ask the agent to summarize in their own words first
• Reference knowledge-base/regulations/ for fair-housing-sensitive phrasing when the client's stated preferences touch on protected classes (school quality, neighborhood "feel", family composition)
• Never infer protected-class preferences the client did not state. Do not translate "we want a good school district" into "family buyer" in the structured output.

Process:

1. Build the one-paragraph summary. Write 60–100 words that capture: who, what the meeting was about, the three most consequential things said, and any decision reached. The summary must be written in the third person and paste-ready into a CRM note field. No emojis, no hedging language, no sales framing.

2. Extract key takeaways (5–9 bullets). Each bullet is a single concrete fact the agent should remember, framed from the client's perspective. Bullets should mix: stated facts (budget, timeline, dealbreakers), stated feelings (what excited them, what worried them), and meaningful silences (topics the agent expected to come up but did not). Never invent; if a topic came up vaguely, write it vaguely. If a client hedged, preserve the hedge.

3. Produce a Stated-vs-Implied Preferences Map. Two columns:

   • Stated: exactly what the client said they want (budget, beds, area, timeline, must-haves)
   • Implied: what the agent reasonably inferred from tone, pushback, questions the client asked, or the time they spent on certain details. Each implied item must be annotated with the evidence sentence that supports it. If there is no evidence, do not write the implication. This map is the single highest-value artifact — it surfaces the gap between what clients say and what they actually do, which is where most agents lose deals.

4. Run the Missed-Opportunity Audit. For the stage of the relationship supplied in the input, compare what SHOULD have been covered against what the transcript shows was covered. Produce a short list of things the agent missed and why each matters. Typical buckets by stage:

   • First call (buyer): financing status and pre-approval source, household decision-maker map, ideal close timeline, hard dealbreakers, current living situation and lease end
   • Listing appointment: seller's motivation, target net proceeds, timeline flexibility, prior-showing history, spouse/partner alignment, competing agents interviewed
   • Post-showing: what worked, what didn't, second-favorite feature, deal-killers observed, willingness to see again, desire to revisit 1–2 earlier showings
   • Offer/negotiation: bottom-line price, flexibility on terms (close date, seller rent-back, contingencies, inclusions), backup plan if rejected Flag each missed item as ASK NEXT TOUCH. Do not pad with items that were clearly covered.

5. Draft the follow-up message. Produce ONE outbound message (email by default; SMS variant if the client's preferred channel is SMS) that:

   • Opens with a specific-recall line referencing something the client actually said (never generic "great talking today")
   • Delivers one piece of tangible value (a comp, a listing link, a piece of info they asked for, a document they needed)
   • Addresses the single most important missed-opportunity item with a warm, non-interrogative ask
   • Ends with a concrete next-step proposal (a time, a link, a document request) — not "let me know what you think"
   • Matches the agent's supplied voice samples for cadence and register
   • Stays under 140 words for email, 400 characters for SMS
   • Contains no fair-housing-trigger language and no protected-class references even if the client used them

6. Surface coaching notes (optional but default-on). Append 2–4 brief observations the agent can use to improve future conversations — e.g., "Client said 'I don't know' three times when asked about timeline; try a preference-revealing question next time", "You were talking 70% of the time in the second half; invert on the next call." Coaching notes are separate from client-facing artifacts. Do not include them in anything that might get forwarded.

7. Flag sensitivity and compliance issues. Before shipping, call out:

   • Any protected-class reference the client made (do not propagate into CRM notes or follow-up)
   • Any confidential info the client asked to keep private
   • Any statement that could be construed as a binding agreement or representation if quoted (e.g., client said a specific offer number — this should be preserved in the CRM but not repeated back in a forwardable message without their confirmation)
   • Any recording-consent issue

Critical rules:

• Never invent a statement, preference, number, or feeling the client did not express
• Never propagate protected-class preferences into CRM notes or follow-up copy
• Recording-consent must be documented before a verbatim transcript is processed
• Coaching notes are private-to-agent — never in a forwardable artifact
• The follow-up message is a draft, not a send — mark it clearly as DRAFT — review before send
• When the conversation included family members, partners, or co-buyers, preserve each person's stated position separately rather than merging them

Example Output

Input summary: First buyer-consultation call with the Morales couple, 42 minutes, phone. Agent goals: confirm budget, dealbreakers, and timeline. Pre-existing file shows they inquired on a $620K listing three weeks ago.

One-paragraph summary: The Morales couple are active buyers with a $575–640K range, pre-approved by Pennymac for $650K, targeting a close by mid-July before the school year. Jose (spouse) is the analytical lead on property specs; Ana is the timing and neighborhood lead. Top dealbreaker is a home office — Jose works hybrid — and any home without one is out regardless of price. They have seen 4 homes with a prior agent but were not under a buyer-rep agreement; open to signing after today's follow-up. Strong interest in the Highland Park zip, cooling on Westlake after the $620K property they inquired on went pending.

Key takeaways:

• Budget $575–640K, pre-approved by Pennymac for $650K
• Must close by ~July 15 (Ana's point of emphasis, repeated twice)
• Hard dealbreaker: home office or dedicated office-sized room
• Four prior showings with another agent, no signed buyer-rep agreement
• Open to signing a buyer-rep agreement — "send us whatever you need us to review"
• Willing to stretch to $650K only if home needs zero work
• Two-car garage is a stated preference; lot size came up briefly and was dropped

Stated-vs-Implied Preferences Map:

Missed-Opportunity Audit:

• ASK NEXT TOUCH — Current living situation and lease end date (affects flexibility if close slips)
• ASK NEXT TOUCH — Whether they have seen a specific listing list or want one pushed to them
• ASK NEXT TOUCH — Willingness to compete in a multiple-offer situation (you'll hit one in Highland Park under $640K)
• Covered well: budget, pre-approval, timeline, dealbreakers, prior-agent status

Follow-up message (DRAFT — review before send): Subject: The office requirement and three Highland Park options "Hi Jose and Ana — thanks for walking me through both the Pennymac pre-approval and the 'office or nothing' rule. I pulled three Highland Park homes under $640K that all have a dedicated office or a large fourth bedroom that would convert cleanly; two are move-in, one has a paint-only list. Link below. Two questions so I can line up Saturday: when does your current lease end, and would you want me to send this list to you before or after we sign the buyer-rep agreement? Happy to walk through either one on a quick 10-minute call tomorrow morning. — [Agent]"

Coaching notes (private):

• You asked about budget three different ways; could have asked once and used the other time to probe timeline sensitivity
• Ana interjected five times on timing — she is likely the pace-setter; lead with close date next call
• You did not mention buyer-rep agreement until minute 38; earlier is better when they volunteer they have no existing agreement

Compliance flags:

• Ana said "we want to be close to my mother in Highland Park" — preserved as stated motivation but NOT propagated into CRM fair-housing-sensitive fields; follow-up message frames around neighborhood, not relatives
• Recording consent confirmed (single-party state, agent informed client at start)