> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Real Estate Property Inquiry to Viewing Voice AI Workflow
> Build the Real estate property inquiry to viewing workflow with DialNexa voice AI. Follow the prerequisites, system handoffs, launch checks, and safety rules.
This **Real Estate Property Inquiry to Viewing voice AI workflow** turns a defined business event into a DialNexa conversation, a structured outcome, and a traceable next action.
**Best for:** Real estate, Property rentals, New-home sales
Property enquiries are time-sensitive. Buyers and renters often contact several agents at once, so speed, qualification, and clear scheduling can decide who gets the viewing.
This workflow calls new enquiries, qualifies requirements, matches the right property or agent, and books a site visit or virtual viewing.
## Who Should Use This Real Estate Property Inquiry to Viewing Workflow
* Real estate brokerages, property portals, rental operators, coworking spaces, and new-home sales teams.
* Teams that receive high-volume listing enquiries from marketplaces and ads.
Track enquiry-to-call time, viewing booked rate, qualified buyer rate, agent acceptance rate, and show-up rate. The workflow matters because every delayed enquiry can become a lost viewing.
## Before You Begin
Prepare the following before building the workflow:
* A clear source event that should start the call.
* A [published DialNexa agent](/docs/agents/agent-versions-and-publishing) with an approved prompt and human-handoff rule.
* A test contact who has agreed to receive the call.
* Access to each source and destination system in the example stack.
* A short list of structured outcomes to store with [post-call analysis](/docs/agent-settings/post-call-analysis).
* An owner for failed runs, sensitive requests, and low-confidence matches.
## How The Real Estate Property Inquiry to Viewing Voice AI Workflow Works
1. A property enquiry arrives from a portal, website, ad, or missed call.
2. DialNexa checks CRM records, listing ID, property status, agent owner, location, and budget range.
3. The AI calls the prospect and confirms buying or rental intent, budget, move timeline, location preference, financing status, and viewing availability.
4. Qualified prospects are matched with available viewing slots.
5. The prospect receives address, meeting time, agent name, and required documents.
6. The agent receives a summary with listing, budget, urgency, and objections.
7. Low-fit leads are routed to nurture or alternate listings.
## Build The Real Estate Property Inquiry to Viewing Workflow Step By Step
1. **Define the trigger.** Choose one source event and document which records are eligible for the workflow.
2. **Prepare the agent.** Add the goal, questions, approved actions, disallowed actions, and transfer conditions to the agent prompt.
3. **Map call context.** Pass only the required customer and business fields through [dynamic variables](/docs/agents/dynamic-variables).
4. **Connect the systems.** Use a workspace connector when it is available. Otherwise use a [custom function](/docs/agent-settings/custom-functions), [agent webhook](/docs/api-access/agent-webhooks), or external automation service.
5. **Store structured outcomes.** Define the exact status, reason, owner, due date, and destination record ID that the workflow must produce.
6. **Add the next action.** Configure the workflow or application node that updates the destination system, sends a message, or creates a human-owned task.
7. **Test every branch.** Test success, rejection, no answer, wrong person, opt-out, missing data, provider failure, and human escalation before launch.
## Data Contract For This Workflow
Store enough data to explain what happened without requiring the next owner to read the entire transcript:
* Source event ID, source record URL, and workflow start time
* DialNexa call ID, agent version, call status, and end reason
* Matched customer or account ID and identity confidence
* Structured outcome, reason, urgency, requested next step, and any promise made
* Destination record ID, assigned owner, due date, and update result
* Transcript or recording link only when your privacy and retention rules allow it
## Example Integration Stack
* [HubSpot](/docs/integrations/hubspot) or [Salesforce](/docs/integrations/salesforce) for lead ownership.
* [Google Calendar](/docs/integrations/googlecalendar) for viewing slots.
* [WhatsApp](/docs/integrations/whatsapp) for confirmations and directions.
* [Gmail](/docs/integrations/gmail) for property details.
* [Google Sheets](/docs/integrations/googlesheets) for lead source reporting.
Provider pages describe possible connection patterns. Confirm the provider and required action in your DialNexa workspace before relying on a native connector.
## Human Review And Failure Paths
Do not book viewings for unavailable listings. Escalate high-value buyers, legal questions, financing concerns, and angry prospects to the agent.
Always send opt-outs, complaints, identity uncertainty, policy exceptions, sensitive data, and actions that change money, access, legal terms, or customer commitments to a trained person.
## Verify The Workflow Before Launch
Run at least one test for every outcome branch and confirm that:
1. Only eligible records enter the workflow.
2. The agent receives the expected variables and does not expose internal field names.
3. The destination system stores the correct status, owner, and DialNexa call ID.
4. Retried events do not create duplicate calls or duplicate downstream records.
5. Opt-outs and human-handoff cases stop automation immediately.
6. The next owner can understand the result and promised next step from the destination record.
## Measure The Real Estate Property Inquiry to Viewing Workflow
Compare the baseline with the first 50 to 100 completed runs, then review results by source, segment, owner, and outcome.
* Enquiry response time
* Qualified viewing booked rate
* Viewing show-up rate
* Agent follow-up completion
* Lost enquiry rate
* Pipeline value by listing source
Track error rate, duplicate rate, human-review rate, and opt-out rate alongside the business metrics above.
## Troubleshoot Common Workflow Problems
| Problem | What to check |
| ------------------------------------ | -------------------------------------------------------------------------------------------- |
| The wrong records enter the workflow | Tighten source filters and record the exact enrollment reason |
| The call sounds generic | Pass fewer, higher-quality variables and explain how the agent should use each one |
| The downstream record is incomplete | Require structured post-call fields before the destination action runs |
| Duplicate calls or writes appear | Use the source event ID and DialNexa call ID as idempotency keys |
| A provider action fails | Verify workspace availability, authentication, permissions, rate limits, and required fields |
| Too many cases need review | Group review reasons and improve one high-volume branch at a time |
## Frequently Asked Questions
### Which property inquiries should become calls?
Prioritize inquiries about available listings, high-intent viewing requests, repeat buyers, and leads with budget or location fit. Generic browsing leads can stay in nurture.
### What should DialNexa qualify before booking a viewing?
Capture property interest, budget, financing status, preferred area, move timeline, viewing availability, and whether the lead is a buyer, renter, agent, or investor.
### When should an agent be alerted immediately?
Alert agents for ready buyers, same-day viewing requests, premium listings, financing questions, seller inquiries, angry prospects, and duplicate leads tied to an active deal.
### What real estate metrics matter?
Track viewing booked rate, show rate, lead response time, qualification quality, and pipeline value by listing source. Review whether agents trust the summaries.
## Related Pages
* [DialNexa voice AI quickstart](/docs/quickstart)
* [Create and publish agents](/docs/agents/agent-versions-and-publishing)
* [Build DialNexa workflows](/docs/workflows/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Test DialNexa agents](/docs/agents/testing-agents)
* [Monitor call results](/docs/monitoring/call-detail-page)