Customer service · Property management
‘Where is my work order?’ is not a new lead. It is customer service.
Once a tenant is in the building, the expensive calls are status, make-ready, and ‘what is the pet policy.’ That is not reception and it is not qualification. It is looking up what you already know without inventing a notice.
EXCEL answers from approved knowledge and connected work-order status. It does not evict, quote a ledger, or replace a manager on exceptions.
Open tickets generate more calls than new applicants
Tenants call three times about the same HVAC ticket. Make-ready dates slip and nobody tells leasing. Owners ask for a statement on the customer-service line. Policy questions get three different answers from three people.
What property customer service is allowed to say
Identify the open work order if a system is connected. Give status you actually have. Recite approved policy. Make-ready dates only if they are in the system. Everything else is a manager callback.
CS is not the first-ring lockout page
Status on an open ticket
Ticket id or unit + issue. Status from the system. No invented ETA if the vendor has not updated.
Make-ready for a new lease
Unit, move-in, what is left. Dates only from operations, not hope.
Policy lookup
Pets, hours, package rooms — from the document you maintain. Not a legal interpretation of a notice.
Enough to find the ticket
Who
Tenant vs owner vs vendor. Owners usually leave this line.
Which ticket
Number, unit, issue.
What they want
Status, reschedule, policy, something new (that may be reception again).
Access
If a vendor visit is the next step.
Hypothetical: work order 1842, still open
Hypothetical. Not a live property software integration demo.
I called Monday about no AC in 2B. Nobody came. What is going on?
I can look up an open work order if one exists. Is 2B the unit, and was the issue cooling?
Yes. Ticket 1842 if I remember.
If 1842 is in the system, I will read the last vendor status we actually have. I will not invent a time window or a ledger credit.
No ticket found → capture and a manager. Do not create a fake status.
CS hard stops for property
- Invent a vendor ETA
- Read or change a ledger, notice, or legal status
- Treat this as a vacancy / application pitch
- Give a lockbox code
- Handle a life-safety emergency as a status FAQ — that is the receptionist tree
Property CS configuration
- Which statuses are safe to read aloud
- Policy documents the agent may cite
- Make-ready fields if operations will maintain them
- Owner calls: almost always a person
- When a repeat caller escalates automatically
Managers still own exceptions
Credits, notices, identity mismatches, anything a vendor marked failed, angry repeat callers.
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
- AI ReceptionistA custom AI receptionist that answers calls, handles approved questions, captures leads, routes callers, and supports scheduling around how the business already works.
- AI Scheduling AgentScheduling AI that helps customers request or book appointments using the business’s hours, rules, and connected calendars when those connections are available.
Related guides
Questions for this workflow
How is this different from the property receptionist page?
Receptionist is who is calling and whether it is an emergency. This page is status and policy after a ticket exists.
Will it create a work order?
New issues can be captured. Creating in your software depends on the connection scoped in discovery.
Can it tell an owner the rent roll?
No. Ledger and owner reporting stay with people.
What if the vendor never updated the ticket?
Say that. An honest ‘no new status’ beats a fictional window.
Does it replace the answering service at night?
Life-safety after hours still belongs on the receptionist tree. This agent is for the questions that repeat during the week.
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.
What if it does not know the answer?
It should ask a clarifying question, capture the request, or escalate — not invent a policy.
Can it handle billing disputes?
Those should be marked human-only. The agent can collect context and route the conversation.
Bring the three questions tenants ask about open tickets. Those answers become knowledge — not improvisation.
Bring the real call types. We will tell you what belongs in an agent and what should stay with people.