Property Enquiry Qualifier
Slug: ai-property-enquiry-qualifier · Category: Lead Capture & Booking · Provisioning: Requires AgentLane staff approval
Grades an incoming property enquiry, books the viewing time the enquiry asks for on Cal.com when it includes a name and email, and emails the listing agent a plain-language summary. It does not match the enquiry against your listings — there is no listings lookup anywhere in the flow.
Required credentials
| Provider | Used for |
|---|---|
anthropic | Scores and qualifies the enquiry |
postgres | Legacy, unused. No step in this flow reads or writes Postgres — there is no listings-table lookup. See the note below. |
cal_com | Books the requested viewing (POST /v2/bookings) |
resend | Emails the listing agent the qualification summary |
Which AI actually runs this: AgentLane’s own managed Google Gemini models on Vertex AI. No Anthropic or OpenAI key is read for inference. The
anthropicrow above is a legacy credential requirement kept so existing rows and portal chips keep working — it is never checked before provisioning. See AI Models & Credits.
postgresis not used either. No catalog flow contains a Postgres step, so this agent writes nothing to a database of yours. The requirement is declared for historical reasons and is skipped before provisioning.
Industry fit
Real Estate — a taxonomy-only vertical today (no real-estate clients exist on this platform yet), but the tag is honest: the agent genuinely does this, it just won’t light up a “Recommended” badge until a real client in that industry exists.
How to deploy
Request it the same way as any non-instant agent — see Deploy your first agent for the request-dialog walkthrough.
Sample conversation flow
Webhook (enquiry) ──► Look up client config ──► Qualify enquiry (Gemini)
│
▼
Parse qualification (code)
│
▼
Book the requested viewing on Cal.com (only when the enquiry has a time, name and email)
│
▼
Email the listing agent a summary (Resend)The enquiry is graded, parsed in a code step, a viewing is booked when the enquiry asks for a specific time, and the listing agent gets an email headed with the classification. There is no listing matching, no three-way switch, no Slack alert, no nurture email and no decline email — the flow is the same five steps every time.
It books only the viewing time the enquiry asks for, and does not check availability first. A
booking is attempted only when the enquiry names a time at least five minutes ahead, includes the
person’s name and email, and the client has a Cal.com viewing event type set; it uses the client’s
configured timezone. There is no GET /v2/slots call: if Cal.com refuses the time, nothing is
booked and the listing agent’s email says so. Check your Cal.com bookings after the first real enquiry.
Related
- Lead Qualifier — same booking mechanics, for non-property verticals
- Connect your integrations