Transaction Milestone Updates

Ask anyone who has bought or sold a house what annoyed them about their agent and the answer is almost never the commission or the price. It is that for weeks at a time they had no idea what was happening. A transaction runs thirty to sixty days, carries fifteen to twenty hard deadlines, and involves a lender, a title or escrow officer, an inspector, an appraiser, a co-operating agent and two sets of anxious humans. Between the day the contract is signed and the day the keys move, the agent becomes a switchboard - and a switchboard that is also showing property, taking listing appointments and answering a phone cannot possibly keep eight parties synchronized from memory.

So two things go wrong. The first is silence. Nothing happened today that was worth a phone call, so no call was made, and after four days of nothing the buyer assumes something is wrong and calls to ask. The agent now spends twenty minutes reassuring somebody that no news is normal - a conversation that produces no progress and happens several times per transaction per party. Multiply that across a pipeline of a dozen live deals and a meaningful share of the week disappears into status updates.

The second is worse. Deadlines get missed. An inspection objection window closes unnoticed. A financing contingency is not extended in writing before it lapses. An appraisal comes back and nobody tells the seller for three days, by which time the renegotiation has become an argument instead of a conversation. Deals die from administrative drift far more often than they die from anything dramatic, and every one of those deaths takes a commission, a referral and a review with it. The money leaks in three directions at once: deals lost to avoidable deadline misses, hours consumed by calls that a notification would have prevented, and a client who closes feeling neglected and therefore never refers anybody.

Pipeline and stages

One pipeline, Transactions, and it is the spine of the whole build. Every stage change is a publishing event that notifies the right people automatically.

• Contract Executed - fully signed, nothing else started
• Escrow Opened - file opened with title or escrow, earnest money instructions issued
• Earnest Money Received - receipted and confirmed
• Inspection Scheduled
• Inspection Complete
• Inspection Resolution - objections, repair requests and responses in flight
• Appraisal Ordered
• Appraisal Received
• Loan Processing - underwriting, conditions outstanding
• Loan Approved
• Clear to Close
• Final Walkthrough Scheduled
• Closing Scheduled
• Closed
• At Risk - a parallel flag, not a sequential stage; see the watchdog workflow
• Terminated - fell through at any point

Cash transactions skip appraisal and loan stages by branch rather than by a separate pipeline, so reporting stays in one place.

Calendars

• Inspection - 3 hr, with the inspector and the buyer invited, and the listing side notified of access requirements
• Final Walkthrough - 45 min, bookable only within seven days of the closing date
• Closing Appointment - 90 min, with the escrow or title office as the location and a 30-minute buffer before
• Weekly Transaction Review - 30 min internal, the agent and coordinator going through the At Risk list

Custom fields

These live on the transaction record. Nothing in this build works if they are not populated at intake, which is why intake is a single form rather than a habit.

• txn_role - dropdown: Buyer side, Seller side, Both sides
• txn_property_address, txn_contract_date, txn_target_closing_date
• txn_financing_type - dropdown: Conventional, FHA, VA, USDA, Cash, Other
• escrow_company, escrow_officer_name, escrow_officer_email, escrow_file_number
• lender_company, loan_officer_name, loan_officer_email, loan_officer_mobile
• coop_agent_name, coop_agent_email, coop_agent_mobile, coop_brokerage
• inspector_company, inspection_datetime, inspection_objection_deadline, inspection_resolution_deadline
• appraisal_ordered_date, appraisal_received_date, appraisal_outcome - dropdown: At contract value, Above contract value, Below contract value, Subject to repairs
• financing_contingency_deadline, title_review_deadline, loan_commitment_deadline, clear_to_close_date
• final_walkthrough_datetime, closing_datetime, closing_location, possession_datetime
• client_update_channel - dropdown: SMS and email, SMS only, Email only, Phone only. Ask once at intake and respect it absolutely.
• notify_coop_agent, notify_lender, notify_escrow - checkboxes controlling which milestone broadcasts reach which professional
• last_milestone_sent - text, and last_client_contact_date - date, together powering the silence watchdog
• risk_reason - long text, written whenever the record is flagged At Risk

Tags

• txn-active on every live transaction, cleared at Closed or Terminated
• txn-buyer-side, txn-seller-side, txn-both-sides
• txn-cash, txn-financed, txn-fha-va - the latter because government-backed loans carry extra timelines worth flagging
• deadline-approaching, deadline-missed, txn-at-risk
• txn-silent-4d, applied when no client contact has been logged for four days and removed on contact
• txn-closed, review-requested, review-received
• txn-terminated, with reason-financing, reason-inspection, reason-appraisal, reason-buyer-walked or reason-other
• sms-opted-out, email-unsubscribed as hard suppression tags - note that transactional updates to an existing client are not marketing, but honor the preference anyway and fall back to email or phone

Forms

• Contract intake form - the most important form in the build. One pass, filled by the agent or transaction coordinator within two hours of a signed contract, capturing every field above. Every deadline in the transaction is calculated from the three or four dates entered here, so the form validates that contract date is before closing date and that no deadline falls after closing.
• Inspection outcome form - inspection complete yes or no, major items found, objection intended, objection deadline confirmed, repair request submitted.
• Milestone update form - a short mobile form the agent fills from the car to advance a stage and add one line of plain-language context, which is what the client actually reads.
• Closing logistics form - closing time and location, what to bring, funds instructions reminder, key handover arrangements, utility transfer reminder.
• Post-close survey - three questions on communication, three on the outcome, and one open box. Drives the review request branch.

BO's role and guardrails

• BO answers the single most common inbound question - where are we? - by reading the current stage, the next deadline and the last milestone note off the transaction record, and replying in plain language within seconds, day or night.
• BO can confirm dates already on the record, restate what the next step is, resend the closing logistics, and schedule the final walkthrough.
• BO may never interpret the contract, give an opinion on whether a party is in default, advise on whether to object or waive a contingency, discuss what the appraisal means for the price, comment on loan approval odds, or say anything about repairs beyond what is recorded. Every one of those is a licensed-professional or legal question.
• Hard handoff, immediately and silently to the agent, on: default, breach, attorney, lawyer, sue, cancel, terminate, extension, waive, dispute, lien, or any mention of an appraisal shortfall. These conversations go to a human within minutes, not hours.
• BO always identifies itself as the agent's assistant and never implies it is the agent, the lender, or the escrow officer.

Numbers and channels

• One local number per agent for SMS and voice, A2P registered, used for all client transaction messaging so the whole deal sits on one thread.
• A separate shared transaction desk number for the coordinator, so professional-to-professional traffic with lenders and escrow does not clutter the agent's client threads.
• Email from the brokerage's authenticated domain for anything carrying documents, with the co-operating agent, lender and escrow officer on the appropriate broadcasts.
• One client-facing transaction timeline page per deal - a simple hosted page showing completed milestones, the current step and the next date, linked from every message so the answer to where are we is always one tap away.
• Missed-call text-back on both numbers, because an anxious client at 8pm on a Sunday will call before they text.

One financed purchase, buyer side, from executed contract to the keys. Thirty-eight days.

1. Day 0, 4:40pm. The contract comes back fully signed. The agent opens the contract intake form on their phone and spends eleven minutes entering the property address, contract date, target closing date, financing type, escrow company and officer, lender and loan officer, co-operating agent details, and the four contingency deadlines straight off the contract. They select SMS and email for client_update_channel.
2. On submission the transaction record is created at Contract Executed, tagged txn-active, txn-buyer-side and txn-financed, and the transaction timeline page is generated at a unique link. Every downstream deadline reminder is scheduled in that one moment - nothing further needs remembering.
3. Within two minutes the buyer receives a congratulations message naming the address, the closing target, the first three things that happen next, and the link to their timeline page. The co-operating agent, lender and escrow officer each receive a different email - the professional version, with the file number, the deadline schedule and the contact sheet attached.
4. Day 1. Escrow confirms the file is open. The coordinator advances the stage to Escrow Opened using the milestone update form and types one line: escrow file open, wire instructions coming direct from the title company - we will never email you banking details. That line goes out verbatim, because wire fraud warnings are worth repeating in the client's own thread.
5. Day 3. Earnest money is receipted. Stage moves to Earnest Money Received. The buyer gets a short confirmation and the timeline page ticks another milestone green.
6. Day 4. The buyer books the inspection from the calendar link. Stage moves to Inspection Scheduled. The inspector and buyer get calendar invitations, and the co-operating agent gets an access-request email naming the date, the three-hour window and who will attend.
7. Day 7, 9am. Inspection happens. That evening the agent fills the inspection outcome form: complete, three significant items, objection intended. Stage moves to Inspection Complete, and because an objection is intended the record also moves straight into Inspection Resolution with the objection deadline already on the clock.
8. Day 8. The watchdog fires its first scheduled warning: the objection deadline is 48 hours out. The agent gets it, the coordinator gets it, and the buyer gets a plain-language note saying the deadline exists and what happens if it passes. Nothing is left to memory on a deadline that can cost a client their deposit.
9. Day 9. The repair request is submitted inside the window. The agent logs it. The buyer receives confirmation and a realistic expectation of how long the seller has to respond.
10. Day 12. The seller agrees to two of the three items. Resolution is logged, the record leaves Inspection Resolution, and the lender is notified that the inspection contingency is satisfied so the appraisal can be ordered.
11. Day 13. The lender orders the appraisal. Stage moves to Appraisal Ordered, which starts a silent timer: if no appraisal result is logged within ten days, the coordinator gets a chase task automatically.
12. Day 19. Appraisal comes back at contract value. appraisal_outcome is set to At contract value, stage moves to Appraisal Received. The buyer and the co-operating agent are both told the same day - not three days later - and the automation does not comment on what the number means, only that it has arrived.
13. Day 20 to 29. Stage sits at Loan Processing, which is the part of a transaction where nothing visible happens and clients get nervous. The silence watchdog catches four days of no client contact on day 24 and triggers a reassurance message explaining that underwriting is quiet by nature and that the next real milestone is loan approval. The buyer does not call. That is the entire point.
14. Day 30. Loan approved. Stage moves to Loan Approved; everyone is notified. Day 33: clear to close. Stage moves to Clear to Close and the closing logistics workflow begins.
15. Day 34. The buyer books the final walkthrough for day 37 from the calendar link, and the closing appointment is confirmed for day 38 at the escrow office. Both go into the buyer's calendar automatically, with the closing logistics email listing what to bring, the identification requirement, and a restated wire fraud warning.
16. Day 37. Walkthrough held. The agent marks it complete with one line of context.
17. Day 38. Closing. The agent marks the record Closed. The buyer gets a congratulations message and the full document package by email, txn-active is cleared, and txn-closed is applied.
18. Day 41. The post-close survey goes out. The buyer rates communication at the top of the scale, which routes them into the review request branch; a lower score would have routed them to the agent for a call instead of a public review ask.
19. Day 45. The contact is handed to the past-client program, with the closing date stored as the anniversary trigger, and leaves the transaction system entirely.

Two shared conditions sit at the top of every workflow. First, the channel gate: read client_update_channel and send only on the permitted channels, falling back to email if SMS is suppressed and to a call task if both are. Second, the audience gate: client messages and professional messages are always separate sends with separate copy, never one email with everybody copied.

1. Contract Intake and Transaction Build

Trigger: contract intake form submitted.

Actions in order:

1. Create the transaction opportunity at Contract Executed, named with the property address and the closing date.
2. Write every field from the form. Apply txn-active, the side tag, and txn-cash or txn-financed from txn_financing_type. Add txn-fha-va for FHA, VA or USDA.
3. Generate the transaction timeline page and store its link on the record.
4. Schedule every deadline reminder in this single pass: 5 days, 2 days and 1 day before each of inspection_objection_deadline, inspection_resolution_deadline, financing_contingency_deadline, title_review_deadline and loan_commitment_deadline.
5. Send the client message: "Congratulations {{first_name}} - {{txn_property_address}} is under contract, targeting {{txn_target_closing_date}}. Next three things: escrow opens, earnest money goes in, and we book your inspection. I'll message you at every step, so no news genuinely means no news. Your live timeline is here: {{timeline_link}}"
6. Send three separate professional emails where the matching notify checkbox is ticked - co-operating agent, loan officer, escrow officer - each with the file number, the full deadline schedule, and the contact sheet.
7. Create the agent task Confirm escrow opened due in 2 business days.
8. Stamp last_client_contact_date.

Exit: record reaches Closed or Terminated.

2. Milestone Broadcast Engine

Why it exists: this is the core of the build. One workflow listens for stage changes and publishes the right message to the right audiences, so adding a milestone later means editing copy rather than building a new sequence.

Trigger: transaction stage changes.

Actions:

1. Write the new stage name into last_milestone_sent. Update the timeline page.
2. Branch by stage to select the client copy. Each is two sentences: what just happened, and what happens next. Examples - Escrow Opened: "Escrow is open on {{txn_property_address}} ({{escrow_file_number}}). Wire instructions will come directly from the title company and never from me by email - if you get banking details from anyone claiming to be us, call me first." Loan Approved: "Your loan is approved. Last step is the clear to close from the lender, then we book your walkthrough and closing." Clear to Close: "Clear to close just came through - we're done with the hard part. Closing logistics coming in a separate email."
3. Send to the client on the permitted channels only.
4. Branch by audience. Send the professional version to each of the co-operating agent, lender and escrow officer whose notify checkbox is ticked and for whom this stage is relevant - escrow does not need the inspection scheduling note, and the inspector is not on the loan broadcasts.
5. If txn_role is Both sides, send separate messages to buyer and seller with copy written for each, never a shared thread.
6. Stamp last_client_contact_date and remove txn-silent-4d.
7. Create the next-step task for whoever owns the following milestone.

Exit: Closed or Terminated.

3. Deadline Watchdog and Escalation

Trigger: each scheduled deadline reminder set up in workflow 1.

Actions:

1. 5 days out: notify the agent and the coordinator only. No client message - it is too early and only creates anxiety.
2. 2 days out: notify the agent and coordinator again, apply deadline-approaching, and send the client a plain-language note: "Quick heads-up: the {{deadline_name}} on {{txn_property_address}} is {{deadline_date}}. Nothing for you to do unless I ask - just so the date isn't a surprise."
3. 1 day out with the milestone still not logged: escalate. Notify the broker or team lead as well, create an urgent task, and put the record on the next Weekly Transaction Review agenda.
4. Deadline date passes with nothing logged: apply deadline-missed and txn-at-risk, write risk_reason, notify agent, coordinator and broker at once, and create a task to call the client within two hours. No automated client message goes out on a missed deadline - that conversation is a phone call from a human, always.
5. Silence watchdog: run daily. If last_client_contact_date is 4 or more days ago and the record is txn-active, apply txn-silent-4d and send a reassurance message naming the current stage and the next expected event. Clear the tag on any logged contact.

Exit: milestone logged, or record Terminated.

4. Inspection Orchestration

Trigger: stage enters Inspection Scheduled.

Actions:

1. Send the buyer a confirmation with the date, the window, who attends, and what to expect from the report timeline.
2. Email the listing side an access request naming the date, window and attendees. On the seller side, message the seller with preparation notes - pets, access to the attic and crawlspace, utilities on.
3. Wait until 24 hours before. Remind buyer, inspector and the access-granting party.
4. Wait until 4 hours after the scheduled end. Create the agent task Complete inspection outcome form, and chase it every 12 hours until filled. The objection clock is already running and the form is what starts the resolution tracking.
5. On form submission: move to Inspection Complete. Branch on objection intended. If yes, move immediately to Inspection Resolution and confirm the objection deadline is scheduled. If no, notify all parties that the inspection contingency is satisfied and prompt the lender to order the appraisal.
6. In Inspection Resolution, send the client a plain-language expectation of the response window and nothing more. The system reports status; the agent advises.

Exit: resolution logged, or Terminated.

5. Appraisal and Financing Tracking

Trigger: stage enters Appraisal Ordered. Skipped entirely when txn-cash is present.

Actions:

1. Notify the client that the appraisal is ordered and that results typically take several days, with no promise of a specific date.
2. Start a 10-day timer. If appraisal_received_date is still empty, create a coordinator task to chase the lender, and repeat every 3 days.
3. On appraisal_outcome being set, move to Appraisal Received and notify the client the same day. Branch on outcome. At or Above contract value: standard milestone message. Below contract value or Subject to repairs: send no automated client message at all. Instead apply txn-at-risk, write risk_reason, and create an urgent call task for the agent with a 1-hour due time. A valuation shortfall is a negotiation, not a notification.
4. In Loan Processing, send one scheduled reassurance message at day 5 explaining that underwriting is quiet by design, then rely on the silence watchdog.
5. Three days before loan_commitment_deadline with no commitment logged, notify agent, coordinator and broker, and create a task to speak to the loan officer directly rather than emailing.

Exit: Loan Approved, or Terminated.

6. Weekly Transaction Digest

Trigger: Friday 7:00am, and separately Monday 7:00am.

Actions:

1. Internal digest to each agent and the coordinator: every txn-active record, its stage, days to closing, the next deadline, and whether txn-at-risk or txn-silent-4d is set. Sorted by nearest deadline, with at-risk records at the top.
2. Create a Weekly Transaction Review calendar event if any record carries txn-at-risk.
3. Client digest, Friday only, to every active client: "End of week on {{txn_property_address}}: we're at {{current_stage}}, {{days_to_closing}} days to closing, and the next date that matters is {{next_deadline_name}} on {{next_deadline_date}}. Full timeline: {{timeline_link}}" Suppress it for any client who already received a milestone message in the previous 24 hours, so Friday does not read as duplicate noise.
4. Stamp last_client_contact_date on every client digest sent.

Exit: record no longer txn-active.

7. BO's Status Concierge

Trigger: inbound SMS or chat from a contact tagged txn-active.

Actions:

1. Read the transaction record. Answer status questions directly: "You're at {{current_stage}} on {{txn_property_address}}. The next date is {{next_deadline_name}} on {{next_deadline_date}}, and closing is still targeted for {{txn_target_closing_date}}. Anything specific you want {{agent_first_name}} to call you about?"
2. BO may resend the closing logistics, resend the timeline link, confirm the walkthrough or closing time, and book the final walkthrough from the calendar.
3. Hard handoff branch. On any of: default, breach, attorney, lawyer, sue, cancel, terminate, extend, extension, waive, dispute, lien, appraisal came in low, or financing fell through - BO sends one line ("Let me get {{agent_first_name}} on this right now."), stops, and alerts the agent by push and SMS with the message text quoted.
4. Outside 8am-9pm, BO still answers status questions, because a client awake at 1am worrying is exactly who this is for - but handoff alerts queue as urgent for 7am unless a handoff keyword is present, in which case the agent is notified immediately.
5. Every BO conversation stamps last_client_contact_date and clears txn-silent-4d.

Exit: handoff, or record closed.

8. Closing Logistics and Walkthrough

Trigger: stage enters Clear to Close.

Actions:

1. Send the client the Final Walkthrough calendar link, restricted to the seven days before closing.
2. Send the closing logistics email: time, address, duration, identification requirements, what to bring, how funds are transferred, and an explicit wire fraud warning in bold text - verify every set of wiring instructions by phone with a number you already have, never one from an email.
3. Notify the co-operating agent, lender and escrow officer that the file is clear to close, with the walkthrough and closing times once set.
4. Wait until 48 hours before closing. Send a utility transfer and address change reminder, plus key handover arrangements and the possession time.
5. Wait until 24 hours before. Send SMS confirming time and place with a reschedule contact.
6. Wait until 2 hours before. Send a short SMS: "On my way - see you at {{closing_location}} at {{closing_datetime}}. Bring photo ID."
7. On the walkthrough being marked complete, notify all professional parties.

Exit: Closed, or Terminated.

9. Post-Close, Review and Handoff

Trigger: stage set to Closed.

Actions:

1. Clear txn-active, apply txn-closed, stop every transaction workflow, and stop the Friday digest.
2. Send the congratulations message and the complete document package by email within one hour.
3. Wait 3 days. Send the post-close survey.
4. Branch on the communication score. Top of the scale: wait 1 day, then send the review request with direct links to the two platforms that matter most to the brokerage, and apply review-requested. Mid or low: send no review request at all; create an urgent call task for the agent with the open-text answer quoted, because a mediocre score is information worth having and a public review ask would waste it.
5. Wait 7 days after the review request. If review-received is not set, send one reminder and stop. Never a third ask.
6. Wait 14 days from closing. Send the referral message: "{{first_name}}, hope the boxes are nearly gone. If anyone you know is thinking about moving, send them my way - I'll look after them the same way."
7. Wait 45 days. Hand the contact to the past-client program with the closing date stored as the anniversary trigger, and remove it from the transaction system.
8. Terminated branch. If the stage is set to Terminated at any point: stop every workflow immediately, clear txn-active, apply txn-terminated and the reason tag, send no automated message of any kind, and create an urgent call task. Then, after 14 days, enroll a buyer-side client into the active-buyer search sequence or a seller-side client into the seller nurture sequence - a fallen-through deal is still a motivated client.

Exit: handoff to the past-client program.

The agent stops being the switchboard. Every stage change publishes itself to the client, the co-operating agent, the lender and the escrow officer in the wording each of them needs, which means the information moves whether or not the agent remembered to move it. The agent's job narrows to the part that actually requires them: negotiating, advising, and making the two or three judgment calls per deal that no automation should ever touch.

Deadlines stop depending on memory. Every contingency date is scheduled the moment the intake form is submitted, warned three times before it lands, and escalated to the broker if it passes unlogged. The specific category of disaster that comes from nobody noticing a window closing largely disappears, and the deals that do fall through fall through for real reasons.

Silence stops reading as neglect. The stretch between appraisal and loan approval is the quietest and most anxious part of any transaction, and it is where reputations are lost. A scheduled reassurance message and a Friday summary cost nothing and replace a stream of just checking in calls that produced no progress. Clients close feeling well handled, which is what produces the review and the referral - and the build asks for both at the exact moment goodwill peaks, rather than six months later when it has faded.

Metrics to watch

• Intake completion time - hours from executed contract to intake form submitted. If this drifts past a day, every downstream reminder is late and the build degrades. Watch this one hardest.
• Intake field completeness - percentage of records with all deadline dates and all three professional contacts populated. Partial intake is the main failure mode.
• Deadline miss count per month, and the count of records that ever carried deadline-missed. The target is zero and it is achievable.
• At-risk incidence and recovery - how many records get flagged txn-at-risk, and what share of those still close.
• Fall-through rate by reason tag, which tells you whether deals are dying from financing, inspection, appraisal or buyer nerves - and therefore what to fix.
• Inbound status inquiries per transaction, split between those BO resolved and those that reached the agent. This number should fall month over month and is the clearest measure of the build's value.
• Average days from contract to close, compared with the target closing date set at intake.
• Silence incidents - how often txn-silent-4d fires. Frequent firing means the milestone copy is too sparse for the quiet stages.
• Post-close survey completion rate, and the communication score specifically, tracked by agent.
• Review request to review received conversion, and the share of closings that produced a public review at all.
• Referrals attributed to past transactions, measured over quarters. This is the metric the whole build is ultimately for.

Prerequisites

• A written milestone map for your own market: every stage, which contingency deadlines attach to it, and who owns advancing it. Transaction mechanics differ substantially between states and countries, and this build has to mirror the real contract, not a generic one.
• A decision on who fills the intake form and what the service-level commitment is - two hours from executed contract is a reasonable standard, and the build is only as good as that discipline.
• Standard document templates: the contact sheet, the deadline schedule, the closing logistics email, and the document package sent at close.
• Named escrow, title, lender and inspector contacts for the firms you work with repeatedly, so intake is selection rather than typing.
• Agreement from the co-operating agents and loan officers you work with most that they are happy to receive the professional broadcasts, and a notify checkbox that lets you turn them off per deal when they are not.
• A transaction coordinator or a clearly named person who owns the pipeline. Advanced builds fail without an owner.

Integrations

• Google Calendar or Outlook two-way sync for inspection, walkthrough and closing appointments, with invitations reaching third parties who are not in the system.
• Sending domain authenticated with SPF, DKIM and DMARC. This build sends documents and deadline notices to professionals, and a message in a spam folder is a missed deadline waiting to happen.
• A document signing tool for amendments, extensions and addenda, with completion events able to advance a stage.
• Optional: the transaction management or compliance platform the brokerage already uses, so the pipeline mirrors rather than competes with it. Decide early which system is the source of truth for dates - one of them must be.
• Optional: QuickBooks or Xero for commission invoicing at close, and a webhook or Zapier or Make connection where a direct integration does not exist.

Number provisioning and messaging compliance

• One local number per agent plus one shared transaction desk number, all A2P registered before launch.
• Complete A2P 10DLC brand and campaign registration early. Register the transaction messaging as its own campaign, separate from any marketing campaign, and describe it accurately as service notifications to existing clients - the use case matters to the carriers and to the throughput you get.
• Capture messaging consent at the point the client signs the representation agreement, not at contract. Record the timestamp and keep it.
• Honor STOP and the other opt-out keywords automatically. Because these are service messages a client genuinely needs, build an explicit fallback: on SMS opt-out, switch client_update_channel to email and notify the agent to confirm verbally how the client wants to be kept informed.
• Quiet hours of 8am to 9pm apply to all scheduled sends. BO may answer inbound questions at any hour; it may not initiate outside those hours.
• If calls are recorded on either number, play the notice and check whether all-party consent is required where you operate.

Compliance and data protection

• Wire fraud is the single largest financial risk in this build's blast radius. Never send wiring instructions, account details or payment amounts through any automated message. Every message that mentions funds carries the same warning: verify instructions by phone using a number the client already has. Put that line in the templates, not in the training.
• No automated message should ever interpret the contract, characterize a party's conduct, or advise on waiving, extending or objecting. Keep templates factual: what happened, what is next, what date applies.
• Transaction records contain sensitive personal and financial information about clients and counterparties. Restrict who can view them, document the retention period, and have a deletion process. Do not store identity documents or bank details in the contact record at all.
• Professional broadcasts go only to parties who have a legitimate role in the transaction, and only the information they need for that role. Do not copy the lender on inspection detail or the inspector on financing status.
• Brokerage record-retention and supervision rules often require that client communications be archivable and reviewable by a broker. Confirm that the messaging archive satisfies whatever your regulator and your brokerage require.
• Fair housing applies to transaction communications too. Keep every template neutral and free of commentary about people, areas or circumstances.
• Confirm all of the above with the client's own attorney and broker compliance officer before launch. Nothing here is legal advice, and transaction practice, licensing obligations, record retention and messaging rules vary materially by jurisdiction.

Scoping

Transaction volume, the number of agents, whether a coordinator exists, which existing transaction platform has to stay in the loop, and how much of the milestone map is local all change the build substantially. To scope it against a real operation, book a call at bookings.appbo.io.