Past Client Anniversary Program

A past client is the most valuable asset an agent will ever own and the one they maintain worst. Somebody who bought a house with you will typically move again, will almost certainly know other people who move, and already trusts you - which is the expensive part of every other lead source. They cost nothing to reach. And most agents let them go completely silent within eighteen months of handing over the keys.

What happens is not malice, it is arithmetic. The agent is busy with people who are transacting right now, and a client who will move in seven years never makes it onto this week's list. The intention is genuine - everyone means to stay in touch - but intention does not survive contact with a Tuesday. So the Christmas card gets sent for two years and then stops, the pop-by happens for the clients who live on the way to the office, and everybody else drifts. Four years later the client is ready to sell, cannot remember the agent's surname, and types a search into their phone. The agent then pays for a lead to replace a client they already had.

The leak is the whole relationship. Every closed transaction represents a future listing, a future purchase, and several referrals, and the entire value of it decays through nothing more than silence. The fix is unglamorous: a small number of genuinely useful touches, scheduled years in advance, running without anyone remembering to run them, with one mechanism that detects the moment a dormant client starts thinking about moving and hands them to a human before they type anything into a search engine.

Pipeline and stages

One pipeline, Past Clients. Unlike a sales pipeline, movement here is slow and mostly automatic - the stages exist so you can see the shape of the database at a glance.

• Year One - closed within the last twelve months, highest touch frequency
• Years Two to Four - steady state
• Years Five Plus - approaching statistical move likelihood, frequency increases again
• Signal Detected - something they did suggests they are thinking about moving
• Re-engaged - a human has made contact and is in conversation
• Returned Client - transacting again; handed to the seller or buyer pipeline
• Referral Source - has sent at least one referral, and is managed with more care than anyone
• Dormant - no engagement across a full year of sends
• Removed - unsubscribed or asked to be left alone

Calendars

• Equity Review Call - 20 min, the booking destination for the annual home value update. Phone, wide availability, no pressure framing.
• Listing Appointment - 60 min, for a past client who turns out to be ready to move.
• Client Event RSVP - optional, used where the agent runs an annual client appreciation event and wants attendance tracked against the database.

Custom fields

• pc_closing_date - date. The single most important field in the build; every anniversary touch is calculated from it.
• pc_closing_year - number, for easy segmentation
• pc_property_address - the address they bought or the one they moved to
• pc_client_type - dropdown: Buyer, Seller, Both, Investor
• pc_household_note - long text. The one or two human details the agent actually remembers: the dog's name, that they renovate constantly, that they hated the move. This is what makes the annual message read like a person wrote it.
• pc_partner_name - text, so the anniversary message addresses both people
• pc_preferred_channel - dropdown: Email only, Email and SMS, SMS only, Post only, No contact
• pc_birthday - date, optional, only where the client volunteered it
• pc_last_touch_date - date, stamped on every send and used by the hygiene workflow
• pc_last_engagement_date - date, stamped only on an open, click or reply - which is a very different thing from a send
• pc_referrals_sent - number, incremented manually or by the referral form
• pc_review_left - checkbox, and pc_review_platform - text
• pc_estimated_value_sent_date - date, so the annual equity update never doubles up
• pc_move_signal - long text, recording what the signal actually was

Tags

• past-client on everyone in the program, applied once and never removed except on unsubscribe
• pc-year-1, pc-year-2-4, pc-year-5plus - maintained automatically by a scheduled recalculation, not by hand
• pc-buyer, pc-seller, pc-investor
• pc-referral-source, pc-review-given, pc-event-attendee
• pc-signal-hot, applied by the signal watch workflow and the only tag in the build that generates an immediate human task
• pc-dormant, pc-no-contact
• sms-opted-out, email-unsubscribed as hard suppression tags

Forms

• Past client enrollment form, filled once at handoff from the transaction: closing date, property address, client type, partner name, preferred channel, and the household note. Five minutes per client, and the only manual work in the whole build.
• Referral submission form, a short public page the agent can send to anyone: who the referral is, the best way to reach them, and what they are looking at. Submission increments pc_referrals_sent on the referring client and creates the new lead with the referral source attached.
• Equity update request form, two fields - address confirmation and anything that has changed about the property - used when a client responds to the annual value email.
• Annual check-in survey, optional, three questions on how the house is working out, whether anything has changed, and whether they would like to hear less often. The last question is not a weakness; a client who tells you to back off is worth keeping.

BO's role and guardrails

• BO handles inbound replies to anniversary and equity messages: thanking them, answering whether the agent still covers their area, and offering the Equity Review Call calendar.
• BO may confirm that a value update has been requested and route it to the agent. It may not produce, estimate or imply any figure about a property's worth. If asked, the reply is one line: "I'd rather {{agent_first_name}} give you a real number than me guess - want me to put a short call in the calendar?"
• BO may not discuss commission or fees, and hands off on contract, attorney, divorce, probate, estate, bankruptcy, foreclosure or any mention of a difficult personal circumstance. Those replies go to a human immediately and quietly, with no automated follow-up queued behind them.
• BO always identifies itself as the agent's assistant, and because these are long-standing relationships it keeps messages short and does not attempt to qualify a friend of the business like a cold lead.

Numbers and channels

• The agent's existing local number for SMS, A2P registered. Past clients already have it saved, which is most of why SMS works here.
• Email from the agent's own authenticated domain, sent as a plain personal-looking message rather than a designed newsletter template - the anniversary email should look like it came from a person, because the whole premise is that it did.
• Social planner scheduling the public side of the same calendar: closing anniversary posts where the client has agreed to be featured, sold-result posts, and the annual client event. Nothing identifying a client is ever posted without written permission recorded against the record.
• Optional printed layer: an annual card posted to clients whose pc_preferred_channel is Post only, generated as an export from the same segment so nobody is handled twice.

One client, from the day after closing to the day they list with the same agent six years later. Most of this happens with nobody doing anything.

1. Day 45 after closing. The transaction is finished and the agent spends five minutes on the past client enrollment form: closing date, property address, client type Buyer, partner's name, preferred channel Email and SMS, and in the household note: two cats, Marcus works from the back bedroom, they are going to redo the bathroom first. That note is the only part of this build that cannot be automated and the only part that makes it work.
2. The contact is tagged past-client, pc-buyer and pc-year-1, enters the Past Clients pipeline at Year One, and every anniversary and quarterly send for the next ten years is scheduled in that moment.
3. Month 3. First touch after handoff: a short email asking how the house is settling and whether they need a plumber or an electrician recommendation. No ask, no marketing. The client replies asking for a tiler. The agent sends two names, which takes ninety seconds and buys another two years of goodwill.
4. Month 6. The quarterly neighborhood email arrives: two sold results on nearby streets and one line on what the area has done since they bought. They open it. pc_last_engagement_date is stamped.
5. Month 12 - the first anniversary. The big one. An SMS in the morning - one year in the house today - naming the address, and an email the same afternoon with the annual home value update: what the agent believes the property is worth now, the three sales it is based on, and a one-line offer of a twenty-minute call if they want to talk about it. First anniversaries also get a small physical gift where the agent does that; the system creates the task and the address label.
6. Month 13. Because they never left a review after closing, the review recovery workflow sends one carefully worded ask referencing the anniversary rather than the transaction. They leave one. pc_review_left is ticked and pc-review-given applied, which permanently excludes them from every future review ask.
7. Month 15. The scheduled tag recalculation moves them from pc-year-1 to pc-year-2-4 and the pipeline stage to Years Two to Four. Touch frequency drops from roughly monthly to quarterly plus the anniversary. Nobody decides this; it just happens on the first of the month.
8. Year 2, month 4. The client forwards the referral form to a colleague who is relocating. The colleague submits it. A new lead is created with the referral source attached, pc_referrals_sent increments to 1, pc-referral-source is applied, and the client moves to the Referral Source stage - which raises their touch frequency back up and triggers a thank-you call task for the agent within twenty-four hours, because a referral thanked by automation alone is a referral you get once.
9. Years 2 to 4. Quarterly emails. One anniversary SMS and one annual value update per year. Two or three opens per year. No calls, no pressure, no effort from the agent beyond approving the quarterly content.
10. Year 5. Recalculation moves them to pc-year-5plus. Frequency increases: the quarterly email becomes every two months, and the annual value update gains a second line asking directly whether the house still fits.
11. Year 6, month 2. The client clicks the value update, then clicks through to two active listings on the agent's site in the same week, then opens the same email three times. The signal watch workflow fires: pc-signal-hot is applied, the stage moves to Signal Detected, pc_move_signal records exactly what they did, and the agent gets a notification naming the behavior.
12. No automated message goes out on the signal. Instead the agent gets a task due within four hours to make a personal call, and makes it. The client says they have been talking about moving for about a month and had not got round to doing anything about it. The agent is the first conversation they have had about it, rather than the fourth.
13. Year 6, month 2, three days later. A listing appointment is booked. The record moves to Re-engaged and then Returned Client, is handed to the seller pipeline, and leaves the past client program entirely so that no quarterly market email ever arrives in the middle of their own sale.
14. Meanwhile, elsewhere in the database. Forty clients have had zero opens, clicks or replies across a full year of sends. They are tagged pc-dormant, dropped to twice-yearly contact, and sent one honest message asking whether they would rather be removed. Eleven reply, which is eleven relationships recovered and twenty-nine addresses no longer damaging the sending reputation of every other email in the account.

Every workflow opens with the same two gates. The suppression gate: skip SMS if sms-opted-out, skip email if email-unsubscribed, exit entirely if pc-no-contact. The channel gate: read pc_preferred_channel and send only what it permits. A past client who asked for email only and receives a text has been told their preference does not matter, which costs more than the message was worth.

1. Enrollment and Year One Sequence

Trigger: past client enrollment form submitted, or a transaction record reaching Closed plus 45 days.

Actions in order:

1. Write pc_closing_date, pc_closing_year, pc_property_address, pc_client_type, pc_partner_name, pc_preferred_channel and pc_household_note.
2. Apply past-client, pc-year-1 and the client-type tag. Create the opportunity in Past Clients at Year One.
3. Remove the contact from every lead nurture and buyer sequence in the account. This step is skipped more often than any other and it is the one that causes a past client to receive a first-time-buyer drip.
4. Month 3: email, no ask: "{{first_name}}, how's the house treating you? You mentioned the bathroom - if you need a tiler, plumber or electrician I've got people I actually trust. Just reply and I'll send names."
5. Month 6: email with the two or three nearest sold results and one line on what the street has done since they bought.
6. Month 9: email with a seasonal home maintenance checklist appropriate to the climate and the property type. Useful, impersonal, and almost always opened.
7. Month 12: hand to workflow 2.
8. Stamp pc_last_touch_date on every send.

Exit: moves to Returned Client, or opt-out.

2. The Anniversary Touch

Why it exists: this is the spine of the program. One message a year that nobody else sends and that is impossible to resent.

Trigger: annually on the anniversary of pc_closing_date.

Actions:

1. At 9:00am local, send SMS: "{{first_name}} - {{anniversary_years}} years in {{pc_property_address}} today. Hope it's still the right house. {{agent_first_name}}" For a first anniversary: "One year in the house today, {{first_name}}. Still my favorite closing of that spring."
2. Where pc_partner_name is populated, address both people by name. Where pc_household_note contains something usable, the agent is prompted to add one line by hand before the send - a queued draft, not a blocked send, so a busy week does not break the chain.
3. Wait 6 hours. Hand to workflow 3 for the value update, so the anniversary carries something of substance and not only sentiment.
4. First anniversary branch: create a task to send a small gift, with the address pre-filled, due within three days.
5. Fifth and tenth anniversary branch: replace the SMS with a call task. Round numbers justify a human voice.
6. If pc_preferred_channel is Post only, add the contact to the monthly print export instead of sending anything digital.
7. Stamp pc_last_touch_date. On any reply, route to BO and move the stage to Re-engaged.

Exit: never - this runs for the life of the relationship. Suppressed only while the contact is a Returned Client.

3. Annual Home Value Update

Why it exists: it is the only message in the build that converts a sentimental touch into a business conversation, and it works because it is genuinely useful.

Trigger: 6 hours after the anniversary SMS, or manually on request.

Condition: pc_estimated_value_sent_date is more than 300 days ago.

Actions:

1. Create a task for the agent two weeks before the anniversary: Prepare value update for {{pc_property_address}}. The agent writes the figure. No automation in this build generates a property value.
2. Send email, subject "{{pc_property_address}} - {{anniversary_years}} years on": what the agent believes it is worth now, the three sales that view is based on, what has changed on the street, and one closing line - "No agenda in this. If you ever want twenty minutes to talk about what it would take to move, here's my calendar: {{equity_call_link}}"
3. Stamp pc_estimated_value_sent_date.
4. Branch on tag. For pc-year-5plus, add one direct question: "Honest question after five years - does the house still fit, or are you starting to think about the next one?" Years one to four get no such question; it is too early and reads as a pitch.
5. On any click of the calendar link without a booking, create a call task for the agent within one business day.
6. On a booking, move the stage to Re-engaged and suppress all program sends until the conversation resolves.

Exit: booking made, or next year's cycle.

4. Quarterly Market Email and Frequency Management

Trigger: first Wednesday of the quarter, plus a monthly scheduled recalculation on the first of the month.

Actions:

1. Recalculation step: for every past-client, compare today against pc_closing_date and set exactly one of pc-year-1, pc-year-2-4 or pc-year-5plus, removing the others, and move the pipeline stage to match. Never maintain these by hand.
2. Send step, segmented by tag. pc-year-2-4 receive the quarterly email. pc-year-5plus receive it every second month. pc-year-1 are excluded because workflow 1 is already covering them.
3. Content, in this order: two or three recent nearby sold results, one short plain-English market observation, one genuinely useful local item, and the referral form link in the signature rather than the body.
4. Exclude anyone tagged pc-signal-hot, pc-dormant or in the Re-engaged or Returned Client stages.
5. Stamp pc_last_touch_date on send and pc_last_engagement_date on any open, click or reply.

Exit: dormancy, unsubscribe, or return to active transaction.

5. Referral Loop

Trigger: referral submission form completed, naming a referring client.

Actions:

1. Create the new lead, attach the referral source, and route it to the agent with a priority flag. A referred lead is contacted the same day, always.
2. On the referring client: increment pc_referrals_sent, apply pc-referral-source, move the stage to Referral Source, and raise their send frequency one band.
3. Within 15 minutes, send the referring client an acknowledgement: "{{first_name}} - just got your intro to {{referral_first_name}}. Thank you, genuinely. I'll look after them and I'll let you know how it goes."
4. Create a call task for the agent, due within 24 hours, to thank them properly by voice.
5. When the referred lead's transaction closes, notify the referring client that it worked out, with permission from the new client first. Closing the loop is what produces the second referral.
6. Second and subsequent referrals: escalate the thank-you to a hand-written note task rather than another message.
7. Independently, once a year only, send every non-referring past client one soft referral ask built into the anniversary sequence. One per year. Never more.

Exit: none - the loop is permanent.

6. Review Recovery

Trigger: first anniversary reached and pc_review_left is false.

Condition: the contact is not tagged pc-dormant and has engaged at least once in the last six months - asking a disengaged client for a public review is how you get a mediocre one.

Actions:

1. Wait 7 days after the anniversary message, so the ask is not bundled with the warm one.
2. Send one email framed on the anniversary, not the sale: "{{first_name}}, a year on from {{pc_property_address}} - if the whole thing went well, a couple of lines where people can see them would genuinely help me. Takes two minutes: {{review_link}}. And if it didn't go well, tell me instead and I'll take it on the chin."
3. Wait 10 days. If no review is recorded, send one SMS reminder where the channel permits. Then stop permanently.
4. On a review being recorded, tick pc_review_left, apply pc-review-given, write the platform, notify the agent, and exclude the contact from every future review request in the account.
5. On any negative reply, suppress all review asks immediately and create an urgent call task. That is information worth far more than the review would have been.

Exit: review recorded, two asks made, or negative reply.

7. Signal Watch and Re-engagement

Why it exists: this is the workflow that pays for the program. Everything else keeps the relationship alive; this one catches the moment it becomes a transaction.

Trigger: any of the following within a rolling 14-day window - two or more clicks on property listings, a click on the value update calendar link, a reply to any program message, a submission of the equity update request form, three or more opens of the same email, or a visit to the valuation funnel by a known past client.

Actions:

1. Apply pc-signal-hot. Move the stage to Signal Detected. Write exactly what they did into pc_move_signal.
2. Send no automated message at all. This is deliberate and it is the most important rule in the build. A past client who has started quietly thinking about moving gets a phone call from someone they know, not a drip campaign.
3. Notify the agent by push and SMS with the signal described in plain language: "{{first_name}} {{last_name}} ({{pc_property_address}}, closed {{pc_closing_year}}) clicked two listings and your value update this week."
4. Create a call task due within 4 hours during business hours, or 9:00am next morning otherwise.
5. Pause every other program workflow for this contact for 30 days so nothing generic lands on top of a real conversation.
6. If the call connects and they are thinking of moving: move to Re-engaged, book the listing appointment or buyer consultation, then move to Returned Client and hand to the appropriate sales pipeline.
7. If the call connects and they are not: clear pc-signal-hot, return to the normal cadence, and note what they said in pc_move_signal so the next signal is read in context.
8. If the call does not connect after two attempts: send one short personal SMS from the agent - not from BO - then return to normal cadence after 14 days.

Exit: conversation held, or 30 days elapsed.

8. Dormancy and List Hygiene

Trigger: monthly, on the first of the month.

Actions:

1. Identify every past-client whose pc_last_engagement_date is more than 12 months ago despite having received at least six sends. Apply pc-dormant and move the stage to Dormant.
2. Drop these contacts to two sends a year: the anniversary message and the annual value update. Remove them from the quarterly email.
3. Once, send one honest message: "{{first_name}}, I've not heard from you in a while and I'd rather be useful than be noise. Want me to keep sending the yearly update on {{pc_property_address}}, or take you off the list? Either is completely fine." Then respect whichever answer arrives, including silence.
4. On any engagement from a dormant contact, clear pc-dormant, restore the normal cadence, and stamp pc_last_engagement_date.
5. At 24 months dormant with zero engagement and no reply to the honest message, remove the contact from all sends and move to Removed. Keep the record - they may come back - but stop emailing an address that is damaging deliverability for everyone else.
6. Report the counts monthly: active, dormant, removed. A past client database that is not being pruned is a database whose numbers are lying to you.

Exit: re-engagement, or Removed.

Staying in touch stops being a character trait and becomes a system. The agent no longer needs to be the sort of person who remembers anniversaries, because the anniversary is calculated from a date typed once, five minutes after a closing, and then fires every year for as long as the relationship lasts. The Christmas card that stopped after two years is replaced by something that does not stop.

The database starts producing work instead of sitting there. Every past client receives one genuinely useful thing a year - an honest view of what their house is now worth - and that single message does more than every generic newsletter combined, because it is specific to their address and it gives them a reason to reply. Replies become conversations, conversations become equity calls, and some of those become listings.

Most importantly, the agent stops finding out too late. The signal watch workflow means the moment a client who has been quiet for five years starts clicking listings, the phone rings before they have spoken to anybody else. That is the difference between being the obvious choice and being one of three agents they interview - and it happens without the agent having to notice anything.

A caution worth stating: this build is a relationship system, not a campaign. If the content becomes self-promotional the whole thing inverts and the database learns to ignore the sender. Keep the ratio honest - useful, useful, useful, then one ask.

Metrics to watch

• Enrollment rate - percentage of closings that reach the program within 60 days. Below total and the build has a hole in the top of it. This is the only metric that depends entirely on human discipline.
• Household note completion - percentage of records with pc_household_note populated. It correlates directly with reply rate, because it is what makes the messages read as personal.
• Annual engagement rate - share of past clients who opened, clicked or replied at least once in the last twelve months. This is the health metric of the whole database and the one to report monthly.
• Anniversary message reply rate, tracked separately from everything else. It should be the highest reply rate in the entire account.
• Value update open and click rate, and bookings generated from the equity call link.
• Signals detected per month, and the conversion from pc-signal-hot to a held conversation. Also watch how fast the agent actually makes the call - a four-hour task completed in four days is a build that is not being used.
• Returned clients per year and the share of total transactions they represent. Over several years this should become a meaningful fraction of the business.
• Referrals per past client per year, and the proportion of the database tagged pc-referral-source.
• Review coverage - share of past clients with pc_review_left ticked.
• Dormancy rate and recovery rate, plus the removed count, so the active number stays honest.
• Unsubscribe rate per workflow. In a past client program this should be very close to zero; anything more means the content has drifted from useful to promotional.

Prerequisites

• A clean list of past clients with real closing dates. This is the entire prerequisite and it is usually the hard part. Expect to spend time reconstructing dates from old files, and accept an approximate month where the exact day is gone - a message on the wrong day of the right month is infinitely better than no message.
• A decision on what the quarterly email actually contains and who produces it. Four pieces of content a year is a small commitment, and the program dies quietly if nobody owns it.
• The seasonal maintenance checklist and the trusted-trades list written before launch, since both are used in year one.
• A view on the annual value update: who prepares it, how long each takes, and how many land in each month. Spread the anniversaries across the year if the volume is large, or batch the preparation weekly.
• Whether there is a physical layer - cards, first anniversary gifts, a client event - and who handles fulfillment. The system creates the tasks and the address exports; somebody still has to post things.
• Written permission from any client whose closing you intend to post about publicly, recorded against the record. Assume no unless you have a yes.

Integrations

• Email sending domain authenticated with SPF, DKIM and DMARC. This matters more here than anywhere else in the business: you are emailing old addresses, some of which are dead, and poor list hygiene on a past client database will quietly damage the deliverability of every transactional message the account sends. Warm up a new domain slowly and clean before you send.
• Google Calendar or Outlook sync for the equity review and listing appointment calendars.
• Review platform connections for whichever two platforms matter most to the business, so a review being left can be detected rather than checked manually.
• Social planner connected to the business profiles for the public anniversary and sold-result posts.
• Optional: a direct mail or print fulfillment service fed by the monthly export, for the posted layer.
• Optional: a spreadsheet or CSV import path for the initial historical backfill, which is usually how the first few hundred records get in.

Number provisioning and messaging compliance

• Use the agent's existing A2P registered local number. These contacts already have it saved, which is most of why an anniversary text works rather than reading as spam.
• Complete A2P 10DLC brand and campaign registration before sending. Be accurate about the use case - relationship marketing to past customers - and expect the carriers to care about how consent was obtained.
• Consent on historical records is the real issue in this build. A client who closed six years ago and never agreed to marketing messages has not consented just because they were once a client. Before any backfilled contact is messaged, confirm you hold a lawful basis: documented consent at the time, or whatever the applicable rules permit for existing customer relationships in your jurisdiction. Where you cannot establish it, start with email only and earn the SMS consent explicitly.
• Honor STOP, UNSUBSCRIBE, END, QUIT and CANCEL automatically by applying sms-opted-out. Honor HELP with a reply naming the agent and the brokerage.
• Quiet hours 8am to 9pm in the contact's time zone, enforced at account level. Anniversary messages send at 9:00am local, never earlier.
• Every marketing email carries a working one-click unsubscribe and a physical mailing address, and the unsubscribe genuinely stops everything - a past client who unsubscribes and then receives the anniversary email has been given a reason to complain.

Compliance and data protection

• This database holds personal data on people who are no longer clients, which is exactly the category regulators pay attention to. Document why you retain it, for how long, who can see it, and how a deletion request is handled - and make sure the handling is real, not theoretical.
• Keep pc_household_note to harmless, useful detail: the dog's name, the renovation plan, that they work from home. It must never record health conditions, family circumstances, financial situations, or anything a client would be uncomfortable reading back. Write every note as though the client will one day see it, because they might.
• Do not record or segment on anything touching a protected characteristic. Fair housing obligations do not end at closing, and a long-horizon marketing program is exactly where thoughtless segmentation creates exposure.
• Never post a client's name, photograph, address or closing publicly without written permission on file.
• Automated messages must not state or imply a property value. Every figure in this build is written by a licensed human, and the message should make clear it is a market opinion and not a formal appraisal.
• Where a reply discloses a difficult circumstance - a death, a divorce, financial trouble - the build must stop and hand to a human with no follow-up queued. Check that behavior deliberately before launch; it is the most important test in the whole program.
• Confirm all of the above with the client's own attorney or broker compliance officer. Nothing here is legal advice, and consent, retention and marketing rules for existing and former customers vary considerably between jurisdictions.

Scoping

Database size, the state of the historical closing dates, how much of the content the client produces themselves, and whether a printed layer is included all change the build. To scope it against a real database, book a call at bookings.appbo.io.