Implementation Vault
How the System Thinks.
The intelligence behind each engine. Not what the system does, but how it decides what to do and why.
Engine 1
Capture Engine
How the system catches, qualifies, and routes every lead before anyone in the office needs to act. No lead leaks. No slow responses. No lost context.
How does the system handle a lead differently depending on where it comes from?
Every lead source triggers a different capture path. A portal enquiry, a website form, a social DM, and a missed call all enter the system through separate ingestion flows, each tailored to the channel the person used. What all of them share is that every lead, regardless of source, ends up normalised into the same format: name, contact, source, intent, and next action. The entry point is different. The destination is the same.
Why this matters
The system does not treat a DM the same as a phone call. Each channel has its own logic because each channel carries different context and urgency.
How does the missed call SMS know whether to text someone or not?
The system checks the incoming number against existing CRM records before sending the SMS. If the caller is already a known vendor, buyer, or landlord, the system either sends a different message or suppresses the text entirely. Callers also get a response preference: "text is fine" or "call me back." Callback requests create a timed task with escalation.
Why this matters
The auto-SMS is not a blunt tool. It filters, adapts, and routes based on who called. That is what separates it from a simple autoresponder.
How does the system qualify leads without a human being involved?
The system assigns qualification tags based on what it knows at the point of entry and then updates those tags over time based on behaviour. Qualification is not a one-time stamp. It is a living assessment. A "cold" contact who opens three emails and clicks a valuation link gets upgraded without manual intervention. Qualification adapts to behaviour, not just initial data.
Why this matters
The system never guesses once and commits. It keeps refining its understanding of each lead as more data comes in.
What happens if nobody picks up a lead in time?
The system runs an escalation ladder. First a reminder, then a manager notification, then optionally a reassignment to another team member. The SLA clock starts the moment the lead enters the system and does not stop until a human responds. The escalation ladder is configurable: how long before a reminder, how long before the manager is pinged, and whether automatic reassignment is turned on. The system treats speed as a process issue, not a people issue.
Why this matters
No lead sits unnoticed. The system escalates quietly and reassigns intelligently so the team gets faster without working harder.
What happens to phone calls after they end?
Every inbound and outbound call is transcribed and summarised automatically. A structured 6-line summary is saved to the lead record covering why they called, their intent, urgency, objections, what was promised, and the next follow-up date. This eliminates lost context, forgotten details, and messy handwritten notes. It also protects the agency in disputes because there is a factual record of what was discussed.
Why this matters
Call summaries mean no one has to rely on memory. The system captures and structures the conversation so the CRM record is always accurate.
What happens when someone enquires outside office hours?
The system runs an after-hours front desk flow. It acknowledges the enquiry, captures intent, offers booking or callback options, and logs everything for the morning. The lead never experiences silence. By the time the office opens, every out-of-hours enquiry has intent tagged, contact details captured, and tasks created. The team starts with a clear list instead of a messy inbox.
Why this matters
Evenings and weekends stop being a dead zone. Leads that arrive at 9pm are captured and ready for 9am.
Engine 2
Revive Engine
How the system turns old, stalled, and forgotten contacts into live opportunities. No endless "checking in." No CRM graveyards. No false hope.
How does the system decide which old contacts are worth reviving?
Not everyone in the database gets the same outreach. The system tags contacts with revival readiness categories based on why they went cold, how long ago it was, and what their last interaction looked like. Only contacts above a revival probability threshold enter the active revival sequence. Below that threshold, they sit in passive monitoring. The system does not waste messages on contacts with almost no chance of re-engaging.
Why this matters
Revival is situational, not blanket. The system treats different stall reasons differently because the same message does not work for all of them.
How does the system know if someone is quietly paying attention without replying?
The Silent Seller Detection Engine tracks engagement signals that fall short of a reply: link opens, repeated message reads, delayed clicks, and patterns of quiet engagement over time. These contacts are flagged internally but not escalated aggressively. They are some of the highest-converting sellers because they have been thinking quietly and are often further along in their decision than someone who replies immediately.
Why this matters
Most agencies miss silent sellers entirely because they only look for replies. The system watches for a wider set of engagement signals.
How does the system interpret a reply to a revival message?
The system categorises replies by intent, not just by the fact that a reply happened. "Not right now" is treated differently from "yes, I am interested" and differently again from "stop contacting me." The system recognises hidden signals too. A question is not the same as an objection. "What would my house be worth now?" is categorised as curiosity, not resistance, even though it does not contain the word "yes."
Why this matters
The system prevents agents from chasing people who are actually asking for space, which is a massive trust and time saver.
What happens to a revived contact when they re-enter the pipeline?
Revived contacts do not re-enter the pipeline at the same point as a fresh enquiry. Their re-entry point reflects their emotional state: cautious, curious, or ready. The system creates a grounding action task so the agent does not have to improvise. This prevents the common mistake of treating a revived seller like a brand new lead. They have history with your agency. The system respects that history and adjusts the approach.
Why this matters
Revived contacts are handled with the nuance their situation requires, not forced into a generic new-lead process.
How does the system prevent revival outreach from becoming spam?
Three mechanisms. Entry gating prevents low-probability contacts from entering the sequence. Early-exit logic stops the sequence automatically if there is no engagement by a configured day. Auto-suppression quietly retires contacts who never engage across multiple reactivation cycles. Every revival contact is forced into one of three outcomes: active, deferred, or closed. There is no "floating" state. The system does not allow contacts to sit in limbo indefinitely.
Why this matters
Revival recovers value without annoying people. The system knows when to stop, which is the part most manual revival efforts get wrong.
How does the system track whether revival is actually generating revenue?
The Revival ROI Attribution Layer tracks which instructions originated from revival sequences. It records recovered fees, average revive-to-instruction time, and which revival paths perform best. It is what proves the system is not "soft nurture" but a revenue mechanism. Every instruction that came from a contact who was previously dormant is tracked back to the revival sequence that reactivated them.
Why this matters
Revival is measurable. The system knows exactly how much revenue came from contacts that would otherwise have sat in the database doing nothing.
How does the system adapt revival tone based on why someone stalled?
The Emotional Stall Pattern Library categorises stalls across the database into types: fear-based, comparison-based, fatigue-based, and timing-based. The system uses these categories to adjust revival tone and timing without agents needing to think about the psychology. Agents never see the stall categories directly. The system handles the adaptation internally and surfaces the contact when it re-engages, with the right emotional context already applied.
Why this matters
The system does not send the same revival message to everyone. It reads the history and adjusts, which is why revival contacts feel personally approached rather than batch-processed.
Engine 3
Valuation Engine
How the system converts seller curiosity into booked valuations and clean decisions. Without pushing, chasing, or inflating expectations.
What does the system capture beyond the price estimate when someone uses the valuation tool?
The system captures language framing (hopeful, cautious, comparative), expectation posture (optimistic, neutral, defensive), and confidence delta: how certain they sound versus how certain they actually are. This shapes every follow-up message. Someone with realistic expectations receives different content than someone who needs gentle grounding before a conversation about pricing is safe.
Why this matters
The system captures psychology, not just property data. Every follow-up is safer and more relevant because of what was learned at the point of entry.
How does the system decide when a seller is ready to book a valuation?
The system tracks what it calls valuation gravity: whether a seller is drifting away, stabilising, or pulling forward. The booking mechanism only presents itself when the gravity signal is right. Some sellers are nudged to talk first, not book. Others are gently fast-tracked. The system respects different decision styles.
Why this matters
The system increases conversion quality, not just booking volume. A well-timed valuation converts at a much higher rate than a premature one.
How does the system prepare the seller before the valuation appointment?
The Expectation Alignment layer delivers market framing, price realism, and process clarity to the seller before the valuer arrives. It does this without giving specific numbers and without creating confrontation. This single layer protects fees, confidence, and post-valuation momentum. The valuer is not starting from scratch. They are building on a foundation the system already laid.
Why this matters
Expectation mismatches at valuation are the biggest source of lost instructions. The system reduces those mismatches before the appointment happens.
What happens after the valuation if the seller goes quiet?
The Post-Valuation Decision Compression Flow prevents valuations from drifting into silence. The system detects why silence occurred: avoidance, comparison, fear, or indecision, and adapts its follow-up tone accordingly. The outcome is always clean: instruct, defer with structure, or close respectfully. The system does not allow post-valuation limbo to persist.
Why this matters
Every valuation ends in truth, not limbo. The system resolves outcomes that most agencies leave floating indefinitely.
Can the system predict whether a valuation will convert before it happens?
The Valuation Outcome Inevitability Map produces internal-only predictions based on behaviour, language, and engagement patterns. It outputs three likelihood assessments: strong instruction, fragile instruction risk, and delay probability. The valuer can see a summary of the prediction if they check the CRM before the appointment. It helps them walk in prepared rather than hopeful.
Why this matters
Agents walk into valuations with context about the likely outcome. The system has already read the signals that most people only see in hindsight.
Engine 4
Demand Engine
How the system turns real buyer behaviour into seller confidence and instruction inevitability. No hype, no exaggeration, no "we have got loads of buyers" theatre.
How does the system separate real buyer demand from noise?
Buyers are segmented by seriousness (active, conditional, browsing), flexibility (price, area, timing), and frustration level (fresh, fatigued, pressured). On top of that, a credibility scoring layer weights demand by funding readiness, decisiveness history, prior drop-out behaviour, and compromise velocity. Only credible demand is surfaced to sellers. The system filters out noise so that when demand is communicated, it is honest and convincing rather than inflated and hollow.
Why this matters
Sellers trust restraint far more than excitement. The system protects that trust by never overstating what buyer demand actually looks like.
How does the system turn buyer behaviour into language that sellers can trust?
The Demand-to-Seller Translation Engine converts raw buyer activity into seller-safe language. Instead of "we have 12 buyers registered," the output is something like "we are seeing buyers stretch on condition, not price" or "interest is strong, but patience is being tested." Most agents show demand. The system interprets it. The difference is that interpretation creates confidence while raw data creates confusion.
Why this matters
Sellers make decisions based on how demand feels, not how many buyers are registered. The system communicates demand in a way that informs rather than pressures.
How does the system detect the right moment for a seller to act?
The Instruction Timing Amplifier monitors buyer frustration density, repeat viewings, and missed-offer clusters. When conditions align, the system delivers grounded context to the seller and cues the agent to act calmly. The timing is never artificial. The system amplifies what is actually happening in the market, not what the agency wishes was happening.
Why this matters
It improves timing without creating urgency addiction. Sellers act because the conditions are right, not because they were pressured.
How does the system use demand to protect fees?
The Fee Justification Demand Layer uses buyer behaviour complexity to defend fees. Instead of justifying fees with confidence ("we are worth it"), the system frames them through execution risk ("here is what poor handling would waste"). Fees are justified through complexity, not confidence. The system provides the ammunition for fee conversations by framing them around what the seller would lose, not what the agent would gain.
Why this matters
Fee conversations shift from "trust me, I am good" to "here is what is at stake if this is handled poorly." The system makes that case with data.
How does the system build a pipeline of future sellers who are not ready yet?
The Off-Market Seller Pipeline captures future sellers based on curiosity signals, buyer pressure exposure, and timing ambiguity. These are people who are not ready to sell but are paying attention. This builds instruction gravity months before competitors notice. By the time these sellers are ready, your agency has been present in the background for weeks or months.
Why this matters
Most agencies only chase active sellers. The system captures future sellers while they are still thinking, which is where the highest-quality instructions come from.
How does the system recycle demand from failed offers?
The Under-Offer Demand Recycle Flow captures the emotional frustration, urgency spike, and compromise readiness of buyers who just lost a property. That energy is redirected into seller-facing demand signals, off-market conversations, and pre-listing confidence. Disappointed buyers become the strongest persuasion asset for future instructions because their frustration is real, current, and measurable.
Why this matters
Missed offers are not dead ends. The system recycles the energy from them into commercial value elsewhere in the pipeline.
Engine 5
Decision and Loyalty Engine
How the system ensures every valuation ends in a decision, every instruction is stabilised, and every completed client feeds the future pipeline. No limbo. No chasing. No silent instruction loss.
How does the system protect newly signed instructions from falling apart?
The Instruction Stabilisation Layer detects early risk signals after a seller instructs: reduced responsiveness, comparison language, price defensiveness, and portal obsession. The system adjusts update tone, reassurance cadence, and agent involvement level before the wobble becomes a withdrawal. The system catches these signals early and responds with stability: calm updates, grounded reassurance, and strategic agent involvement. It does not panic. It stabilises.
Why this matters
The gap between instruction and confidence is where most agencies lose fees. The system closes that gap before the seller starts looking elsewhere.
How do vendor updates adapt to the seller's emotional state?
Update cadence and tone adapt based on instruction fragility, price sensitivity, engagement decline, and anxiety markers. Updates shift from "here is what happened" to "here is what matters." The vendor feels consistently supported regardless of what is happening in the market, because the system calibrates its communication to their state.
Why this matters
Vendor updates that ignore emotional context make anxious sellers more anxious. The system prevents that by matching tone to temperature.
How does the system prevent fee erosion?
The Fee Integrity Protection System monitors for discount language, competitor mentions, and justification pressure. When these signals appear, the system reinforces complexity framing, execution risk, and value narrative before the fee conversation escalates. Fees are defended before they are questioned.
Why this matters
Most fee negotiations are lost before they start because nobody noticed the early warning signs. The system notices.
How does the system turn completed clients into future revenue?
The Lifetime Value Loop Engine maps every completed client into potential future roles: seller to landlord, seller to buyer, buyer to seller, client to advocate. Re-engagement points are contextual and timed to life-stage transitions, not arbitrary drip campaigns. No push. No drip. Just contextual re-entry points that feel natural because they are timed to the moment the person is most receptive.
Why this matters
One transaction becomes an ecosystem. The system ensures no completed client is ever truly "done."
How does the system catch disengagement before it becomes a lost instruction?
The Silent Disengagement Detector flags polite silence, delayed replies, and emotional flattening. These are the early warning signs that a vendor is mentally withdrawing before they formally tell you. When these patterns are detected, the system triggers a grounding intervention, an expectation reset, or release logic if the instruction is genuinely unrecoverable. The goal is to address the drift while it is still fixable.
Why this matters
The system catches the emotional withdrawal that precedes the formal one. That early detection is the difference between saving an instruction and receiving a cancellation call.
How does the system decide when to stop pursuing a seller?
The Close-or-Convert Decision Logic defines when to pursue and when to step back. Decision rules account for market volatility, seller psychology, and agent bias toward over-chasing. The system prevents pursuit when probability collapses. The outcome is always clean: instruct, defer with structure, or close respectfully. No limbo. No endless follow-up.
Why this matters
Knowing when to stop is as valuable as knowing when to push. The system removes the emotional bias that makes agents chase too long.
Engine 6
System Intelligence and Protection
How the system maintains its own integrity over time. It resists human drift, absorbs emotional volatility, and stays effective without constant intervention.
How does the system detect when people are quietly undermining it?
The System Drift Monitor tracks manual overrides, SLA bypassing, tagging inconsistency, automation interruptions, and staff workarounds. Drift is classified as accidental, defensive, convenience-driven, or belief-based, and each type has a different correction path. When override patterns are detected, the system responds by slowing cadence, reasserting system ownership, and preventing over-contact. It protects itself from the agent without confrontation.
Why this matters
Most systems fail quietly over time as people develop workarounds. This system notices the drift and corrects for it.
How does the system handle seller anxiety without escalating it?
The Seller Anxiety Absorber detects urgency language, reassurance-seeking behaviour, comparison panic, and sudden silence after engagement. It responds by softening cadence, inserting reassurance framing, and stabilising expectations. This prevents trust erosion before it becomes visible. By the time most agents notice a seller is anxious, the damage is already done. The system catches it earlier.
Why this matters
Anxiety is dampened, not amplified. The system absorbs emotional spikes instead of reflecting them back.
How does the system show health without creating performance pressure?
The Invisible Performance Gradient uses four internal-only states: stable, settling, noisy but normal, and intervention required. No targets. No rankings. No leaderboards. No vanity metrics. The Market Noise Filter adds protection against external panic: headline-driven anxiety, social media speculation, and competitor chatter. The system prevents the agency from chasing the news cycle with reactive messaging.
Why this matters
System health is communicated without creating the pressure that causes the very drift the system is trying to prevent.
How does the system prevent people from pushing it too hard?
The System Boundary Enforcer prevents premature acceleration, misuse of CTAs, escalation outside readiness, and over-optimisation attempts. It is the engine that says "not yet." Constraint is what preserves power. The system knows that the most common form of system damage is well-intentioned interference, and it actively resists it.
Why this matters
The system protects itself from enthusiasm as much as neglect. Both can cause drift. The boundary enforcer keeps things within the design limits.
How does the system protect vulnerable instructions from collapsing?
The Instruction Fragility Map monitors communication gaps, price defensiveness, expectation mismatch, portal obsession, and comparative language across all active instructions. When vulnerability signals cluster, the system adjusts tone, cadence, and agent involvement level. The system watches for the slow deterioration that humans miss because it happens gradually. By the time the signs are obvious, the instruction is often already lost.
Why this matters
The system protects instructions across their full lifecycle, not just at the point of signing. Fragility can emerge at any stage and the system watches for it continuously.
What intelligence does the system aggregate for Bazema as your steward?
The Bazema Steward Layer aggregates system intelligence across all engines: drift patterns, misuse risk, churn signals, future upsell readiness, and system health over time. This data is used by Bazema to protect outcomes and adjust the system proactively. When Bazema recommends a change, the recommendation is backed by aggregated intelligence from this layer. It is how outcomes are protected and stewardship scales.
Why this matters
The system does not just run. It reports. Bazema uses that reporting to stay ahead of problems and keep the system performing over time.
"The system follows its rules.
When something seems off, check the data it acted on."
Bazema Operating Principle
%20(1).png)