Tenant Management Voice AI: CallSphere's Built-In Stack vs Vapi DIY

TL;DR

Property management calls are a different beast than buyer calls. The caller is a tenant, the topics are rent, repairs, lease renewals, and emergencies, and the data layer is a structured tenant lifecycle. CallSphere Real Estate ships tenants, leases, rent_ledger, maintenance_requests, payments, and notifications as first-class tables, with Maintenance, Payment, and Emergency agents wired to them. Vapi.ai gives you the voice plumbing — the entire tenant lifecycle is yours to design and build. This post walks the schema, the agents, and the call patterns.

What Property Management Voice Actually Does

A typical week of inbound calls to a 400-unit property management portfolio looks like:

• 38% rent and payment questions ("what's my balance?", "can I pay over the phone?", "did my payment hit?")
• 27% maintenance requests ("dishwasher broken", "AC not cooling", "leak under the sink")
• 14% lease questions ("when does my lease end?", "renewal terms?", "move-out process?")
• 9% emergencies (gas leak, fire alarm, lockout, water leak)
• 7% prospective new tenants (handed to leasing)
• 5% vendor calls (handed to operations)

That distribution requires more than a voice — it requires a stack.

Vapi's Tenant Story

There isn't one. Vapi has no tenant table, no lease object, no rent ledger, no maintenance request entity. To replicate tenant management on Vapi:

• Design the schema (tenants, leases, units, rent_ledger, maintenance_requests, payments).
• Build every API endpoint the agent calls (list tenant, get balance, log maintenance, schedule plumber, etc.).
• Integrate with existing property management software (AppFolio, Buildium, Yardi, RentManager) — most have APIs of varying quality.
• Build the emergency override path.
• Build the audit log.
• Build the tenant identity verification (caller ID + last 4 of SSN, or unit + last name).

For a 2-engineer team that already knows property management, plan 2-3 months for the data layer alone, plus another month per integrated PM software.

CallSphere's Tenant Stack

CallSphere ships the tables and the agents.

Tables (per property management company, with row-level security by company_id):

• companies — the property management company.
• properties — each managed property.
• units — each rentable unit.
• tenants — current and former tenants.
• leases — start, end, rent, security deposit, terms.
• rent_ledger — every charge and payment row.
• maintenance_requests — with status, priority, vendor.
• payments — payment intent + result history.
• notifications — outbound SMS/email/voice notifications.

Agents:

• Maintenance — creates and tracks requests; can offer self-service troubleshooting; routes to vendors.
• Payment — pulls balance, accepts payment over the phone, sends receipt.
• Emergency — overrides triage on emergency keywords; gathers nature + address; dispatches.

Comparison Table

Capability	Vapi (DIY)	CallSphere Real Estate
Tenants table	Build	Built-in
Leases table	Build	Built-in
Rent ledger	Build	Built-in
Maintenance requests	Build	Built-in
Payments	Build	Built-in
Notifications	Build	Built-in
Multi-property tenancy isolation	Build	Built-in (RLS)
Maintenance agent	Build	Built-in
Payment agent	Build	Built-in
Emergency override agent	Build	Built-in
Tenant identity verification	Build	Built-in
Time to live	4-6 months	Days

Tenant Lifecycle Diagram

flowchart LR
    A[Lease signed] --> B[(tenants + leases)]
    B --> C[Move-in inspection]
    C --> D[Recurring rent charge]
    D --> E[(rent_ledger)]
    E --> F{Tenant calls}
    F -->|Balance| G[Payment agent]
    F -->|Repair| H[Maintenance agent]
    F -->|Lease question| I[Aria + lease tool]
    F -->|Emergency| J[Emergency agent]
    G --> K[(payments)]
    H --> L[(maintenance_requests)]
    L --> M[Vendor dispatch]
    M --> N[Status update + notification]
    J --> O[On-call dispatch + audit]
    K --> P{Lease expiring?}
    P -->|Yes| Q[Renewal workflow]
    P -->|No| D
    Q --> R[Lease renewed or move-out]
    R --> S[Move-out inspection + final ledger]

Worked Example: Friday Night Maintenance Call

Tenant calls at 9:14pm: "My dishwasher is leaking water all over the floor."

CallSphere flow:

1. Caller ID matches a tenant in unit 4B at 1219 Cedar.
2. Aria identifies maintenance intent → hands off to Maintenance agent.
3. Maintenance agent confirms identity ("Is this Jenn? Unit 4B at 1219 Cedar?"), clarifies severity ("Is water still flowing? Have you turned the valve off?").
4. Tenant says water is contained but pooling. Agent classifies as urgent-but-not-emergency, creates a maintenance_request row priority=high, dispatches the on-call plumber.
5. Agent sends an SMS confirmation with the request ID and the ETA window.
6. Post-call analytics flag a satisfaction score; if low, an escalation email goes to the property manager Saturday morning.

That sequence on Vapi is a database, four endpoints, an SMS integration, and a vendor dispatch flow you build. On CallSphere it is the default behavior.

Migration / Decision Section

If you manage rentals and you are evaluating Vapi for tenant calls, the decision is usually how much PM software you already have. Three patterns:

• Greenfield (no PM software). CallSphere is straightforwardly faster — the tenant lifecycle is included.
• AppFolio/Buildium/Yardi already in place. CallSphere can sync with these via configured connectors; the voice layer becomes the "front door" while the existing PM stays the system of record.
• Custom in-house PM stack. Either build tenant tools on Vapi (months of work) or wire CallSphere's voice agents to your custom stack via webhooks.

Most independent property managers (200-2,000 units) pick CallSphere because the build math fails on small teams. Larger managers usually run a hybrid.

FAQ

How does tenant identity verification work?

Default is caller-ID match + a verification question (last 4 of phone, unit number, or last name). Higher-security flows can require a one-time SMS code. Sensitive operations (cancel autopay, change bank account) always require enhanced verification.

Can tenants pay rent over the phone?

Yes. The Payment agent integrates with the property management company's payment processor and accepts ACH or card subject to the company's configuration. PCI scope is minimized — the agent never speaks card numbers; it sends a one-time secure link.

What if the request is something the agent can't handle?

The agent escalates with full context. The property manager gets a structured ticket with the call transcript, the inferred intent, and any actions taken.

How are emergencies routed at 3am?

The Emergency agent runs the on-call rotation defined per property. It dispatches the appropriate vendor or staff and sends a notification to the property manager with the call recording and transcript.

Can the agent quote rent or accept lease modifications?

The agent reads from the lease and ledger. Modifications (lease changes, rent concessions) are flagged for human approval, never silently committed.

Does this integrate with my existing PM software?

Connectors for major PM platforms are available; custom webhook integrations to in-house systems are supported on enterprise plans.

See the tenant stack live at /demo. Real estate details at /industries/real-estate.