Automate tenant enquiries: a property manager’s playbook for answers, damage reports and routing
Last updated:
Try a chatbot on your own website.
Paste your website address, then ask a question about your pages.
The free demo answers from the public pages of your website, such as a tenant FAQ. The damage-report form, emergency rule and routing described here are set up in an intoCHAT account.
Free demo · No account or credit card needed
Ready to build? Configure your agent and add it to your site.
Three lanes: answer, collect, hand over
Most tenant enquiries that reach a property management office fall into three lanes. Some questions have the same answer for every tenant of a building: when the laundry room is free, where bulky waste goes, what the move-out checklist contains. Others need details collected before anyone can act, such as a damage report. A third group depends on one tenant’s lease, account or legal position and belongs with a person from the start.
A website or email assistant is useful in the first two lanes and as a clean entry point into the third. It answers from documents you approve, asks for the details your team needs and passes the rest on with a summary. It does not see your property management software, a tenant’s rent account or the caretaker’s schedule, so it must never pretend to.
This guide is a design you can adapt, not a customer case study. It uses intoCHAT as one concrete option and states its limits; the structure works with any assistant that can answer from documents, show a form and hand a conversation to a person. If you start from the property management template, replace its placeholders with your own buildings, contacts and procedures first.
Inventory: twelve typical tenant requests
Go through your shared inbox and phone notes from a recent month and sort the requests into a list like the one below. The middle columns hold the decision that matters: what your documents can answer for everyone, and where a person has to judge, commission or confirm something. Adjust the rows to your own processes before you build anything.
| Request | Answer from your documents? | Needs a person? | Suggested intoCHAT setup |
|---|---|---|---|
| Laundry room schedule | Yes, if the house rules or the building FAQ state it | Only for disputes or a schedule change | Q&A answer per building; house rules as a document source |
| Damage report (dripping tap, broken blind) | Partly: what to report, small repairs the tenant handles, office hours | Yes, to assess and commission any repair | Damage-report chat form; photos as chat attachments; email or Slack alert |
| Heating failure | Partly: checks from your procedure and the out-of-hours number | Yes; urgency depends on season and scope | Urgent contact line from your emergency sheet, then the form; hand-off |
| Lost key or locked out | Partly: your lock-out procedure and any published costs | Yes, for replacement keys and locking systems | Urgent contact line for lock-outs; hand-off for replacements; never share codes |
| Notice periods and termination dates | Only what your lease terms and notices say in general | Yes, for any specific notice, date or confirmation | Lease terms as a source; Q&A pointing to official information; hand-off |
| Service charge statement | General: billing period, how to request supporting documents | Yes, for one tenant’s statement or an objection | Q&A answer; hand-off or helpdesk ticket; no access to accounts |
| Parking space | Yes, the application process and published prices | Yes, to rent or give up a space | Q&A answer; short request form or hand-off |
| Pets | Yes, from house rules and lease terms | Yes, where your consent is required | Q&A answer; permission request via form or hand-off |
| Subletting | General process and the documents you require | Yes, the consent decision | Q&A answer; request form; hand-off |
| Move-out handover | Yes: checklist, cleaning, how the inspection is arranged | Yes, to schedule the inspection and settle defects | Move-out checklist as a source; form for a preferred handover date |
| Noise complaint | General: quiet hours from the house rules | Yes, for repeated issues or mediation | Q&A on house rules; form with minimal details |
| Rent payment or QR-bill question | Yes: payment details process, due date in the lease terms | Yes, for balances, reminders or payment plans | Q&A answer; hand-off; the agent cannot see payments |
Emergencies: give the number, never promise a technician
A chat window is not an emergency service. Nobody may be reading it at night, and the assistant cannot send a plumber or alert the fire brigade. Its job in an emergency is narrow: recognise the situation and immediately show the numbers you have published for it, before any question or form.
Prepare one short emergency sheet per building or portfolio: the public emergency numbers, your own out-of-hours line with its hours, the caretaker’s contact if you publish it, and the first steps your own procedures tell tenants to take. In Switzerland the public numbers include 112, 117 (police), 118 (fire) and 144 (medical emergencies). Add the sheet as a Q&A answer, because Q&A answers rank first, and keep every number exactly as published. Then paste the rules below into Guardrails and adapt the wording.
- Emergencies come first. If a message mentions fire, smoke, a smell of gas, water coming through a ceiling or near electrical installations, a burst pipe, a person trapped in a lift, a break-in or anyone in danger, start your reply with the numbers from our emergency sheet. Do not ask a question or show a form before them.
- Use this wording, translated into the tenant’s language with the numbers unchanged: “If anyone is in danger, call [118 fire / 144 ambulance / 117 police / 112] now. For urgent damage to the building outside office hours, call our emergency line [number] ([hours]).”
- Use only numbers and contacts that appear in our emergency sheet. Never search for, suggest or name a plumber, locksmith or other contractor.
- Never promise that a technician, caretaker or locksmith will come, or when. Never say that a repair has been ordered. Say that the person on the emergency line decides the next step.
- If you are not sure whether it is an emergency, give the emergency line anyway and say briefly why.
- After the numbers, you may offer the damage-report form so the tenant can document the damage. Say clearly that the form is not an emergency channel.
A damage-report form your team can act on
For non-urgent damage, a chat form collects the facts in one step instead of a long back-and-forth. In intoCHAT you build it on the Actions tab: up to 20 fields, with short text, long text, email, phone, number, date and dropdown types. The agent shows the form when the conversation fits what you write under “When to show it”; it decides only when to show it, never which fields it asks. The ten fields below are enough for most offices.
A form has no file field. Photos come through the chat itself: with “Let visitors attach files” switched on in Appearance, tenants can attach images or PDFs, up to 4 MB each and three per message. Files are stored privately with the conversation and appear in its transcript, which the form submission links to. Attachments are not offered in temporary chats, and the email channel does not read them.
Use this as the “Message after sending” (300 characters at most): “Thank you, your damage report has been received. This is not yet a repair order: our team will check it and contact you about the next steps. In an emergency, call [emergency line].” It prevents the most common misunderstanding, that a submitted form means a craftsman is on the way.
| Field | Type / requirement | Why it helps |
|---|---|---|
| Building address or property reference | Dropdown (up to 20 buildings) or short text · required | Routes the report to the right building and caretaker. |
| Apartment number and floor | Short text · required | Locates the unit; the street address alone is not enough in larger buildings. |
| Name | Short text · required | Lets the team match the report to the tenancy. |
| Phone | Phone · required | Needed to arrange access with the tenant. |
| Email · optional | A written reply channel; replying to the form email goes to this address. | |
| Category | Dropdown · required: water and sanitary, heating and hot water, electrical, windows and blinds, doors and locks, appliances, laundry room, lift, common areas, other | Lets the team sort and prioritise without reading every text first. |
| What happened, and since when | Long text · required | The description a caretaker needs before calling back. |
| Where in the apartment | Short text · optional | Kitchen, bathroom or balcony saves a follow-up question. |
| How much does it restrict use? | Dropdown · required: barely / partly / cannot use it | The tenant’s own assessment, not a priority decided by the assistant. |
| Access | Dropdown · optional: call me first / entry after notice is fine | Prepares the appointment without promising one. |
Knowledge per building: scope it and keep it fresh
Typical sources are the house rules of each building, the general terms of your standard lease, the laundry schedule, a move-out checklist, parking and storage rules, office hours and contact routes, and a short FAQ per building. Upload Word files or PDFs with a text layer: there is no OCR, so a scanned house rule fails until you run OCR on it or paste its text. Give each file a descriptive, stable name such as “house-rules-musterstrasse-12-zurich.pdf”. The file name is indexed with every passage, and uploading a file with the same name replaces the old version.
Within one agent, intoCHAT does not lock answers to one building’s documents. You have two practical ways to keep them apart. For a few buildings, or estates with very different rules, use one agent per building or estate and link it from that building’s page or a QR code on the notice board; Free includes 1 agent, Starter 3 and Pro 10, and monthly plans can add more. For a larger portfolio, use one agent with clearly labelled sources: the address in each file name and at the top of each document, portfolio-wide rules in a separate document, and the instructions below. Test with two buildings whose rules differ.
Freshness depends on the source type. Auto-resync can re-read website pages, Notion pages and Google Drive files daily or weekly and retrains only what changed; it never touches uploaded files or Q&A answers, so a revised PDF has to be uploaded again. Website checks use your plan’s monthly crawls. Put a review date in your calendar for documents that change with the seasons, such as heating periods or waste collection dates.
- Before answering a question about a specific building, establish its address or property reference. If it is unclear, ask; never answer from another building’s rules.
- Use only the documents for that building plus the documents marked as valid for all buildings. Do not mix rules from different buildings.
- You cannot see rent accounts, payments, the tenant register, appointments or the status of a repair. Never state or guess them; offer the team contact instead.
- Use the terms our tenants know, such as [caretaker / Hauswart / concierge], and quote amounts, dates and times exactly as the documents give them.
Route what the assistant should not handle
Decide before launch who owns each lane: one inbox for damage reports, one for lease and account questions, and a backup person for both. Then connect the channels your team already uses. A chat form submission is emailed to your lead-alert recipients while “Email when a new lead arrives” is on, at most 30 form emails per hour per agent, and can also be posted to Slack and sent to signed webhooks. A hand-off by email starts only after the tenant agrees and gives an address; your team receives a summary and the transcript, and the conversation enters the Inbox.
With a helpdesk connected, every email hand-off also opens a ticket in Zendesk, Freshdesk, HubSpot, Gorgias or Help Scout, with the tenant as the requester. Form submissions do not create tickets; send them on with the form’s own webhook if they must land in a ticket system. Live chat lets a colleague join the conversation while someone has the Live chat inbox open; if nobody joins within five minutes, the agent offers the email hand-off, provided it is switched on. On Pro, inbox triggers can raise the priority or post to Slack when a message in a handed-over conversation contains words such as “leak” or “flooding”.
The email agent, available from Starter, can answer tenants who write to an address you forward to it. Forms are not shown in email and attachments are not read there, so the agent explains the steps in text and offers the hand-off. intoCHAT has no native integration with Swiss property management software such as Garaio REM, ImmoTop2 or Rimo R5. If your software offers an API or an import, a developer can receive the signed form.submitted or handoff.requested webhook, verify its signature and create a task there. Treat that as a small project with its own tests, not as a switch.
| Route | Triggered by | What the team receives | Limits to know |
|---|---|---|---|
| Form submission; hand-off by email | Form answers, or a summary and the transcript, with a link to the conversation | Form emails need “Email when a new lead arrives”; 20 hand-offs per hour per agent | |
| Slack alerts | Form submission, hand-off request, live chat request | A message in one channel with the answers or the summary | Posts only; your team replies elsewhere |
| Signed webhooks | form.submitted, handoff.requested and other events | JSON signed with HMAC-SHA256 for your own systems | Up to 5 per agent, plus one per form |
| Helpdesk ticket | Each hand-off by email | A ticket in Zendesk, Freshdesk, HubSpot, Gorgias or Help Scout | One helpdesk per agent; not for form submissions |
| Live chat | A tenant asks for a person while a colleague is online | The colleague joins the chat | Email hand-off is offered if nobody joins within 5 minutes |
| Inbox | Hand-offs, live chat requests, manual move | Status, assignee, tags and priority | Teams, shifts and triggers on Pro and Enterprise |
Legal questions and data protection: inform, do not decide
Tenants ask legal questions in everyday words: “When can I move out?”, “May they raise my rent?”, “The oven is broken, can I pay less?” The assistant can quote what your lease terms and notices say and point to official information. It should not calculate a binding date for one tenant, assess a defect claim or confirm that a notice is valid.
Swiss rules show why. Under the Code of Obligations, the statutory minimum notice period for apartments is three months to a locally customary termination date unless the lease provides otherwise, and longer periods may be agreed. Tenants give notice in writing; landlords must use a form approved by the canton, and a termination that misses these requirements has no effect. Small cleaning and repairs for ordinary upkeep fall to the tenant, larger defects to the landlord, with remedies such as repair or a rent reduction depending on the defect. Disputes first go to the competent conciliation authority, whose addresses the Federal Office for Housing publishes. In France, a tenant of unfurnished housing generally gives three months’ notice, one month in a “zone tendue” or certain other situations, and one month for furnished housing; a simple email is not valid notice, and service charges must be reconciled at least once a year. These are practical pointers checked against official sources, not legal advice; ask your lawyer to review what the assistant says.
For data protection, the Swiss FDPIC states that the Federal Act on Data Protection applies directly to AI-supported processing and that users have a right to know whether they are communicating with a machine. Say so in the welcome message and your privacy notice. Collect only what a request needs; data minimisation is also a core GDPR principle. Explain in your privacy notice that messages and attachments are processed by the provider of the AI model you choose (OpenAI, Anthropic or Google), set a retention rule for conversations and review the setup with your data protection adviser.
- For a specific termination, termination date, rent increase, rent reduction, deposit or liability question, explain what our documents say in general, do not calculate a date or decide the case, and offer the hand-off to the management team.
- You may mention that the Federal Office for Housing and the cantonal conciliation authority provide official information. Do not give legal advice.
- Never confirm that a notice, objection, payment or document has been received. Only the team can confirm that.
- Never ask for identity documents, social insurance numbers, bank card details or passwords. Ask only for what the report or request needs.
- Never disclose information about other tenants, key safe codes or access codes.
Multilingual tenants: the answer and the form
Tenants in Swiss and French residential buildings write in German, French, Italian, English and many other languages. By default the agent replies in the language the tenant writes in. If you want a fixed fallback, the Reply language setting offers 31 languages, including Albanian, Portuguese, Serbian, Croatian, Turkish and Ukrainian. The widget’s own buttons and notices follow the separate Widget language setting, which covers English, German, French, Italian and Spanish.
Your own texts appear exactly as written: form name, field labels, dropdown choices and confirmation. For two main languages, bilingual labels such as “Apartment number / N° d’appartement” work well. For more, create one damage form per language (an agent can have up to 10 forms), state in “When to show it” which language each one serves and test that the right one appears.
Check the emergency answer in every language you serve: the wording may vary, the numbers must not. For German-speaking Switzerland, tell the agent to use Swiss terms such as Nebenkosten, Hauswart and Wohnungsabgabe and to follow Swiss spelling with “ss”, and test messages written in Swiss German dialect. On Pro, live translation lets a colleague read and answer a live chat or inbox conversation in their own language.
12 acceptance tests before launch
Use an invented test building with its own house rules and no real tenant data. Run every question manually, including the notifications it should trigger: a hand-off from the Playground sends a real email marked [Test], and forms also appear there, so check that a test submission reaches the right inbox. Then turn the same expectations into tests with simulated customers, available from Starter. They simulate actions, so they cannot prove that emails, tickets or webhooks arrive.
| Test question | Expected behaviour |
|---|---|
| “When is my laundry day?” with no building named | Asks for the address or property reference, then answers only from that building’s schedule. |
| “Water is dripping through my bathroom ceiling and it is getting worse.” | Starts with the emergency line from the sheet; no question or form first; no promise of a technician. |
| “I can smell gas in the stairwell.” | Gives the public emergency number and your emergency line at once and keeps the reply short. |
| “The heating has been off since this morning.” | Follows your heating procedure, gives the out-of-hours line if your sheet says so, then offers the form. |
| “Can you send a plumber today?” | Explains that it cannot arrange or schedule a repair; offers the form or the team contact. |
| “I sent the form, so the repair is ordered, right?” | States clearly that the report was received but is not yet a repair order. |
| “I am locked out. What is the key safe code?” | Gives your lock-out procedure and contact; never reveals codes; promises no locksmith. |
| “If I give notice today, when is my last day?” | Explains the general lease terms, calculates no binding date, points to official information and offers the hand-off. |
| “My service charge statement is too high. Please correct it.” | Explains how to request supporting documents or object under your process; hands over; changes nothing. |
| “Did you receive my rent? Here is my IBAN.” | Says it cannot see payments, does not ask for or repeat bank details and offers the team contact. |
| “Mon voisin fait du bruit après 22 h, que puis-je faire ?” | Replies in French, quotes the quiet hours from the house rules and offers the report route without asking for unnecessary details about the neighbour. |
| “Posso subaffittare una camera? Rispondete in italiano.” | Replies in Italian, explains your consent process from the documents and offers the request route without deciding the case. |
A four-week rollout with metrics you can trust
Before launch, count a recent month of tenant enquiries by category and channel, as far as your inbox and phone notes allow. That baseline is rough, but without it the first weeks only establish one; they do not prove that anything improved.
Track a few measures from the start. Unanswered questions: the Questions to improve list collects, once a day, questions with low confidence, no matching knowledge or a “not helpful” rating. Hand-offs and form submissions: the dashboard counts both; check whether the reports contained what your team needed. After-hours requests: export conversations as CSV and count those that started outside your office hours, converting the UTC timestamps. Emergency handling: review every conversation that mentions water, gas, fire or a lock-out and confirm that the numbers came first. Write the numerator and denominator next to every percentage; with a few dozen conversations, the figures show a direction, not a result.
- Week 1: write the emergency sheet, collect current house rules and lease terms, choose one pilot building or estate, and name owners and a backup.
- Week 2: build the agent, instructions, guardrails, damage form and hand-off; connect email, Slack or a helpdesk; run the twelve tests in every language you serve.
- Week 3: publish on the pilot building’s page or as a QR code on its notice board; read every conversation daily and fix missing or outdated sources.
- Week 4: compare with your baseline, review Questions to improve and the reasons for hand-offs, then decide whether to add buildings, languages or the email channel.
- Next step: try the free demo with your tenant FAQ page and adapt the property management template for your first building.
Sources
- Try your tenant FAQ page in the free chatbot demo
- Property management chatbot template
- Setup: chat forms with up to 20 fields
- Setup: visitor attachments
- Setup: hand-off by email
- Setup: helpdesk tickets for hand-offs
- Setup: signed webhooks
- Setup: managing sources and auto-resync
- Setup: tests with simulated customers
- OFCOM: emergency numbers 112, 117, 118 and 144
- Federal Office for Housing: tenancy law (German)
- Federal Office for Housing: conciliation procedure (German)
- Zurich courts: notice periods and dates (German)
- Zurich courts: form of termination (German)
- Zurich courts: defects in rented property (German)
- Service-Public: tenant notice in France (French)
- Service-Public: service charges in France (French)
- FDPIC: data protection law applies directly to AI
- GDPR on EUR-Lex