45 Questions
AI Receptionist for Property Management Companies.
Real questions and answers about using an AI phone receptionist for property management companies: pricing, setup, compliance, day-to-day workflow, and more.
What does Voksha cost for a property management company managing a few hundred units?
Most companies managing 200 to 500 units land on Premium at $99/month, which includes 150 answered calls. That included allotment rarely covers a portfolio this size on its own, since a 300-unit portfolio typically generates 250 to 500 inbound calls a month across leasing inquiries, maintenance requests, rent questions, and general tenant support. Overage is a flat $1 per call, so a company running 400 calls a month pays $99 plus $250 in overage, or about $349/month total. Compare that to a $3,000/month call center contract, which is a common rate for property management answering services that only take messages and still require your staff to call tenants back the next morning. Even at $500 to $700/month all-in with overage, Voksha runs at a fifth to a quarter of that cost while actually dispatching emergencies and booking showings instead of just logging a message. Companies under 100 units with lighter call volume can often start on Starter at $14/month with 15 included calls, though most professionally managed portfolios outgrow that within the first month. Enterprise, starting at $990/month with custom call volume, becomes worth evaluating once you cross roughly 800 to 1,000 units or have multiple property managers sharing a central line generating well over 600 calls monthly. Billing is month-to-month with no long-term contract, and a 7-day money-back guarantee lets you test it through a real weekend of maintenance calls before committing.
Will overage fees add up fast given how many calls a 500-unit portfolio generates?
It depends on your baseline call volume, but the flat $1 per call overage is predictable in a way that per-minute answering service billing is not. A 500-unit portfolio typically generates somewhere between 400 and 800 calls a month once you count leasing inquiries, routine maintenance requests, emergency dispatch calls, rent and lease questions, and move-in/move-out coordination. On Premium at $99/month with 150 calls included, that same portfolio would run $99 plus $250 to $650 in overage, landing between $349 and $749/month. At that volume it is worth running the math against Enterprise, which starts at $990/month with custom call volume built in rather than metered overage, since a portfolio consistently generating 600+ calls a month often breaks even or comes out ahead on Enterprise once you add the custom routing and compliance features. The key difference from a traditional answering service is that Voksha's overage never changes rate based on call length or time of day. A 45-second call asking about pet policy and a 6-minute emergency triage call for a burst pipe both cost the same flat dollar. Answering services, by contrast, often bill per minute and charge premium rates for after-hours or holiday coverage, exactly when property management emergency volume spikes hardest (storms, freezing pipes, heat waves). Run your actual call log from the last 60 days through your phone system or current answering service invoice to get a real number before picking a plan, rather than guessing.
Is Voksha actually cheaper than the $3,000/month answering service we're paying now?
In almost every case, yes, and by a wide margin. A $3,000/month call center contract for property management coverage typically buys you message-taking only, someone answers the phone, writes down that a tenant has no hot water, and emails or texts it to your on-call staff, who then has to call the tenant back to get details, assess severity, and find a vendor. Voksha on Enterprise, starting at $990/month with custom call volume, costs roughly a third of that and does the triage itself: it identifies whether the issue is a true emergency (flooding, no heat, gas smell) versus routine (leaky faucet, squeaky door), gathers unit number and access instructions, and creates the work order in AppFolio or Buildium automatically before your on-call staff is even alerted. Even a mid-size portfolio on Premium at $99/month plus overage, likely landing between $300 and $700/month total depending on call volume, still comes in well under $3,000. The real savings compound beyond the subscription cost: your on-call property manager stops spending 20 to 30 minutes per emergency call gathering basic information the answering service should have already collected, and routine after-hours calls (a tenant asking about pool hours or trash pickup day) get resolved instantly instead of generating a callback task for the morning. Most companies switching from a legacy call center see the cost difference alone justify the switch within the first billing cycle, before even counting the operational time saved.
Do we need Enterprise pricing or can Premium handle a mid-size portfolio?
For most portfolios under 600 to 800 units, Premium at $99/month with 150 included calls plus $1 overage covers you comfortably and is the more economical choice. The math flips toward Enterprise, which starts at $990/month with custom call volume, once you cross that threshold and are consistently generating 700+ calls a month, because at that point flat per-call overage on Premium starts costing more than a custom Enterprise rate. Volume is not the only factor, though. Enterprise also makes sense if you manage properties on behalf of multiple owners and need centralized reporting broken out by property or owner, if you run a shared regional call center serving several offices with different escalation contacts per property, or if your portfolio includes affordable housing, senior living, or other property types where you need documented compliance handling (HIPAA-adjacent data for senior communities, or audit trails for Fair Housing compliance) built into the plan. A practical way to decide: pull your last three months of inbound call volume across every property you manage, average it, and compare the total cost on Premium (base plus overage) against Enterprise's starting rate. If you are a single-office company managing under 500 units with one main line, Premium is almost always the right starting point, and you can move to Enterprise later since there is no long-term contract locking you in either direction. Several companies start on Premium, watch their actual call volume for 60 to 90 days, and then make the Enterprise decision with real data instead of a guess.
Is there a setup fee or long-term contract to use Voksha for our property management company?
No setup fee, and no long-term contract on any plan, including Enterprise. Billing is month-to-month, so you can start on Starter or Premium, test it against a real month of tenant calls and maintenance emergencies, and change plans or cancel without penalty. There is also a 7-day money-back guarantee, which matters more in this industry than most, because the real test of an AI receptionist for property management is whether it correctly triages a genuine emergency (a burst pipe at 11pm versus a tenant asking about the dog policy) the first time it happens, not in a demo. Setup itself, connecting your existing phone number, calendar, and property management software, takes 5 to 30 minutes and does not require hardware, a new phone system, or IT involvement beyond call forwarding, which most companies already know how to configure from switching answering services in the past. The absence of a contract is a deliberate difference from most call center and answering service agreements in this space, which frequently lock property management companies into 6 or 12-month terms with early termination fees, partly because those services know how disruptive it is to switch your emergency contact line once tenants and vendors have it. Because Voksha keeps your existing number through call forwarding rather than issuing a new one, switching away later (if you ever needed to) is also low-friction, you are never stuck with a locked-in number the way you might be with a dedicated answering service extension.
How does setup work if we already use AppFolio or Buildium?
You keep AppFolio or Buildium as your system of record; Voksha connects to it rather than replacing it. During setup, you link your AppFolio or Buildium account so work orders created from tenant calls sync automatically with unit number, tenant name, issue description, and urgency level already filled in, the same fields your maintenance team already checks each morning. You also load your property list (addresses, unit counts, amenity details, pet policy, application requirements) either by importing directly from your property management software or pasting details for each property, so Voksha can answer prospect questions accurately without a human checking a spreadsheet. Next you set your maintenance escalation rules: which issues count as true emergencies (flooding, no heat, no AC in extreme heat, gas smell, broken locks) that trigger an immediate alert to your on-call staff, versus routine requests that get logged as a standard work order for business-hours follow-up. You also connect your leasing calendar, Google Calendar, Outlook, or Calendly, whichever your leasing agents already use, so Voksha can check real availability before booking a showing. Most companies already running AppFolio or Buildium have this fully configured within 30 minutes, since the bulk of setup time is populating property and unit details rather than technical integration work. Nothing about your existing AppFolio or Buildium workflow changes for your staff, work orders still land in the same dashboard they check every day, they just show up already triaged instead of needing intake from a paper message or voicemail.
Can we keep our existing main office line and after-hours emergency number?
Yes. Most property management companies run two numbers, a main office line published on their website and lease paperwork, and a separate after-hours emergency line tenants are given at move-in for true emergencies. You do not need to change either. Setup uses call forwarding, so both numbers can point to Voksha, either full-time or conditionally (rings your office during business hours, forwards to Voksha after hours and on weekends, which is the most common setup). This matters specifically for property management because tenants are typically trained during move-in orientation to call one specific number for emergencies, and changing that number creates real risk, a tenant with a burst pipe calling an old disconnected line during a genuine emergency is exactly the scenario you are trying to prevent. Because nothing changes on the tenant-facing side, no re-training tenants, no updating lease documents, no reprinting the emergency contact card taped inside unit utility closets, you avoid the transition risk of a new number entirely. If you use a dedicated after-hours answering service currently, you simply redirect that same forwarding rule from the answering service to Voksha, a change most phone carriers or VOIP providers (RingCentral, Grasshopper, standard PBX systems used by property management offices) can make in a few minutes. Many companies run a short overlap period where both the old service and Voksha are configured, testing Voksha on the after-hours line for a week or two before fully cutting over the main office number.
How do we teach Voksha our maintenance escalation matrix and on-call rotation?
You define it once during setup and update it whenever your rotation changes, the same way you would update an on-call spreadsheet. The escalation matrix has two parts. First, severity classification: you tell Voksha what counts as an emergency requiring immediate dispatch (no heat below a certain temperature threshold, active flooding, no water, gas odor, broken exterior locks or doors, no power in extreme heat) versus routine issues that get logged as a standard work order (running toilet, minor appliance issue, cosmetic damage). Second, contact routing: you list who gets alerted for each issue type and property, since a lot of portfolios split maintenance across categories, a plumbing emergency might route to your in-house maintenance tech, while an electrical emergency routes to a licensed contractor, and different properties in your portfolio might have entirely different vendor lists if you manage buildings for multiple owners. You also set the on-call rotation itself (who is primary contact this week, who is backup), which you update the same way you'd update a shared calendar or on-call app, changes take effect immediately rather than requiring a new setup session. Voksha then follows this matrix automatically: a true emergency gets an instant call or text alert to whoever is on-call for that property, with the tenant's description, unit number, and callback number already attached, while routine requests get logged as a normal work order in AppFolio or Buildium for business-hours review. Most companies refine this matrix over the first few weeks as they see what Voksha actually classifies as emergency versus routine, then leave it largely static after that.
How long does it take to get Voksha fully live across multiple properties?
For a single office managing one central phone line across all properties, the core setup (number forwarding, calendar connection, property management software sync) takes 5 to 30 minutes. The variable that actually determines your full go-live timeline is how much property-level detail you load in: pet policies, application fees, parking rules, amenity hours, and maintenance escalation contacts, since these often differ property by property even within one management company. A company managing 5 to 10 properties with fairly standardized policies can usually finish full setup, including property-specific details, in half a day. A company managing 20+ properties with different owners, different pet policies, different maintenance vendor contracts per building, and different application requirements should budget 1 to 3 days to load everything accurately, since getting these details wrong means Voksha gives a prospect the wrong pet deposit amount or routes a maintenance emergency to the wrong vendor. The practical approach most companies take is a phased rollout: connect the after-hours emergency line and your highest-call-volume properties first, confirm triage and dispatch are working correctly for a week, then add the remaining properties and switch the main daytime line over. This lets your team validate accuracy on a smaller scale before the full portfolio is live, and catches any property-specific detail that was missed (a pet policy exception, a specific gate code procedure) before it affects every property at once rather than after the fact.
Does Voksha know how to stay Fair Housing compliant when answering rental inquiries?
The Fair Housing Act prohibits discrimination based on race, color, national origin, religion, sex, familial status, and disability, and many states and cities add protected classes on top of that, source of income, sexual orientation, gender identity, or student status, depending on jurisdiction. Voksha answers every prospect's questions from the same script and the same property data regardless of who is asking, which is actually a meaningful compliance advantage over relying entirely on human leasing agents. A leasing agent, even a well-trained one, can inadvertently steer callers, answering a question differently or volunteering extra information based on assumptions about a caller's family status or background, which is a common source of Fair Housing complaints and the exact behavior HUD-affiliated fair housing testing organizations specifically call to check for. Voksha's answers about pricing, availability, pet policy, and application requirements come from the property data you loaded, not improvised in the moment, so every caller gets the same factual answer. That said, Voksha is a tool that reduces risk through consistency, it does not replace your obligation to configure it correctly. You are responsible for making sure the property data and policies you load (occupancy limits, screening criteria) are themselves Fair Housing compliant, since occupancy standards that are overly restrictive or screening criteria that have a discriminatory effect are compliance issues regardless of who or what communicates them. Every call is logged, which also gives you a documented record if a Fair Housing complaint or test call is ever raised against a property.
How does Voksha handle tenant screening questions without creating FCRA problems?
The Fair Credit Reporting Act governs how you use consumer reports, credit checks, background checks, and eviction history, when screening rental applicants, including requirements around applicant consent and adverse action notices if someone is denied based on report content. Voksha does not pull credit reports or make approval or denial decisions, it answers general questions (what's the application fee, what's the minimum credit score requirement, what documents do I need to apply) and routes the actual screening to your existing tenant screening tool, TransUnion SmartMove, RentSpree, or whatever service you already use for background and credit checks. This division matters for FCRA compliance: the actual consumer report pull and any adverse decision based on it still happens through your compliant screening vendor with proper consent and disclosure, exactly as it does today, Voksha just handles the front-end questions that would otherwise consume a leasing agent's time. Where Voksha helps directly is consistency: it states your published screening criteria (minimum income multiple, credit score threshold, no evictions in the last X years) the same way to every applicant who calls, rather than a leasing agent giving a slightly different answer depending on the conversation, which reduces the risk of your stated criteria appearing to shift caller to caller. If a caller asks why they were denied, Voksha directs them to your formal adverse action process rather than speculating, since FCRA adverse action notices have specific legal requirements around content and delivery that need to come from your screening vendor or compliance process, not an ad hoc phone explanation.
What happens to sensitive tenant data like Social Security numbers and payment info collected during calls?
Voksha is built to avoid collecting the most sensitive data types over the phone in the first place. For payments, rather than taking a card or bank number verbally (which would pull the call into PCI DSS scope, the payment card industry standard governing how card data is stored and transmitted), Voksha directs tenants to your existing tenant payment portal, the one built into AppFolio, Buildium, or whatever software you use, so card and bank details are entered directly into a system already built to handle that securely. The same logic applies to Social Security numbers for rental applications: Voksha does not collect or store SSNs, it directs applicants to your formal application in your leasing software where that data is captured through a proper, secured intake flow rather than spoken aloud on a recorded call. What Voksha does collect and store is call content relevant to property management operations, tenant name, unit number, issue description, appointment requests, which is encrypted in transit and at rest. On the Enterprise plan, Voksha offers HIPAA and GDPR-level compliance controls, HIPAA is most relevant if your portfolio includes senior living or assisted living properties where health-related information comes up in tenant communication, and GDPR matters if you manage properties on behalf of international owners or investors whose personal data you process. For a standard residential or commercial property management company without those specific circumstances, the practical security question is usually just data encryption and access controls, which apply on every plan, not just Enterprise.
Does HIPAA or GDPR actually apply to our property management company?
For most standard residential or commercial property management companies, no, not directly, and you should be skeptical of anyone claiming otherwise. HIPAA governs protected health information handled by covered entities, healthcare providers, insurers, and their business associates, not landlords or property managers. The exception is if your portfolio includes senior living communities, assisted living facilities, or supportive housing where health-related accommodations (a tenant's mobility equipment, a caregiver's access schedule, medication delivery coordination) are routinely discussed as part of managing the property, in which case HIPAA-adjacent handling of that information becomes genuinely relevant, and that is the scenario where Voksha's Enterprise-tier HIPAA compliance features actually apply. GDPR governs personal data of individuals in the European Union, so it is relevant to a US property management company mainly if you manage properties owned by European investors or funds where their personal and financial data as owners is processed by your systems, not typically because of your tenants, who are usually US or Canada based. What does apply to essentially every property management company, regardless of size, is Fair Housing Act compliance on the leasing side, FCRA compliance on the screening side, and state-level landlord-tenant law governing security deposits, notice periods, and habitability standards. If a vendor or consultant tells you HIPAA applies to your typical multifamily or single-family rental portfolio, ask specifically what protected health information your business handles as a covered entity or business associate, because for most portfolios the honest answer is none.
What does a typical day actually look like with Voksha handling our front line?
Overnight and before your office opens, Voksha has already been answering calls: a tenant reporting no hot water at 11pm, a prospect asking about a two-bedroom unit's availability at 9pm, a current tenant confirming their move-out date. By the time your property manager logs in, the dashboard shows what happened overnight sorted by urgency, true emergencies (flooding, no heat) that were already dispatched to on-call maintenance with a text alert sent in real time, and routine items (a work order for a squeaky door, a leasing lead who wants a callback) queued for business-hours follow-up. Your morning starts with reviewing that queue instead of listening to a stack of voicemails or reading handwritten message slips from an answering service. During business hours, Voksha keeps answering calls that come in while your team is on other lines, showing a unit, or in a resident meeting, so nothing goes to voicemail during your busiest hours either. A prospect calling about pet policy or pricing gets an answer immediately and, if qualified, a showing gets booked directly onto your leasing agent's calendar without anyone playing phone tag. Your maintenance coordinator checks the work order queue in AppFolio or Buildium the same way they always have, except every ticket already has unit number, issue description, and urgency level filled in, cutting the intake step that used to require calling the tenant back. By end of day, the team has spent time actually resolving issues and showing units instead of doing message intake.
How does a maintenance call actually get from a tenant's phone to a technician showing up?
A tenant calls the emergency line and describes the issue, no heat, water coming through the ceiling, garbage disposal jammed. Voksha asks clarifying questions to classify severity: is water actively flowing, is the temperature dropping below a livable threshold, is anyone in immediate danger. Based on your pre-configured escalation matrix, a true emergency (active flooding, no heat in freezing weather, gas smell, no working smoke detector) triggers an immediate alert, a call or text, to whoever is on-call for that property, with the tenant's name, unit number, callback number, and issue description attached, so your on-call staff has everything they need to dispatch a vendor without calling the tenant back first to gather basic facts. At the same time, a work order is created directly in AppFolio or Buildium with the urgency flag set, so it is visible in your normal dashboard, not sitting in a separate answering service log you have to check manually. For routine issues, a dripping faucet, a light fixture that needs replacing, Voksha logs the work order the same way but without the immediate page, since it can wait for business-hours triage and vendor scheduling. The tenant is told what to expect, an emergency dispatch is on the way, or a routine ticket has been logged and someone will follow up, so they are not left wondering whether their call actually registered. This whole path, call to classification to alert to logged work order, typically completes in under two minutes for an emergency, which matters because the gap between a burst pipe starting and a plumber arriving is what determines whether you are looking at a $200 repair or a $15,000 water damage claim.
Who reviews the work orders and leasing leads Voksha captures overnight?
It depends on your team structure, but the workflow is designed to fit into whatever review process you already run, not create a new one. True emergencies never wait for morning review, they trigger an immediate alert to your on-call staff the moment the call happens, so dispatch decisions happen in real time regardless of when your office opens. Everything else, routine maintenance requests, leasing inquiries, general tenant questions, lands in your existing systems overnight and gets reviewed the same way your team already starts the day. Routine work orders show up in AppFolio or Buildium exactly like a ticket submitted through the tenant portal, so your maintenance coordinator reviews and assigns them during their normal morning routine, no separate inbox to check. Leasing leads captured overnight, prospect name, contact info, unit interest, qualification answers, and a booked showing time if they qualified, show up on your leasing agent's calendar and CRM the same way a lead from your website or Zillow listing would. Most companies designate one person, often the property manager or a leasing coordinator, to do a quick morning pass through anything Voksha flagged as needing human follow-up (a prospect with an unusual question, a tenant dispute that needs a manager's judgment rather than a scripted answer) before the rest of the team starts their day. For portfolios with multiple properties and multiple managers, review responsibility is typically split by property, matching whoever already owns that property's day-to-day operations, so nothing changes about who is accountable for what, it just arrives pre-sorted instead of as a raw voicemail pile.
Can Voksha handle rent payment questions and late notice calls?
Yes, for the informational side, and it routes anything requiring judgment or negotiation to your team. A tenant calling to ask when rent is due, what payment methods are accepted, whether a partial payment posted, or how to set up autopay gets an immediate, accurate answer pulled from your policies and, where connected, your property management software's payment status. If a tenant received a late notice and calls asking what they owe or the grace period on their lease, Voksha can state the facts from your lease terms and late fee schedule. Where it hands off to a human is anything involving negotiation or exceptions, a tenant asking for a payment plan, disputing a late fee, or explaining a hardship situation, since those decisions involve judgment calls about the specific tenant relationship and often legal considerations (state-specific rules on late fees, grace periods, and notice requirements before pursuing further action) that need a property manager's sign-off rather than a scripted response. In those cases, Voksha logs the call with full context and flags it for your team to follow up rather than making a commitment on the company's behalf. This split matters operationally: rent and late notice questions are a high-volume, low-complexity call category, the same handful of questions repeated across hundreds of tenants each month, and handling that volume automatically frees your leasing and accounting staff to spend their time on the smaller number of calls that actually require a decision, rather than answering "when is rent due" for the fortieth time in a week.
How does Voksha handle move-in and move-out coordination calls?
Move-in and move-out generate a predictable cluster of calls, and Voksha handles the scheduling and informational side while routing anything requiring a physical inspection or judgment call to your team. On move-in, prospects and new tenants call to confirm key pickup time and location, ask about parking assignment, utility transfer instructions, and move-in inspection scheduling, all of which Voksha answers from your property's standard move-in procedures and can book directly onto your team's calendar if a specific appointment (key handoff, walkthrough) is needed. On move-out, tenants call to confirm their notice was received, ask about the move-out inspection process, and ask what is required to get their security deposit back in full, cleaning standards, whether carpets need professional cleaning, what damage counts as normal wear and tear versus chargeable. Voksha states your documented move-out checklist and deposit return timeline (many states require itemized deductions and return within a specific window, commonly 14 to 30 days depending on the state) directly from your policy, and books the move-out inspection appointment with your property manager or maintenance staff. What it does not do is make the actual damage assessment or deposit deduction decision, that inspection still requires a human physically walking the unit, Voksha's role is making sure the scheduling and informational calls around that inspection do not consume staff time or get missed during a busy turnover season when you might have a dozen units moving in and out in the same week.
Does Voksha integrate with AppFolio specifically?
Yes. AppFolio is one of the most common property management platforms Voksha connects to, and the integration works in both directions. When a tenant reports a maintenance issue by phone, Voksha creates the work order directly in your AppFolio account with unit number, tenant name, issue description, and urgency level already filled in, so it shows up in your maintenance dashboard the same way a ticket submitted through AppFolio's tenant portal would, no manual re-entry needed. For rental inquiries, Voksha can pull current unit availability and pricing from your AppFolio listings so prospects get accurate, up-to-date answers rather than information that was correct when a leasing agent last checked the spreadsheet. This matters specifically because AppFolio already centralizes so much of a mid-size property management company's daily operations, work orders, tenant ledgers, lease terms, that routing calls into a separate system would just create a second place your team has to check, defeating the purpose of automating the front line. Setup on the AppFolio side is a connection made once during onboarding, after which new work orders and updated availability sync automatically without your team doing anything differently in how they use AppFolio day to day. Companies using AppFolio's built-in maintenance workflow, vendor assignment, tenant communication logs, keep using all of that exactly as before; Voksha's job is making sure the intake step, the actual phone call from the tenant, happens accurately and immediately instead of sitting as an unclaimed voicemail before it ever reaches AppFolio.
What about Buildium, does that integrate too?
Yes, Buildium integrates the same way AppFolio does. Work orders created from tenant maintenance calls sync directly into your Buildium account with unit, tenant, issue description, and urgency already populated, so your maintenance team reviews and assigns them from the same Buildium dashboard they already use, rather than a separate inbox or spreadsheet fed by an answering service. Rental listing details, availability, pricing, application requirements, connect from Buildium so prospect calls get accurate answers pulled from your live listings instead of a leasing agent working from memory or an outdated printout. Buildium is especially common among smaller and mid-size property management companies and independent landlords managing anywhere from a handful of units up to a few hundred, and this segment tends to run leaner staffing, often one or two people handling leasing, maintenance coordination, and accounting simultaneously, which is exactly the setup where an unanswered after-hours call is most likely to become a lost lead or a small maintenance issue that turns into a bigger one by the time someone calls the tenant back. The practical benefit for a Buildium-based operation is that the phone stops being a bottleneck tied to one or two people's availability; calls get answered and logged into the same Buildium workflow whether your small team is in a showing, on another call, or asleep. Setup for the Buildium connection happens once during onboarding, typically taking a few minutes alongside connecting your phone number and calendar, and requires no changes to how your team already works inside Buildium day to day.
Does it work with Yardi or RealPage for larger multifamily portfolios?
Yardi Voyager and RealPage are the two platforms most commonly used by larger multifamily operators and property management companies running 1,000+ units across multiple communities, and Voksha connects to both. For a portfolio at that scale, the value shifts somewhat from basic call answering toward handling volume and consistency across many properties at once: work orders from maintenance calls route into Yardi or RealPage with the correct property and unit already tagged, which matters a great deal when your portfolio spans dozens of distinct communities, each potentially with its own maintenance vendor list, escalation contact, and leasing team. Leasing inquiries similarly pull live availability and pricing per community from your Yardi or RealPage data, so a prospect asking about a specific community gets that community's actual current pricing and unit mix rather than a generic answer. At this scale, Enterprise pricing, starting at $990/month with custom call volume, is typically the right fit rather than Premium, since a multifamily operator running Yardi or RealPage across a large portfolio is almost always well past the 150-call included allotment on Premium, and Enterprise's custom routing lets you configure different escalation paths per community rather than a single flat rule across the whole portfolio. Larger operators also tend to have compliance and reporting requirements, centralized visibility into call volume, response time, and lead conversion across every community, that Enterprise's reporting tier is built to support, which matters for regional or corporate oversight across a multifamily portfolio in a way it typically does not for a single-office company managing under a few hundred units.
Can Voksha sync property showings directly to our leasing agents' calendars?
Yes. Voksha connects to Google Calendar, Outlook, or Calendly, whichever your leasing team already uses, and checks real-time availability before booking a showing, so a prospect calling at 8pm asking to see a unit this weekend gets booked directly into an open slot on the correct leasing agent's calendar rather than a message that has to be manually scheduled the next morning. This matters more in property management than in most industries because showings are usually split across multiple agents and multiple properties, a caller asking about a unit at one community needs to land on that community's leasing agent's calendar, not a shared generic calendar that then has to be manually reassigned. During setup, you map which leasing agent or team member handles showings for each property so Voksha routes bookings correctly without a dispatcher in the loop. If a property uses a self-showing system, a lockbox code or smart lock, rather than an agent-led tour, Voksha can instead provide access instructions directly after confirming the prospect is qualified, skipping the calendar step entirely for that property type. For portfolios juggling move-out walkthroughs, maintenance inspection appointments, and prospect showings across the same calendar, Voksha respects whatever blocked time and buffer rules you've set, so it will not double-book a leasing agent who already has an inspection scheduled. The net effect is that the 60% of rental inquiries that come in outside business hours convert into a booked showing on the spot instead of a next-day callback, which is often the difference between a prospect touring your unit versus a competitor's.
Does it connect to tenant screening tools like TransUnion SmartMove or RentSpree?
Voksha connects to these screening tools at the handoff point rather than performing the screening itself, which is the correct division given FCRA requirements around consumer report consent and adverse action notices. When a prospect calls asking how to apply, Voksha explains your screening criteria, minimum credit score, income requirement, application fee, required documents, and sends them the application link tied to whichever screening tool you use, TransUnion SmartMove, RentSpree, or another provider, so the actual credit and background check happens through your existing compliant process with proper applicant consent captured at that step. Once an application is submitted and a screening result comes back, that decision stays with your leasing team, not Voksha, since approve/deny decisions based on consumer reports carry legal requirements around adverse action notices that need to come from your screening vendor or compliance workflow. Where the integration adds real value is reducing the number of calls your leasing agents field just explaining the process: "what's the application fee," "how long does screening take," "what if I have a past eviction," which are high-frequency, low-complexity questions that eat up leasing agent time without requiring their judgment. Voksha answers those consistently and sends the applicant straight to your screening portal, so your leasing team's time goes toward reviewing actual applications and handling edge cases (a prospect with a screening question that genuinely needs a judgment call) rather than repeating the same intake information to every caller who's still deciding whether to apply.
Should we just hire a full-time after-hours on-call coordinator instead of using an AI receptionist?
Run the actual numbers before deciding. A dedicated after-hours coordinator, someone answering emergency calls and coordinating dispatch overnight and on weekends, typically costs $40,000 to $55,000/year in salary alone once you account for the odd-hours schedule, before benefits, payroll tax, and the fact that a single person cannot cover every night and weekend without burning out or requiring backup coverage, which usually means budgeting for at least 1.5 to 2 FTEs to genuinely cover nights, weekends, and holidays. That puts real after-hours coverage with a human at $70,000 to $100,000+/year for most portfolios. Voksha on Enterprise, starting at $990/month, or roughly $12,000/year, covers unlimited after-hours availability at a fraction of that cost, and unlike a single coordinator, it never misses a shift, calls back to back without a queue, and does not need a night off. The honest trade-off is judgment: a skilled human coordinator can make nuanced calls a script cannot, deciding whether an unusual situation warrants waking up a property manager versus waiting until morning, or handling a tenant who is upset and needs de-escalation rather than information. The practical approach many companies land on is a hybrid, Voksha handles the volume, triage, and dispatch for standard emergency categories, while a human property manager remains the actual on-call decision-maker who Voksha alerts and hands off to, rather than trying to reach a live coordinator by phone in the first place. That gets you 24/7 coverage without paying for a dedicated overnight staff member sitting idle most nights waiting for a call that may not come.
How does Voksha actually compare to a live answering service built for property management?
The core difference is what happens after the phone gets answered. A property management answering service, typically $500 to $3,000/month depending on call volume and coverage hours, has a live operator take a message: tenant name, unit, and a brief description of the issue, then relay it to your on-call staff, usually by text or email. That operator generally cannot access your property management software, cannot check real unit availability for a leasing call, cannot verify a maintenance escalation matrix specific to your portfolio, and often does not know the difference between a routine work order and a genuine emergency beyond whatever the tenant says in a 30-second call, so triage quality varies operator to operator and shift to shift. Voksha does the triage and the action: it classifies severity against your specific escalation rules, creates the work order directly in AppFolio or Buildium with details filled in, and alerts on-call staff immediately for true emergencies, all without your team calling anyone back to get basic facts. On the leasing side, an answering service operator can only take a message; Voksha checks real calendar availability and books a showing directly. Cost-wise, Voksha typically runs at a quarter to a third of a comparable answering service contract once you account for the operational value, work orders arriving pre-triaged and correctly routed instead of raw messages your team has to process manually. The main scenario where a traditional answering service still has an edge is calls requiring genuine emotional judgment, a distressed tenant needing de-escalation, where an experienced human operator's instincts matter more than speed or consistency.
What's the real difference between Voksha and just letting after-hours calls go to voicemail?
Voicemail is functionally equivalent to no coverage for the two call types that matter most in property management: true emergencies and rental leads. A tenant with a burst pipe or a gas smell calling at 11pm is not going to leave a calm voicemail and wait until 9am, they are going to call the next property management company, or a competitor's on-call number if there's a shared building line, or worse, they will not call at all and the damage compounds overnight, turning a $200 fix into a $10,000+ water damage claim by morning. On the leasing side, roughly 60% of rental inquiries happen after normal business hours, and a prospect who hits voicemail rather than a live answer moves on to the next available rental within minutes; renters comparing multiple listings simply book a showing with whoever answers first, and voicemail means you are never that first answer. Voicemail also creates a compounding morning workload problem: your staff arrives to a backlog of messages that all need callbacks, by which point the emergency has often worsened and the leasing prospect has often already toured somewhere else. Voksha replaces that gap entirely, every call gets answered in real time, emergencies get dispatched immediately rather than discovered hours later, and qualified leasing prospects get booked into a showing on the spot. The cost comparison is almost not worth making, voicemail is free but effectively costs you every lead and every hour of unmitigated emergency damage that happens while nobody has picked up, which for most portfolios adds up to far more than a $99/month or even $990/month subscription.
Is Voksha better than using a generic national call center that serves multiple industries?
The main gap with a generic call center is that its agents are trained across dozens of industries, not property management specifically, so they typically default to message-taking rather than triage because they lack the property-specific context to safely do more. A generic call center agent handling a tenant's maintenance call has no visibility into your AppFolio or Buildium account, no knowledge of which issues count as emergencies at your specific properties, and no ability to check your leasing calendar for real showing availability, so the best-case outcome is still a relayed message rather than a resolved or dispatched issue. These contracts also frequently bill by the minute with premium rates for after-hours or holiday coverage, which is exactly when property management emergency volume spikes hardest, freezing pipes in January, AC failures during a heat wave, meaning your costs climb precisely when call volume climbs. Voksha is configured specifically around your portfolio: your properties, your maintenance escalation matrix, your leasing calendar, your screening criteria, so every call is handled with actual context rather than generic scripting, and every emergency gets triaged and dispatched rather than just logged. Pricing is also flat rather than time-of-day sensitive, a call at 3am costs the same as a call at 3pm. The one place a generic call center with live human agents may still have an edge is handling truly unpredictable, high-emotion situations, a tenant in genuine crisis, where a trained human's real-time judgment and de-escalation skill outperforms any scripted or AI-driven system, which is why most companies configure clear escalation paths to reach a live property manager quickly in those specific situations.
What's the real cost of a missed emergency maintenance call?
It depends on the issue, but the range is wide and the downside is severe. A burst pipe or supply line failure left unaddressed overnight can produce $5,000 to $25,000 in water damage once you account for flooring, drywall, insulation, and potential mold remediation, plus displaced tenant costs if the unit becomes uninhabitable during repairs and you owe relocation assistance under your lease or state law. A no-heat call in freezing weather that goes unanswered risks frozen and burst pipes throughout a building, not just one unit, turning a single missed call into a multi-unit claim. Even smaller misses compound: a routine leak that would have been a $150 to $400 repair if caught immediately can become a $3,000 to $8,000 job with mold remediation if it runs for a week because nobody picked up the after-hours line. Beyond direct repair cost, there's liability exposure, most states hold landlords to an implied warranty of habitability, and an unaddressed no-heat or no-water complaint that a tenant can prove they reported creates legal exposure around rent withholding, repair-and-deduct claims, or in serious cases, constructive eviction claims. There's also tenant retention cost: a tenant who experiences a genuine emergency going unanswered is measurably more likely to not renew, and turnover costs (vacancy, cleaning, marketing, leasing commission) typically run one to two months of rent per unit. Against that range of $150 on the low end to $25,000+ on the high end for a single missed emergency, a $99 to $990/month Voksha subscription that guarantees every emergency call gets answered and triaged in real time is a small, predictable cost against a large, unpredictable one.
How many months of rent does one lost rental lead actually cost us?
A single lost lease is more expensive than most property managers estimate when they only think about the missed application fee. At a national average asking rent around $1,750/month, one signed 12-month lease is worth $21,000 in gross rent, and your leasing commission or management fee on that lease, if you charge one, adds further direct revenue. But the real cost of a lost lead isn't just that one prospect, it's the vacancy days that stack up while you wait for the next qualified prospect to call, tour, and sign. Every day a unit sits vacant costs roughly the daily rent equivalent, about $58/day at $1,750/month rent, plus the marketing spend (listing syndication fees, photography, staging) that has to run longer to attract the next applicant. Since 60% of rental inquiries happen after typical business hours, and renters comparing multiple available units tend to book a tour with whoever answers first, every prospect who hits voicemail or an unanswered line at 8pm is a prospect who very likely tours a competing property that answered instead, not someone who patiently waits and calls back tomorrow. If your portfolio loses even 2 to 3 leads a month to unanswered after-hours calls, and even a third of those would have converted to signed leases, that's a meaningful chunk of your annual leasing revenue disappearing to something as fixable as call coverage. Against $99 to $990/month for guaranteed after-hours answering, a single retained lease that would have otherwise gone to a competitor pays for a full year of the subscription many times over.
What's the actual ROI on Voksha for a company managing around 500 units?
Start with the cost side: a 500-unit portfolio generating roughly 400 to 700 calls a month typically lands on Premium plus overage or Enterprise, somewhere between $350 and $990/month depending on volume, call it $6,000 to $12,000/year. Now the return side. On leasing, even a modest reduction in after-hours lead loss, say retaining 2 additional leases a year that would have otherwise gone to a faster-responding competitor, at an average rent of $1,750/month and a 12-month lease, is $42,000 in retained annual rent revenue plus the vacancy days saved on those units. On maintenance, avoiding even one serious unaddressed emergency (a burst pipe causing water damage, a no-heat complaint escalating to a habitability claim) a year easily saves $5,000 to $25,000 in avoided repair and liability cost. On staffing, offloading routine tenant questions and work order intake from your team means each property manager can realistically handle more units without adding headcount, going from managing roughly 100 to 150 units per staff member toward 200 to 300, which for a 500-unit portfolio can mean running with one fewer full-time property manager, saving $55,000 to $75,000/year in salary. Even conservatively counting only the leasing and maintenance-avoidance numbers, the return is 5 to 10x the subscription cost annually, before counting the staffing efficiency gain at all. The honest caveat: this ROI depends on your portfolio actually having meaningful after-hours call volume and emergency exposure, a portfolio with very low call volume or minimal maintenance risk will see a smaller, though still positive, return.
Does Voksha actually let us manage more units without hiring more staff?
Yes, for the portion of the workload that is repetitive front-line communication, which is a larger share of a property manager's day than most people estimate. A typical property manager without automated call handling can effectively oversee roughly 100 to 150 units before phone volume, intake calls, leasing questions, work order collection, rent questions, starts crowding out the actual management work, vendor coordination, budget oversight, resident relations, lease renewals, that requires their judgment. Offloading the routine 80 to 90% of inbound calls, the pet policy questions, the "when is rent due," the basic work order intake, the showing scheduling, frees enough time that many companies find one property manager can effectively oversee 200 to 300 units instead, roughly doubling capacity per staff member without proportionally growing the team. For a company planning to grow from, say, 500 to 1,000 units over the next couple of years, that difference is the gap between hiring 3 to 4 additional property managers versus 1 to 2, a meaningful payroll saving at $55,000 to $75,000 per additional hire. This does not mean you need zero additional staff as you scale, judgment-heavy work, vendor negotiation, lease renewals requiring a human conversation, resident disputes, still needs people, and grows somewhat with unit count regardless of call automation. But the specific bottleneck of "we can't grow past X units without hiring another person just to answer the phone" is the exact problem this addresses, letting headcount growth track the parts of the job that actually require a human rather than call volume.
How much does unresolved after-hours maintenance actually cost in water damage claims?
Water damage is the single most expensive maintenance category that after-hours delay makes worse, and the cost curve is not linear, it accelerates the longer water keeps flowing or sitting. A supply line or pipe burst caught and shut off within an hour typically costs $500 to $2,000 to repair and dry out. The same event left unaddressed overnight, roughly 8 hours, commonly runs $5,000 to $15,000 once it soaks flooring, drywall, and potentially the unit below if it's a multifamily building. Past 24 to 48 hours, mold growth becomes a real risk in most climates, and mold remediation alone can add $2,000 to $10,000 on top of the water damage repair itself, plus potential health-related liability if a tenant develops respiratory symptoms and the delay in response is documented. For multifamily properties specifically, water intrusion rarely stays contained to one unit, a leak on a third floor can damage units on the second and first floor below it, multiplying the claim from a single-unit repair into a multi-unit, sometimes multi-tenant-relocation event that can run well into six figures for a serious case. Insurance typically covers a portion of this, but claims impact your loss history and future premiums, and most policies have deductibles in the $5,000 to $25,000 range for commercial property coverage, meaning a chunk of even an insured claim comes out of pocket regardless. The entire cost driver is response time between the issue starting and a plumber physically shutting off water, which is exactly the gap Voksha's immediate emergency dispatch is built to close, the difference between a call answered in real time and one sitting in a voicemail box until morning.
Is Voksha a good fit for a property management company with fewer than 100 units?
Generally yes, and it's often where the relative impact is largest, because small companies typically have the least after-hours coverage to begin with. A company managing 50 to 100 units often runs with one or two people handling everything, leasing, maintenance coordination, accounting, which means after-hours calls almost by default go to voicemail unless someone is willing to personally be on call every night and weekend indefinitely. Voksha on Starter at $14/month with 15 included calls, or Premium at $99/month with 150 included calls, gives that same small team 24/7 coverage without anyone burning out from being permanently on call, at a cost that's easy to justify against even a single avoided emergency or retained lease. The consideration that matters most at this scale is call volume relative to plan: a 60 to 80 unit portfolio might genuinely run under 100 calls a month, in which case Starter is enough, while a more active 80 to 100 unit portfolio with higher turnover or more marketing-driven leasing activity often crosses into Premium territory faster than the unit count alone suggests. Where it's a weaker fit at this size is if your portfolio is genuinely low-touch, long-term tenants who rarely call, minimal turnover, and a personal relationship-driven management style where you as the owner-operator want to personally handle every tenant interaction as a relationship touchpoint rather than delegate any of it. In that specific case, the volume and complexity may not justify even the low cost, though most small operators still keep it running purely as after-hours emergency insurance, given how disproportionately costly a single missed emergency can be.
Does this work for Section 8 or affordable housing portfolios with specific compliance needs?
It works, with some setup care around the specific rules that apply to subsidized housing. Section 8 and other affordable housing programs (LIHTC, HUD-subsidized properties) carry additional requirements beyond standard Fair Housing law, source of income protection is federal law under Section 8 itself in how vouchers must be accepted where required, and many states and cities have their own source-of-income anti-discrimination laws that go further. Voksha needs to be configured to state your voucher acceptance policy accurately and consistently, since inconsistent answers about whether a property accepts vouchers is a common source of Fair Housing and source-of-income discrimination complaints when different staff (or an inconsistently configured system) give different answers to different callers. Affordable housing properties also often have specific eligibility criteria, income limits tied to Area Median Income, unit set-asides, waitlist procedures, that differ meaningfully from standard market-rate screening, and these need to be loaded accurately into Voksha's property data so prospect calls get correct eligibility information rather than generic market-rate screening criteria. On the maintenance side, HUD and many state housing authorities have specific habitability inspection standards (HQS, Housing Quality Standards, for Section 8) with defined response time expectations for certain issue categories, which can be built directly into your escalation matrix so those categories are flagged with appropriate urgency automatically. The setup effort is somewhat higher than a standard market-rate portfolio because there's more property-specific compliance detail to load accurately, but the underlying tool works the same way, and companies managing mixed portfolios, market-rate and affordable units together, can run different rule sets per property within the same account.
When does Voksha not make sense for a property management company?
A few genuine scenarios. If your portfolio is extremely small, a single owner-managed duplex or a handful of units where you personally answer every call anyway and the volume is genuinely a handful of calls a month, the cost, even at $14/month on Starter, may simply exceed the value if you're never actually missing calls today. If your tenant base skews heavily toward residents who strongly prefer or need to speak with a human immediately for every interaction, some senior housing communities or properties serving populations with specific communication needs, an AI-first front line may create friction rather than removing it, and you'd want a hybrid model where Voksha handles routine intake but routes to a live person faster than it would for a typical portfolio. If your maintenance operation is entirely informal, no defined vendor list, no consistent escalation process, no property management software, Voksha's value is diminished because there's nothing structured for it to route into; you'd get more value from formalizing that process first, since even a human answering service struggles to be useful without a defined dispatch path to hand off to. It's also a weaker fit if your properties have highly unusual, judgment-heavy leasing terms that change constantly and can't be reduced to a stable script, a boutique portfolio where every lease is individually negotiated, since the value of consistent, accurate automated answers comes from having relatively standardized policies to draw from. For the large majority of professionally managed residential and commercial portfolios with defined maintenance vendors and standard leasing terms, though, none of these caveats apply.
Is this the right fit for a company managing luxury or high-touch properties?
It can be, but the configuration matters more than it does for standard portfolios. Luxury and high-touch properties often sell service quality as part of the value proposition, a resident paying premium rent expects white-glove responsiveness, and a poorly configured AI receptionist that sounds robotic or fails to escalate quickly to a concierge-level human touch can actually undercut that positioning. The way this works well in practice is using Voksha for exactly what it's strong at, instant answering so no call ever goes to voicemail, accurate informational answers about amenities and policies, and immediate triage and dispatch for maintenance emergencies, while configuring faster, more deliberate handoff to a live property manager or concierge for anything relationship-sensitive, a VIP resident request, a complaint that needs a personal touch, a leasing inquiry from a high-value prospect who expects a callback from an actual person quickly. Many luxury and boutique operators run Voksha specifically for after-hours and overflow coverage, so residents always get an immediate, competent response even at 2am, while daytime calls still route primarily to their in-house concierge or leasing team who residents already know by name. The 200+ language support is also genuinely useful here if your resident base is international, since it means an international resident or high-net-worth prospect calling doesn't hit a language barrier at 9pm. The honest test: if your brand promise is speed and consistency, this is a strong fit. If your brand promise is exclusively personal relationships with every interaction, use it as a safety net for coverage gaps rather than the primary front line.
What happens if a tenant calls about a gas leak or a carbon monoxide alarm going off?
This is treated as the highest-severity emergency category, and the response is built around getting the tenant safe first, then dispatching second. Voksha is configured to immediately instruct the tenant on safety steps consistent with standard guidance for gas or CO emergencies: leave the unit immediately, do not operate light switches or anything that could spark, call 911 or the gas utility's emergency line if instructed to do so by your protocol, and do not re-enter until cleared by the fire department or gas company. This life-safety guidance takes priority over any information gathering, Voksha does not spend time collecting extensive details before telling the tenant to evacuate. Simultaneously, it triggers an immediate emergency alert to your on-call staff with the property, unit number, and situation flagged as the highest urgency level, so a property manager is aware in real time and can coordinate with the tenant, the utility company, and if needed, temporarily displaced neighboring units. You configure the exact protocol during setup, some companies want Voksha to explicitly instruct tenants to call 911 directly for suspected gas leaks rather than treating it as a standard maintenance emergency, since gas and CO situations are genuinely life-threatening and first responders, not a maintenance vendor, are the correct first call. Because this call type carries real safety stakes, it's one of the categories worth reviewing carefully during setup and testing before go-live, confirming the exact wording and escalation sequence matches what your risk management or legal team wants tenants told in that specific scenario.
How does Voksha handle a tenant reporting no heat in the middle of winter?
No heat during cold weather is classified as a true emergency in virtually every escalation matrix, both because of tenant safety and habitability and because of the property risk: a cold unit risks frozen and burst pipes, which can turn a single no-heat complaint into a multi-unit water damage event if not addressed quickly. Voksha asks a few quick clarifying questions, current indoor temperature if the tenant knows it, outdoor temperature, whether this is the whole unit or one room, whether there's a working backup heat source, to gauge severity and pass accurate context to your on-call maintenance contact. It then immediately alerts whoever is on-call for that property with the details, so a technician or HVAC vendor can be dispatched the same night rather than the tenant waiting until morning. Many states and cities have specific legal requirements around minimum habitable indoor temperature and landlord response time for heat complaints, some municipalities require restoration within 24 hours or even same-day during winter months, and unaddressed heat complaints are one of the more common sources of habitability disputes and rent withholding claims. Because of that, no-heat calls are typically configured with the highest urgency alongside flooding and gas emergencies, not treated as a routine work order. If the outage affects an entire building (a boiler failure in a multifamily property) rather than a single unit, Voksha flags that distinction clearly since it changes the response, a building-wide boiler failure needs a commercial HVAC vendor and possibly tenant communication across many units simultaneously, not a single-unit maintenance visit.
What if a tenant calls in visible distress, like a domestic violence or safety situation?
These calls are configured to route to immediate human escalation rather than being handled through standard scripted flows, and this is one of the clearest cases where speed to a live person matters more than automated triage. If Voksha detects signals of a genuine safety crisis, a tenant describing violence, feeling unsafe, or any situation involving immediate physical danger, it is configured to first direct the caller to emergency services (911) if they are in immediate danger, since that is the appropriate first response regardless of the property management context. It then immediately escalates to a live property manager or your designated emergency contact rather than continuing to gather routine information, flagging the call as highest priority so a human is engaged as fast as possible. Property managers should think through this scenario specifically during setup, deciding in advance what your protocol is: does this go to the on-call property manager, to a specific trained staff member, or does it also trigger notification to building security if the property has it. Many property management companies also have lease provisions and legal obligations around domestic violence situations specifically, some states have laws protecting domestic violence victims from lease termination penalties or requiring landlords to allow lock changes, and those policies should inform how your team is instructed to respond once Voksha hands the call off. Voksha's role in this scenario is narrow and intentional: get the caller safety guidance immediately, get a human involved as fast as possible, and stop trying to be the primary problem-solver, since a genuine crisis situation is exactly where human judgment, empathy, and authority to act matter most.
Can Voksha handle storm or hurricane evacuation notices across a portfolio?
Voksha can handle the inbound side well, answering the flood of calls a severe weather event generates, but the outbound notification side (proactively telling tenants about an evacuation order) is a different function and typically still runs through your existing mass communication tool, a tenant portal announcement, text blast service, or property management software's bulk messaging feature. What Voksha does well during and after a storm event is absorbing the enormous spike in inbound calls that follows: tenants asking whether their building is in an evacuation zone, whether the property has specific storm procedures, how to report storm damage, whether maintenance can address a leak from wind damage, and questions about temporary relocation if a unit becomes uninhabitable. Instead of that call volume overwhelming a small property management staff during exactly the highest-stress period of the year, Voksha answers immediately with your pre-configured storm protocol information (evacuation zone status if you provide it, emergency contact procedures, insurance claim starting steps) and routes anything requiring an actual decision, temporary housing assistance, lease concessions for storm damage, to your team with full context already logged. For coastal and hurricane-prone portfolios (Gulf Coast, Atlantic Coast, Florida in particular), it's worth pre-loading storm-specific protocol answers before hurricane season starts rather than trying to configure them reactively once a storm is already forecast, since call volume during an active storm warning can be many multiples of a normal day and you want accurate answers ready immediately rather than being built on the fly while your team is also dealing with the storm itself.
What happens when a tenant is locked out of their unit at 2am?
Lockouts are extremely common after-hours calls, but they are not usually classified as maintenance emergencies in the same tier as flooding or no heat, since they don't threaten property or immediate safety in most cases, and how they're handled depends entirely on your company's specific policy, which varies quite a bit between property management companies. During setup, you tell Voksha your exact lockout procedure: some companies have an on-site or on-call maintenance staff member who can let tenants in with a master key or through a smart lock system remotely (increasingly common with properties using Latch, Yale, or similar smart lock systems where a code can be issued instantly without anyone driving to the property); others direct tenants to call a locksmith at their own expense per the lease terms, since many leases explicitly state lockouts are the tenant's responsibility and cost, not the property's. Voksha states whichever policy you've configured clearly and consistently, verifies the caller's identity against the tenant record on file before providing any access code or confirming a maintenance dispatch (an important step to avoid giving building access information to someone who isn't actually authorized for that unit), and either dispatches your on-call staff for units with staff-assisted entry or gives the tenant your standard locksmith referral information if that's your policy. This consistency matters because lockout policy inconsistently applied, letting some tenants in for free while charging others, creates both a fairness problem and potential Fair Housing exposure if the inconsistency correlates with any protected characteristic, even unintentionally.
How does Voksha work for a portfolio spanning multiple states or provinces?
Voksha handles multi-state and cross-border portfolios by letting you configure rules per property rather than applying one blanket policy across everything, which matters because landlord-tenant law, security deposit rules, notice periods, and habitability standards vary significantly by state and even by city. During setup, each property in your portfolio carries its own configuration: local security deposit limits and return timelines, applicable rent control or just-cause eviction ordinances if relevant, state-specific habitability response expectations, and local Fair Housing protected classes beyond the federal baseline (source of income protections exist in a growing number of states and cities, for example). This means a caller asking about deposit return timing for a property in a 30-day-return state gets a different, correct answer than a caller asking about a property in a 14-day-return state, without your team having to manually track which policy applies where. For companies operating in both the US and Canada, Voksha's 200+ language support also handles the practical reality of serving diverse tenant populations across different regions, and Canadian provinces have their own distinct landlord-tenant frameworks (Ontario's Residential Tenancies Act versus British Columbia's Residential Tenancy Act, for example) that get configured the same way as US state-level differences, property by property. Centralized reporting on Enterprise lets a regional or corporate team see call volume, response time, and issue trends rolled up across the whole multi-state portfolio while each property's actual policy configuration stays locally accurate, which is the practical balance most multi-region property management companies need: consistent operational visibility at the top with legally correct, locally specific answers at the property level.
Can it handle different maintenance vendors and escalation contacts for each property we manage?
Yes, this is configured at the property level, not as a single portfolio-wide rule, which is necessary for any company managing more than a handful of properties since vendor relationships and on-call staff typically differ building to building, especially for companies managing properties on behalf of different owners. Each property in your Voksha setup carries its own escalation matrix: which vendor or in-house technician handles plumbing emergencies at that specific building, who the electrical contractor is, who the HVAC vendor is, and who the actual on-call human contact is (which may be a dedicated property manager, a regional maintenance supervisor, or a rotating on-call schedule depending on how that specific property is staffed). This matters practically because a third-party management company running properties for 10 different owners might have 10 completely different vendor relationships, one owner insists on their preferred plumber, another property has an in-house maintenance tech who handles everything under a certain dollar threshold before escalating to outside vendors. Voksha routes each incoming call based on which property number or address the tenant is calling about, applying that property's specific rules rather than a generic default. When vendor relationships change, a plumber retires, a new HVAC contract starts, you update that property's configuration without touching any other property's settings, so a vendor change at one building never accidentally affects escalation at another. For companies managing a mix of owned and third-party managed properties, this per-property configuration is effectively what makes the tool usable at scale, since a one-size-fits-all escalation rule simply does not reflect how multi-owner portfolios actually operate.
Does this scale for a third-party management company running separate portfolios for different owners?
Yes, and Enterprise, starting at $990/month with custom call volume, is generally the right tier for this use case specifically because of the reporting and configuration needs it involves. A third-party management company typically needs each owner's properties handled with that owner's specific policies, pet policy, screening criteria, maintenance vendor preferences, and often wants to report back to each owner individually on call volume, response times, and lead conversion for their properties specifically, separate from the company's overall numbers. Voksha's per-property configuration supports this by letting different owner portfolios run under different rule sets within a single account, so a call about Owner A's building follows Owner A's policies and a call about Owner B's building follows Owner B's, without cross-contamination. Enterprise's reporting tier lets you pull performance data segmented by property or by owner group, which matters when owners expect transparency into how their specific assets are being handled, a common ask in third-party management contracts, especially institutional owners or those with multiple management companies managing different parts of their portfolio who want to compare performance. This also matters for onboarding and offboarding individual properties: when your company picks up a new owner's portfolio or loses a management contract, you add or remove that specific property's configuration without touching anything else, rather than having to reconfigure your entire phone and call-handling setup. For third-party managers actively pitching new owner contracts, being able to show a documented, consistent call handling and response time track record per property is also a genuine differentiator in new business conversations with prospective owner clients.
How does call routing work when we have regional property managers instead of one central office?
Voksha routes based on which property or region a call relates to, not a single central destination, which fits how most companies past a certain size actually structure their teams, regional property managers or regional offices each responsible for a geographic cluster of properties rather than one central team handling everything. During setup, you map each property to its regional manager or regional on-call rotation, so a maintenance emergency or leasing inquiry about a property in your Southeast region alerts the Southeast on-call staff, while a call about a Midwest property alerts that region's team, all through the same main number or through region-specific numbers if you maintain those separately. This avoids the common failure mode of centralized routing, where a call gets logged centrally but takes longer to reach the actual regional person who can act on it, or worse, reaches someone unfamiliar with that specific property's vendor relationships and escalation history. For companies where regional managers also have their own distinct policies, different application fees, different pet policies, or different maintenance vendor networks by region, those differences are configured at the property or region level the same way they would be for entirely separate owner portfolios. Centralized visibility still exists at the corporate level through Enterprise reporting, so leadership can see aggregate call volume, emergency response times, and lead conversion across every region, while each region's day-to-day call handling stays routed to the people who actually manage those properties. This structure scales reasonably cleanly whether you have 3 regions or 15, since adding a new region is a configuration addition rather than a rebuild of the whole routing setup.
More Industry Resource Centers.
Looking for something else?
Try Voksha
for Property Management Companies.
Set up your AI receptionist in under 5 minutes. 7-day money-back guarantee.