One phone workflow for residents, prospects, vendors, and emergencies

Property-management calls rarely arrive in neat categories. A resident reporting a leak, a prospect asking about a showing, and a vendor requesting access can all reach the same number within minutes. After hours, the most important question is not simply “Can someone answer?” It is “Can the call be classified and routed correctly?”

ThunderPhone gives a property team an AI phone agent that can identify the caller's purpose, collect property and unit details, search approved policies, create or update a request through an integration, and escalate according to the manager's rules. The same agent definition can answer a production number brought over a direct VoIP connection or a manual SIP trunk, place outbound calls and campaigns from that number, and take voice conversations from a website widget — one phone policy instead of a scattered answering service, leasing line, and maintenance hotline.

Separate routine requests from true escalation paths

A property-management agent can be configured to:

• ask whether the caller is a resident, prospect, owner, or vendor;
• collect the property, unit, callback number, and a concise description of the issue;
• follow a manager-authored emergency checklist without diagnosing the underlying problem;
• create a work-order record through a connected API;
• answer approved questions about office hours, application steps, rent-payment channels, amenities, parking, or vendor access;
• schedule or request showings when connected to an approved calendar or leasing system;
• transfer emergencies to an on-call number; and
• place compliant outbound follow-up calls for work orders, appointments, or resident confirmations.

Use cases across the resident lifecycle

Maintenance requests with urgency triage

Maintenance intake is the workload that defines property-management phones. The agent collects the property, unit, callback number, issue description, and access or permission-to-enter notes, then classifies the request against the manager's written urgency criteria — for example, active water intrusion, no heat below a stated temperature, or a security-compromising door failure. Requests that meet an escalation trigger go to the on-call path immediately; everything else becomes a structured work-order record for the morning queue. The classification comes from management's policy, never from the agent's own judgment about what is dangerous.

Emergency escalation to on-call staff

When a call trips an escalation trigger, the agent can warm-transfer to the on-call number: the resident waits on hold while the agent privately briefs the on-call recipient with the unit, the issue, and what the caller reported. If the recipient accepts, the resident is connected with context already delivered. If the recipient declines, does not answer, or the call reaches voicemail, the agent returns to the resident, confirms the callback number, and follows the configured fallback — so a missed handoff never becomes a silent dead end at 2 a.m.

Leasing inquiries and showing scheduling

Prospect calls are time-sensitive: an unanswered leasing inquiry is often a lost lead. The agent can answer approved questions about availability, floor plans, application steps, pet policy, and parking from attached documents; collect the prospect's contact details, move-in window, and unit preferences; and book or request a showing through a connected calendar or leasing system. Every leasing call produces a transcript and structured data deliverable to the team's CRM by webhook, so no inquiry disappears into a voicemail box.

Rent and payment questions

Residents call about due dates, accepted payment methods, late-fee policy, and where to find the payment portal. The agent answers those questions from approved policy documents and directs the resident to the management-approved payment channel. It routes — it does not take payments: ThunderPhone agents should not collect card or bank details by phone, which keeps payment handling inside the systems the management company already secures and reconciles.

Lease renewal outreach

Renewal conversations reward early, consistent contact. An outbound campaign can call residents entering the renewal window using management-approved scripts — confirming interest, answering approved questions about terms, and scheduling a follow-up with the property team for anything requiring negotiation. Voicemail detection lets the campaign leave a configured message or retry later, and calling windows keep outreach inside the hours management sets.

Move-in and move-out coordination

Move dates generate a burst of predictable calls: key and access pickup, utility-transfer reminders, elevator reservations, inspection scheduling, and forwarding-address collection. The agent can place confirmation calls before a move-in, walk new residents through the management-approved checklist, and collect move-out details — departure date, inspection availability, forwarding address — as structured data pushed to the record system. That turns a coordinator's afternoon of phone tag into a reviewed call log.

Vendor call coordination

Vendors call to confirm work-order details, request unit access, or report that a job is complete. The agent can verify which work order the vendor is referencing, share management-approved access instructions, record completion notes, and flag no-shows or reschedules for staff follow-up. Outbound, it can call a vendor list to confirm tomorrow's appointments — navigating a keypad menu or waiting on hold if the vendor's office routes calls through one.

After-hours coverage

The calls that arrive after 6 p.m. are the ones most likely to be either emergencies or lost leads. An agent answers every after-hours call the same way it answers the daytime ones: it classifies the caller, applies the emergency checklist, escalates what qualifies, and logs everything else with a timestamped record. Managers stop losing sleep over routine calls — and stop discovering true emergencies from a morning voicemail.

Amenity and community questions from a knowledge base

Pool hours, gym access, package-room procedures, guest parking, pet rules, and clubhouse reservations account for a steady stream of short calls. Uploading community handbooks and policy documents — or importing pages directly from the property's website by URL — gives the agent an approved source to search mid-call. Documents can be scoped per agent, so a multi-property portfolio can keep each community's rules separate.

Multilingual resident communication

Portfolios often serve residents more comfortable in Spanish, Cantonese, Hindi, or dozens of other languages. A ThunderPhone agent supports 47 languages, starts in its configured primary language, and can switch automatically mid-call when a caller uses another configured language — so a resident reporting a leak in Spanish gets the same emergency screening, in Spanish, that an English-speaking caller would get, without a translation callback.

Delinquency reminder calls

Payment-reminder calls can run as outbound campaigns using only management-defined scripts: a courteous reminder of the balance status and the approved payment channels, within configured calling windows, with voicemail behavior set by policy. ThunderPhone does not provide collections scripts or escalation tactics. The management company defines every word the agent may say and remains responsible for compliance with the laws that govern its reminder calls — including consent, contact-hour, identification, and debt-communication rules that vary by jurisdiction and by how the portfolio is structured.

Sample maintenance call flow

Agent: Thank you for calling Cedar Row Management. Are you calling about maintenance, leasing, billing, or something else?

Caller: Maintenance. Water is coming through the ceiling in my bathroom.

Agent: I will treat this as urgent. Is anyone in immediate danger, and is water near an electrical fixture?

Caller: No one is hurt, but it is close to the ceiling light.

Agent: Please keep away from the fixture and follow the property's approved emergency instructions. What is the property address and unit number?

Caller: 418 Pine Street, unit 3B.

Agent: Thank you. I have created an urgent request for unit 3B and will try the on-call maintenance line now. You may hear hold music while I explain the situation privately.

If the on-call person accepts an eligible warm transfer, the caller is connected. If not, the agent returns, confirms the request and callback number, and gives only the fallback instructions approved by management.

Features that matter in property management

Rules-based emergency intake

Define the exact questions and escalation triggers for water, fire, electrical hazards, lockouts, heating, security, and other property-specific issues. The agent follows that policy; it does not invent repair or safety advice.

Knowledge by property or portfolio

Attach approved documents for office hours, maintenance responsibilities, access procedures, leasing FAQs, and community rules — as text, Markdown, CSV, PDF, or DOCX uploads (up to 5 MB per text file and 50 MB per PDF or DOCX), or imported directly from a URL. Scope the documents so the agent searches the right information for the caller's property.

Work-order and leasing integrations

Connected apps, APIs, and MCP tools let an agent write structured call data into the systems your team already uses, when those systems expose the needed operations. Remote MCP servers can be added by URL and synchronized so newly exposed tools become available to the agent automatically.

Warm transfers with a fallback

Warm transfer is available on eligible production VoIP or SIP numbers that can place outbound calls. The agent can brief the on-call recipient privately while the resident waits, then reconnect with the resident if the recipient declines or does not answer.

Outbound campaigns and follow-ups

Campaigns can call contact lists within a configured time window and retry selected outcomes. Before enabling outbound calls, a covered organization admin must complete ThunderPhone's one-time TCPA compliance confirmation. The property manager remains responsible for consent, caller identification, do-not-call obligations, calling windows, and other applicable laws.

Voicemail, hold, and phone-menu handling

Outbound agents can detect voicemail, navigate keypad menus, and wait on hold. Voicemail behavior can be set to let the prompt decide, hang up, or leave a configured message.

Records, webhooks, and oversight

Every call — phone or web widget — produces a transcript and grade, plus a recording when recording is enabled, so a manager can audit exactly how an emergency script was applied. Webhook endpoints with HMAC-SHA256 signatures deliver call events to the systems that need them, each endpoint with its own secret and event subscriptions.

Test before residents call

Emergency policies deserve rehearsal. AI-caller simulations can play a panicked resident with a burst pipe or a prospect asking about pet policy; scenarios can be saved into regression suites with minimum pass-rate gates, and live-traffic A/B experiments can compare script variants. Simulations are billable real calls, and the interface shows the charge before a run.

What would this cost each month?

Suppose a portfolio handles 1,200 AI-assisted calls per month, averaging 2.5 minutes each:

1,200 calls × 2.5 minutes = 3,000 minutes per month

• Spark: 3,000 × $0.02 = $60/month
• Bolt: 3,000 × $0.05 = $150/month
• Storm: 3,000 × $0.09 = $270/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Frequently asked questions

Can a ThunderPhone agent create maintenance requests?

Yes, when connected to a work-order system or API that permits the action. It can collect the property, unit, contact details, issue description, access notes, and priority fields defined by the manager.

Can it determine whether a maintenance issue is an emergency?

The agent can apply a written emergency-screening policy, but it should not independently diagnose hazards. Management defines the questions, approved instructions, trigger conditions, and escalation numbers.

Can the agent call residents with follow-up updates?

Yes, through individual outbound calls or campaigns using an eligible production number. The organization must complete the applicable outbound-compliance confirmation, and the organization placing the calls remains responsible for consent and other calling-law requirements.

Does ThunderPhone enforce TCPA compliance for us?

No. ThunderPhone requires a one-time admin confirmation before covered organizations enable outbound calling and provides configurable calling windows. The organization remains responsible for consent, identification, do-not-call handling, and the laws that apply to each campaign.

What happens if the on-call person does not answer a transfer?

In a warm-transfer flow, the agent can return to the resident, confirm the callback details, and follow the configured fallback. Cold transfers route immediately and do not provide that private screening step.

Can one agent support multiple properties?

Yes. The prompt, call-routing data, integrations, and attached knowledge can identify the property and select the correct workflow. Test each property's emergency and policy variations before deployment.

Can the agent take rent payments over the phone?

No, and it should not be configured to. The agent can answer approved questions about due dates, methods, and late-fee policy, and direct residents to the management-approved payment portal or office. Keeping payment collection out of the phone channel keeps card and bank details inside the systems the management company already secures.

Can it serve residents who do not speak English?

Yes. The platform supports 47 languages, and an agent can switch automatically mid-call when a caller uses a configured additional language, applying the same approved scripts and emergency screening in that language. ThunderPhone is GDPR and HIPAA compliant, and customers remain responsible for configuring their workflows, recordings, and notices — including any language-access obligations that apply to their properties.