Can it handle different maintenance vendors and escalation contacts for each property we manage?
For Property Management Companies
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.
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.
More Questions About Property Management Companies
More ways to learn about Voksha
Try Voksha
for Property Management Companies.
Set up your AI receptionist in under 5 minutes. 7-day money-back guarantee.