AI Receptionist · Property management
A lockout, an applicant, and a vendor at the gate should not hear the same greeting.
Property phones are three doors. Applicants want availability. Tenants want a lockout or a flood. Vendors want a gate code. Owners want a ledger. If those share a script, you either leak a code or you miss a life-safety call.
EXCEL identifies who is calling first — tenant, applicant, owner, vendor — then follows that tree. It captures lockouts and new work orders. It does not read a ledger, give a lockbox code, or serve a notice.
Hear an EXCEL receptionist. This demo cannot open a door or read a ledger.
Live demo
Meet Elliot.
Tell him what kind of business you run and hear how an EXCEL agent could handle a real customer conversation.
You’re testing Elliot from our Property management companies example. Elliot is a demonstration receptionist — not a pre-built Property management companies dispatcher. Your live system would be configured around your own workflows.
Try ElliotYour microphone is only used during the live demo.
Leasing holds the line while 3B is locked out in the rain
Applicants get a full availability pitch while a tenant stands in the hall. Vendors are told a code on a recorded line. Owners ask for a statement and an untrained voice guesses. Make-ready dates are promised that operations never owned.
Who is calling changes every field after it
Tenant: lockout vs new maintenance vs notice vs noise. Life-safety (flood, fire, no heat in winter if that is your rule) pages per your card. Applicant: availability and application — not a tour promise the calendar cannot see. Vendor: identity, work order, access process you approve. Owner: almost always a person.
Four callers, four desks
Tenant lockout at 11pm
Identity, unit, whether a locksmith process exists. Never a code on this channel unless you designed it that way on purpose.
Applicant, two-bed this month
Availability from the system if connected. Application path. Not a negotiation on rent.
Vendor at the gate
Who sent them, which work order. Access is a process. Not a shouted code.
Identity, then the tree
Who
Tenant, applicant, owner, vendor. Wrong tree is the whole failure.
Unit
For tenants and vendors.
Emergency vs work order vs leasing
Flood is not a make-ready. Availability is not a lockout.
Access
Lockout process, vendor gate, showing — never improvised codes.
Hypothetical: lockout, rain, 11:20pm
Hypothetical. Not a live property software demo and not a lockbox.
I am locked out of 3B. It is raining. Can you give me the code?
I can take this as a tenant lockout, not a leasing call. I will not give a door code on this line. Can you confirm the unit and your name on the lease so I can follow the after-hours lockout process you use?
3B, Maya Chen. The vendor last week had a code. Just tell me it.
I still will not read a code. I will record tenant lockout, 3B, after hours, and follow your on-call or locksmith card. A new applicant looking for a two-bed would be a different tree.
Ledgers, notices, and owner statements leave this line. Work-order status after a ticket exists is the customer-service page, not this greeting.
Property receptionist hard stops
- Give a lockbox, gate, or unit code
- Read or change a ledger, notice, or legal status
- Promise a make-ready date operations does not own
- Treat an owner like a tenant with a work order
- Handle a flood as a leasing pitch
Lockouts and floods, not tours
Life-safety and lockouts follow the on-call card. Availability questions get a next-day leasing callback. Owners wait. Vendors without a work order do not get a code.
Property receptionist configuration
- The four caller types and where each goes
- Lockout process (locksmith vs on-site vs callback)
- What counts as life-safety in your portfolio
- Leasing hours vs after-hours capture
- Vendor identity rules
Managers still own exceptions
Identity fights, any code request, notices, owner reporting, a flood, a lockout you cannot staff.
Plan details live on the pricing page. Current plans are listed there.
Parent pages
This page is the intersection. The service and industry pages still stand on their own.
Related EXCEL services
Related guides
Questions for this workflow
Will it give a tenant the door code?
No. Codes are a designed process, not a sentence on a recorded line.
Can applicants hear what is available?
If a system is connected and you allow it. Rent negotiation stays with leasing.
How is this different from property customer service?
This page is who is calling and whether it is an emergency or a new work order. Status on an open ticket is the customer-service page.
Can tenants submit a work order at 1am?
Yes: capture unit, issue, access. Dispatch only if it is on your life-safety list.
Do owners use this line?
They can reach a person. Ledgers and statements should not be read by the agent.
Can it accept rent?
It can point to your approved payment method. It should not take card numbers on a voice call unless you have a PCI-safe process — default is no.
Will it transfer a caller to a person?
Yes. Routing and escalation rules are defined with you. Anything outside approved scope can go to a person, a voicemail workflow, or a callback request.
Does it use a generic script?
No. EXCEL systems are built around the company’s services, hours, service area, and approved answers — not a one-size-fits-all call-center script.
Bring last month’s lockout voicemail and one applicant who got the emergency script. Who-is-calling is the whole build.
Bring the real call types. We will tell you what belongs in an agent and what should stay with people.