An estate agency needs to know what a caller wants before deciding who should respond. For a Zanus AI CRM trial, separate buyer enquiries, seller appraisal requests and existing-client updates. Useful intake records the customer’s stated request and property context without inventing intent or making a sales decision on the caller’s behalf.

Use distinct routes for distinct requests

A buyer asking about a listing needs current property information and possibly a viewing. A seller asking for an appraisal needs the right valuer and a property address. An existing client asking for an update should reach the person handling the open instruction.

Write an intake route for each and keep uncertain cases available for staff review. Do not force someone to fit a sales category when the actual request is an administrative update or complaint.

Store what the caller actually said

Request typeUseful information
Buyer enquiryListing reference, stated question and callback preference
Seller appraisalProperty address, requested next step and owner
Existing clientOpen instruction or case reference and named agent
Unclear requestCaller’s own description and a review task

Keep unknown fields unknown. A tentative moving date is not a firm deadline, and a question about a listing is not proof that a viewing was requested.

Test a caller with two roles

Use a test customer who is selling one property and enquiring about another. Check that the CRM preserves two related opportunities rather than merging their purposes into a single note. Then call about an existing sale from a second phone number.

Ask staff to inspect the resulting records without listening to the calls first. They should be able to identify the right property, the requested next step and who owns it. Wrong-property matches deserve explicit review even when the customer identity is correct.

Assess usefulness at the agent’s desk

Measure whether agents can respond without repeating basic intake, how often leads are routed incorrectly and whether agreed callbacks happen. Keep appointment requests separate from confirmed viewings and completed appraisals.

Have the agency approve its questions, information access and routing policy before using real callers. The first pilot should improve administrative clarity. It should not introduce unsupported automated judgments about which customers deserve service.

Questions and answers

Should one customer have only one CRM opportunity?

Not necessarily. A buyer enquiry and a separate sale can require different property records, owners and next steps linked to the same customer.

Mapping the Estate Agency Enquiry Before It Reaches a Record

Every inbound contact arrives with a gap between what a caller says and what the agency needs to know. Closing that gap administratively, before a negotiator picks up the thread, is where a CRM routing arrangement either earns its place or creates rework. This guide establishes that buyer enquiries, seller appraisal requests and existing-client updates should travel separate routes. This companion section examines how to design and stress-test those routes in detail, how to handle the cases that do not fit neatly, and how to prepare the agency's staff to evaluate whether the resulting records are genuinely useful.

A useful way to frame this work is to think of three distinct objects that a CRM must handle: the customer identity, the individual request and the responsibility for acting on it. These three things do not always align in an obvious way. A caller may be the correct person on record, may state a clear request, and yet the responsibility for responding may sit with a colleague who is currently unavailable. A system that conflates these objects will produce records that are technically complete but operationally confusing. Keeping them distinct at the design stage reduces that risk.

Designing the Intake Record Around the Request, Not the Customer Type

A common design temptation is to build intake forms around the customer category rather than the stated request. The result is that a landlord who telephones about a maintenance matter on a property that is also for sale gets routed to the sales team because the CRM recognises a vendor record. The caller's actual request, which concerns lettings management, gets lost or delayed.

A more robust approach starts with the stated request as the primary field, then links the customer identity and the responsible person as secondary attributes. In practice, this means the first thing the intake record captures is a plain-language summary of what the caller said they needed, without categorising it. A staff member or automated routing step then applies a category, and that categorisation is visible and reversible.

Consider an illustrative scenario. A caller gives their name and says they want to know whether an offer has been accepted on a flat they viewed last week. That is a buyer enquiry about a specific transaction in progress, but it is also a request for an update on an existing open negotiation. If the CRM routes it purely as a buyer enquiry, it may land with a front-of-house team member who has no visibility into the negotiation. If it routes as an existing-client update, it may reach the negotiator handling the sale, which is the correct destination. The routing decision depends on whether the system can distinguish between a general buyer enquiry and a post-offer status check. That distinction is worth specifying explicitly in the routing policy before the system goes live.

Structuring Seller Appraisal Requests to Protect Valuer Time

Appraisal requests place particular demands on intake quality because the stakes for a mismatch are high. A valuer who attends a property without the correct address, the correct point of contact, or an understanding of whether the owner wants a formal market appraisal or an informal estimate will waste time that the agency cannot recover. The intake record for an appraisal request should therefore be treated as a pre-qualification document, not just a callback note.

The minimum useful content for an appraisal intake record includes the full property address as stated by the caller, the caller's relationship to the property (whether they describe themselves as the owner, a co-owner, a solicitor acting on behalf of an owner, or something else), the type of appraisal they are requesting, and any timing constraints they have mentioned. Each of these fields has a distinct operational consequence. A caller who identifies as a solicitor changes who should receive the callback. A caller who says they need a valuation within a specific window changes scheduling priority. A caller who is uncertain whether they want to sell changes the framing of the follow-up conversation entirely.

In evaluation, it is worth asking whether the intake arrangement captures these nuances or flattens them into a single appraisal category. A reviewable sample record should make each of those distinctions legible to a valuer who has not heard the original call.

Handling Existing-Client Contacts Without Losing Continuity

Existing-client contacts carry a different risk from new enquiries. With a new enquiry, the cost of a routing error is typically a delayed response. With an existing client, a routing error can interrupt a relationship that the agency has already invested in building. A vendor who telephones for an update on their sale and is treated as an unrecognised new enquiry will notice, and the experience undermines confidence at a moment when confidence matters.

The operational challenge is that existing clients rarely identify themselves as such at the start of a call. They may give a property address rather than a case reference. They may give a first name only. They may telephone from a number the agency does not hold. Any of these situations can cause a matching failure even when the caller is well-known to the agency.

A practical evaluation exercise for this scenario involves staging a call from an unregistered phone number on behalf of a fictional client whose property record exists in the system. The caller gives the property address and the name of their handling agent. The question for evaluation is whether the resulting intake record correctly links to the open instruction and flags it for the named agent, or whether it creates a new unmatched record that sits unresolved. Both outcomes are informative. A new unmatched record with the property address and agent name clearly noted is a manageable outcome if a staff member reviews it promptly. A new unmatched record with only a phone number and no property context is a more serious gap, because it cannot be resolved without calling the client back to ask questions they have already answered.

A Worked Fictional Enquiry: The Dual-Role Caller

Consider a fictional caller, referred to here as the caller, who telephones an estate agency on a Tuesday morning. The caller states that they are currently selling their flat through the agency and also want to register an interest in a house that appeared on the portal over the weekend. The call lasts several minutes and covers both topics.

At the end of the call, the agency's CRM should ideally contain two linked records: one attached to the open sales instruction for the flat, noting that the caller is seeking an update on progress, and one registering a buyer enquiry for the portal listing, noting the specific listing reference and the fact that the caller wants to arrange a viewing. The responsible person for the first record is the negotiator handling the flat sale. The responsible person for the second is whoever manages buyer enquiries for that listing's area or price range.

When evaluating whether an intake arrangement handled this correctly, a reviewer should be able to open both records without having listened to the call and answer the following questions. Which property is the subject of each record? What did the caller ask for in relation to each? Who is responsible for the next action on each? Are the two records linked to the same customer identity without being merged into a single opportunity? If the reviewer cannot answer all four questions from the record alone, the intake arrangement has produced incomplete operational output regardless of whether it captured the call.

Staff conducting this review should approach it as a practical test rather than an audit. The goal is to identify which fields are missing or ambiguous so that the intake template can be adjusted before real callers are involved.

Defining and Reviewing Unclear Cases

No routing policy eliminates unclear cases, and a routing system that forces every contact into a defined category will misclassify some of them. The more useful design choice is to define what constitutes an unclear case, decide how those cases are held and reviewed, and specify who makes the final routing decision when automated classification is insufficient.

Unclear cases in an estate agency context tend to fall into recognisable patterns. A caller who asks a general question about the market without mentioning a specific property or instruction is neither a buyer enquiry nor a seller appraisal request in the operational sense. A caller who says they are thinking about moving but has not decided is a speculative contact whose value to the agency is real but whose routing is genuinely ambiguous. A caller who is unhappy about something but has not stated what is potentially a complaint, a request for information, or a misunderstanding about a process, and all three require different responses.

For each of these patterns, the agency should decide in advance whether the intake record is assigned to a staff queue, held for a named reviewer, or passed to a duty negotiator on a rotating basis. The decision matters not because any one approach is correct but because an unclear case that sits unassigned for an extended period represents a lost contact. Building an explicit review step into the routing policy, with a defined timeframe and a named owner for the review queue, closes that gap.

Comparing Routing Arrangements: Criteria That Change the Decision

When an agency is evaluating how to configure intake routing, several criteria are worth examining in sequence rather than simultaneously, because they interact.

The first criterion is whether the routing categories match the agency's actual workflow rather than a generic sales pipeline. An agency that operates a dedicated lettings department alongside sales needs intake routing that can distinguish a lettings enquiry from a sales enquiry at the point of capture, not after a negotiator has already spent time with the contact. An agency that operates a single team handling both has a simpler requirement.

The second criterion is how the arrangement handles volume variation. During a busy period, the review queue for unclear cases may grow. The evaluation should test what happens to unreviewed records after a defined interval and whether the system surfaces them for follow-up or leaves them to age silently.

The third criterion is how errors are corrected. If a buyer enquiry is routed to the appraisal team in error, what does the correction process look like? Can a staff member reclassify the record and reroute it without losing the original intake information? The answer to this question affects how much damage a routing error causes in practice.

The fourth criterion is whether the intake record supports the agency's callback commitments. If the agency undertakes to return calls within a specific window, the intake record should capture when the contact arrived so that elapsed time is visible. Without that, the commitment cannot be monitored.

Acceptance Criteria for an Intake Arrangement Before Live Use

Before any intake arrangement is used with real callers, the agency should be able to demonstrate observable evidence against a set of acceptance criteria that staff have agreed in advance. The following criteria are suggested as a starting point for that agreement.

  • A buyer enquiry referencing a specific listing produces a record that identifies the listing, the question asked and the caller's preferred contact method, without requiring a negotiator to ask for any of those details again.
  • A seller appraisal request produces a record that includes the property address as stated, the caller's relationship to the property and the type of appraisal requested.
  • An existing-client contact produces a record that links to the open instruction and identifies the responsible negotiator, even when the caller telephones from an unregistered number.
  • A dual-role caller produces two linked records rather than one merged record or two unlinked records.
  • An unclear case produces a record that captures the caller's own description of their request and assigns a review task to a named staff member.
  • A staff member who has not heard the original call can identify the correct property, the requested next step and the responsible person from the record alone.

These criteria are observable rather than subjective. Each one can be tested with staged calls before the arrangement handles real contacts. Where a criterion is not met, the specific gap can be identified and addressed in the configuration or the intake template, which is a more productive outcome than discovering the gap through a live customer complaint.

Handover Arrangements Between Intake and Negotiation

The intake record is the beginning of the relationship with a contact, not the end of it. The handover from intake to the negotiator or valuer who will follow up is where many of the practical benefits of careful intake design are either realised or lost. A well-structured intake record that is handed over without context, or that sits in a queue the receiving negotiator has not checked, produces the same outcome as a poor intake record.

A useful handover arrangement specifies the trigger for the handover (such as the arrival of a record in a particular category), the channel through which the negotiator is notified (such as an in-system task or a team message), the information the negotiator is expected to review before responding, and what to do if the negotiator is unavailable. That last point is worth particular attention. If the responsible negotiator is out of the office when a callback-urgent record arrives, the handover arrangement should specify who takes responsibility and how the original negotiator is informed when they return.

Evaluating this in practice means staging a handover during a time when the nominally responsible staff member is unavailable and observing what actually happens to the record. The result tells the agency whether its escalation path works as designed or whether urgent contacts would be delayed without a visible reason.

Careful intake design, explicit routing policy, reversible categorisation and a tested handover arrangement together give an estate agency a foundation for evaluating whether an AI-assisted CRM arrangement adds administrative clarity. The measurable question at the end of a pilot is straightforward: can a negotiator pick up any record in the system and know what the caller needed, which property it concerns and what the agreed next step is, without making a further call to find out?

Sources and next steps

This independent Sysevo guide proposes evaluation steps, not hands-on Zanus AI results. Check the official Zanus AI Front Office overview and ask the vendor to demonstrate your exact workflow and confirm its current availability.

For related context, read Zanus AI CRM integration and lead handoff. To compare providers using the same requirements, explore Sysevo CRM or book a Sysevo demo. Sysevo publishes this guide and sells its own business software.

Related workflow guides

For current Sysevo subscriptions and usage options, compare plans and pricing.