Qualify property enquiries before handing off appointment booking
A real-estate business combined a scripted messaging agent with a human appointment team so brokers received booked meetings rather than an unmanaged queue of new enquiries.
How this works
A real-estate business combined a scripted messaging agent with a human appointment team so brokers received booked meetings rather than an unmanaged queue of new enquiries.
Use messaging to collect stated property requirements and prepare a reliable handoff to a human appointment team. Keep listing facts current and distinguish a viewing preference from an actually confirmed appointment.
Before you start
Defined operating scope
Property enquiries require bounded qualification before a human completes appointment booking.
Required source material
Obtain Inbound property enquiry; Approved property information; Qualification and handoff rules. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The property’s availability is stale. Ask the responsible team to verify before offering a definite viewing.
Prepare the inputs
- enquiry
- Required
Contact, property interest and source
Verify the requested communication context.
- property_reference
- Required
Approved listing facts and availability
Record update dates and unit identity.
- qualification_rules
- Required
Required needs and constraints
Use relevant stated criteria, not sensitive inferred traits.
- booking_handoff
- Required
Appointment team and required fields
Define receipt and confirmation states.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check enquiry, property_reference, qualification_rules, booking_handoff before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected enquiry and any missing required fields.
Respond to the enquiry and gather the required qualification details
- Disclose the assistant and collect the requested location, property type, timing and other approved qualification details.
- Check all property facts against the exact listing and freshness date.
Checkpoint: A saved intermediate result for: Respond to the enquiry and gather the required qualification details.
Answer bounded questions and share approved property material
- Answer using the selected listing’s current facts, flagging unavailable prices or availability instead of guessing.
- Verify booking receipts and distinguish requested, offered and confirmed times.
Checkpoint: A saved intermediate result for: Answer bounded questions and share approved property material.
Record the conversation and update the CRM
- Save the conversation and qualification record in the correct CRM context, retaining unanswered questions.
- Check all property facts against the exact listing and freshness date.
Checkpoint: A saved intermediate result for: Record the conversation and update the CRM.
Have an appointment specialist complete scheduling and hand off to the broker
- Send the appointment team a complete handoff and report a viewing as booked only after human or system confirmation.
- Verify booking receipts and distinguish requested, offered and confirmed times.
Checkpoint: A saved intermediate result for: Have an appointment specialist complete scheduling and hand off to the broker.
Package the result and unresolved work
- Review scripts and escalation rules, disclose automation, and verify appointment details. The source’s human impersonation and unverified conversion claims are excluded.
- Disclose automation and avoid discriminatory or sensitive personal inference.
Checkpoint: A qualified enquiry with a human-confirmed appointment and CRM context. Unresolved items remain visible in the review record.
Decisions along the way
The property’s availability is stale.
Ask the responsible team to verify before offering a definite viewing.
The prospect proposes a time but no slot is confirmed.
Record a preference and keep appointment status pending.
The request exceeds the approved property script.
Escalate to a human rather than inventing terms or eligibility judgments.
What you will produce
qualify-property-enquiries-before-human-booking-result.json
JSONA qualified enquiry with a human-confirmed appointment and CRM context. Label proposed and completed states separately.
Include: enquiry_id · property_id · stated_requirements · unanswered_questions · viewing_preference · handoff_status · confirmed_appointment · status · evidence_reference · review_note
qualify-property-enquiries-before-human-booking-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving booking_handoff.
Include: source_reference · question · owner · next_action
Check the result
- Check all property facts against the exact listing and freshness date.
- Verify booking receipts and distinguish requested, offered and confirmed times.
- Inspect enquiry and property_reference in both the original and output; confirm that record identity and interpretation survived the transformation.
- Review scripts and escalation rules, disclose automation, and verify appointment details. The source’s human impersonation and unverified conversion claims are excluded.
When something goes wrong
The property’s availability is stale.
Ask the responsible team to verify before offering a definite viewing. Retain the affected evidence and recovery status.
The prospect proposes a time but no slot is confirmed.
Record a preference and keep appointment status pending. Retain the affected evidence and recovery status.
The request exceeds the approved property script.
Escalate to a human rather than inventing terms or eligibility judgments. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Qualify property enquiries before handing off appointment booking for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Prospect E-7 wants a two-bedroom unit and prefers Saturday afternoon. Listing L-2 was last checked a week ago; no appointment slot is confirmed.
Expected result
Synthetic expected result: Record requirements and Saturday preference, flag availability verification and pass to the appointment specialist. Do not tell the prospect the viewing is booked.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure accurate qualification records; human-booked appointments and failed handoffs.
Stop or revise
The request exceeds the approved property script. Pause affected records and apply this recovery: Escalate to a human rather than inventing terms or eligibility judgments.
Keep the scope clear
- Disclose automation and avoid discriminatory or sensitive personal inference.
- Humans handle appointment confirmation and consequential commercial exceptions.
Check before using
Review scripts and escalation rules, disclose automation, and verify appointment details. The source’s human impersonation and unverified conversion claims are excluded.
Business activities
- Handle inbound enquiries
- Run sales conversations and proposals
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Inbound property enquiry · Approved property information · Qualification and handoff rules
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow