1. Acknowledge concern
What happened?
Captures complaints calmly, separates urgent risks from disputes, and sends a documented summary to managers.
What happened?
When did it happen?
Is anyone unsafe or at risk right now?
What happened?
When did it happen?
Capture tenant complaints by phone. Stay neutral, ask what happened, when, who was involved, evidence available, and safety concerns. Escalate sensitive matters and save a complaint record.
{
"outcome": "Tenant complaint intake outcome",
"fields": [
{
"description": "caller name captured during the call.",
"name": "caller_name",
"required": true,
"type": "text"
},
{
"description": "phone number from caller id captured during the call.",
"name": "phone_number_from_caller_id",
"required": true,
"type": "text"
},
{
"description": "property captured during the call.",
"name": "property",
"required": true,
"type": "text"
},
{
"description": "unit captured during the call.",
"name": "unit",
"required": true,
"type": "text"
},
{
"description": "complaint type captured during the call.",
"name": "complaint_type",
"required": true,
"type": "text"
},
{
"description": "incident time captured during the call.",
"name": "incident_time",
"required": false,
"type": "date"
},
{
"description": "evidence available captured during the call.",
"name": "evidence_available",
"required": false,
"type": "text"
},
{
"description": "risk level captured during the call.",
"name": "risk_level",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Tenant complaint intake. What happened?
Caller: I need to report repeated noise from upstairs.
AI: When did it happen?
Caller: It happens after midnight and I have recordings from this week.
Make the first screen and opening line match what the caller will actually get. For Tenant complaint intake, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.
Decide which fields are required before the call can be considered complete. A practical first version should capture caller name, phone number from caller id, property, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.
Write down the cases that should not be automated. Use human review for threats, harassment, discrimination claim, safety issue, caller is highly distressed so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.
Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for property management, hoas, student housing.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "What happened?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.
Save a structured result with caller name, phone number from caller id, property, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.
Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: threats, harassment, discrimination claim, safety issue, caller is highly distressed.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.