An AI answering service for your property management business
Tenants call about a leaking ceiling. Prospects call about a listing. Cysora tells them apart, gathers what each one actually needs — the unit, the lease, the issue — and routes it correctly, instead of treating every call the same.
No credit card required. Preview before you commit.
Worked examples
How a call gets routed to the right workflow
Tenant maintenance request
Caller: "There's water coming through my ceiling in unit 4B."
The agent asks:
- Is the water actively dripping or pooling right now?
- Can you confirm the unit number and building?
- What's the best number to reach you?
Job summary
- Issue
- Active water intrusion — unit 4B, matches the configured emergency-maintenance rule
- Service area
- Unit and property confirmed against the configured portfolio
- Preferred time
- Priority routing, per the configured emergency-maintenance rule
- Next action
- Routed to the configured maintenance contact or vendor for that property — the agent coordinates the request, it doesn't dispatch a repair itself.
- Captured details
- Unit and building · Callback number · Nature and severity of the issue
Why this outcome: The business's own definition of "emergency maintenance" — not the agent's judgment — decides priority routing, and the destination (in-house team or a vendor) is whatever's configured for that property.
Prospective tenant enquiry
Caller: "I saw your two-bedroom listing online — is it still available, and can I see it?"
The agent asks:
- Which property or listing were you looking at?
- What move-in date are you targeting?
- What's your name and the best way to reach you?
Job summary
- Issue
- Leasing enquiry — availability check against the configured unit list
- Service area
- n/a — leasing, not maintenance
- Preferred time
- Showing slot offered from the configured availability, if the unit is open
- Next action
- A showing is booked if the unit is available; if not, the agent says so plainly and offers the configured next step (a waitlist or similar listings) rather than pretending it's open.
- Captured details
- Name and contact · Unit/listing of interest · Target move-in date
Why this outcome: Availability is checked against what's actually configured — the agent never guesses or promises a unit is open without a real answer.
Routine tenant question
Caller: "My lease is up in two months — what do I need to do to renew?"
The agent asks:
- Can you confirm your unit and name so I can log this correctly?
- Is there anything specific about renewal you wanted to ask, or just how the process works?
Job summary
- Issue
- Lease renewal question — routine, no maintenance component
- Service area
- Unit confirmed against the configured portfolio
- Preferred time
- Not urgent — logged for the leasing team's normal workflow
- Next action
- Logged to the Lead Inbox for the leasing team; caller told plainly when to expect a follow-up rather than left wondering.
- Captured details
- Unit and tenant name · Nature of the renewal question
Why this outcome: Routine tenant questions are logged and routed, not answered with invented lease terms or renewal pricing the agent doesn't have.
How it’s built
The same configurable engine, applied to your business
Every Cysora agent runs on the same four-step engine — what makes it yours isn’t a different template, it’s the rules you configure inside each step. Here’s how those four steps actually play out for a business like yours:
Asks the right questions to understand exactly what the caller needs — configured by you, not a fixed script.
It separates a tenant's maintenance issue from a prospect's listing question in the first exchange, since they need completely different handling.
Checks the request against your own configured rules and examples before deciding what happens next.
For prospects it checks real unit availability from what you've configured — never an invented "yes, it's open."
Turns what it learned into a concrete next step, following your pricing, scheduling, and escalation rules.
For tenants it applies your own definition of an emergency to decide priority routing, not a fixed SLA the agent makes up.
Books the visit, logs the lead, or hands off — exactly the way you've configured it to end.
It ends in a booked showing, a logged maintenance ticket, or a routed request — never a lease signature.
Personalize
How your portfolio and routing rules are configured
You set which properties and units it knows about, what counts as an emergency maintenance issue versus routine, who gets notified for each, and what a prospective tenant needs to hear about availability and move-in dates — the same distinctions you'd give a new leasing coordinator.
Scale
Every channel, one conversation
You edit the modules and rules above once, in one place — the resulting agent deploys across every channel below without separate setup for each.
Embedded on the property management company's own website.
Same conversation continues over WhatsApp for callers who prefer to text.
Answers your phone line directly — the same agent, the same configured rules, whether the call comes in by voice, web, or WhatsApp.
Replies from your business inbox with the same configured rules — the same agent whether the conversation started by phone, WhatsApp, web, or email.
The same configured agent answers every channel it's deployed on, so a tenant who starts on the website and later texts gets consistent answers instead of repeating themselves to a different system.
Questions before you try it
What buyers ask first
Does it know the difference between a tenant and a prospective renter?
It asks the questions that make the distinction — a unit number and issue points to a tenant, a listing and move-in date points to a prospect — and routes each accordingly. See the scenarios above.
How does it know which units are actually available?
You configure the property and unit list it works from. It checks a caller's request against that — it doesn't guess or promise availability it can't confirm.
Can it handle multiple properties, not just one building?
Yes — you configure the full portfolio it should recognize, so a caller can mention any property you manage and get routed correctly.
Does it dispatch a maintenance vendor itself?
No — it routes the request to whoever you've configured (your team or a vendor) for that property. It coordinates the request; it doesn't perform or schedule the repair itself.
Can I keep my existing business number?
Yes — forward your existing number to the agent rather than handing out a new one.
What does setup involve?
Your property and unit list, what counts as emergency maintenance, and who gets notified for each — a configuration pass, not new phone hardware.
What’s out of scope today
- Does not dispatch or perform maintenance itself — it routes the request to your configured team or vendor.
- Does not quote rent, fees, or lease terms unless the business has configured that information.
- Does not process payment or sign a lease — leasing and maintenance coordination only.
Also built for
Advertise
Once tenant and prospect calls are routing reliably, the leasing-specific language it captures — which units get asked about, which move-in dates are common — is what should inform the property manager's paid search and listing spend.
How this example was produced
Reproducible internal demonstration, synthetic caller data
The scenarios above reflect how a property-management-style agent is actually configured in the Cysora builder, run against synthetic caller scenarios.
Last checked 2026-09-08
No credit card required. Preview before you commit.