All use casesMaintenance · rent · safe document uploads

Property Manager — Tenant Support & Rent Bot

Property managers run on inbox triage. This workflow replaces three channels (the maintenance line, the rent portal, the document email thread) with one Telegram bot — and adds an AI severity check so real emergencies actually get paged.

Operations 6 min read

What it does

Three flows in one bot. Tenants describe a maintenance issue and AI classifies it as urgent or normal, automatically paging your on-call team for emergencies. Rent is collected right inside the chat. Every file a tenant uploads is scanned for safety before anyone on your team has to open it.

  • Tenant describes an issue → AI rates it urgent or normal in seconds
  • Urgent issues page your on-call team before the tenant even sees the reply
  • Rent collected via in-chat payment — no portal handoff or late-fee phone calls
  • Every tenant file is scanned against 70+ antivirus engines before being accepted

What you get

  • A tenant types /maintenance and describes the issue — the bot triages it within seconds
  • Urgent issues fire a notification to your on-call channel; normal ones go into the daily queue
  • Rent is paid in three taps: invoice, card, receipt — all inside Telegram
  • Documents are scanned automatically — clean files are accepted, flagged files are rejected

What you’ll need

VirusTotal API key

Powers the file scanning step. The free tier is plenty for low-volume properties. Without a key, the document flow fails safe — files are treated as unsafe by default.

On-call notification URL

Where urgent maintenance issues get paged — a Slack webhook, PagerDuty, Opsgenie, or anything that accepts a JSON POST.

Telegram payment provider token

Same connection as in the restaurant workflow — connect Stripe to your bot via @BotFather and paste the token into the rent collection step.

Rent amount per property

The template ships with a placeholder amount. Update it in the rent collection step to match the property — or duplicate the workflow per building.

How it works

1. Maintenance flow — /maintenance

The tenant types /maintenance and describes the issue in their own words. AI reads the description, classifies it as urgent or normal, picks a category (plumbing, electrical, HVAC, etc.), and writes a short reasoning.

Urgent path

Your on-call channel gets a real-time notification with the tenant’s name, the issue, and the AI’s reasoning. The tenant is told help is on the way.

Normal path

The issue is logged and the tenant gets a "we’ll respond within 24 hours" acknowledgment so nothing feels ignored.

2. Rent collection — /rent

The tenant types /rent. The bot sends an in-chat invoice. The tenant pays with a few taps and immediately receives a receipt with the payment reference. No external portal, no email forwarding.

3. Document uploads

Any time a tenant attaches a file (lease addendum, insurance proof, ID), the bot scans it against dozens of antivirus engines before anything else happens. Clean files are accepted and acknowledged; flagged files are rejected automatically.

Why it works

  • One bot collapses three traditionally fragmented tenant interactions into a single channel both sides actually use.
  • AI triage means real emergencies get paged in real time — not lost in an inbox until Monday.
  • File scanning happens before anyone on your team opens the attachment, so an infected upload can’t become an infected laptop.

Build it with AI

Generate this workflow from a prompt.

Copy the prompt below and paste it into Eavur’s AI workflow builder. It builds the whole flow for you — then just drop in your API keys and go live.

AI builder prompt
Build a Telegram bot for property management with three separate flows.

1) On /start, send a welcome message listing the available commands.

2) Maintenance — on the /maintenance command, ask the tenant to describe the issue, await their text and save it as issue_text, show a typing indicator, then use an "Ask AI" node that classifies the issue with URGENT or NORMAL as the FIRST WORD, plus a short [category] and one sentence of reasoning; save the result as severity. Use a text condition to check whether severity contains "URGENT". If urgent: send an HTTP POST request to an on-call webhook with the tenant name, chat id, issue, and AI triage as JSON, then tell the tenant on-call has been paged. If normal: tell the tenant the issue is logged and will be handled within 24 hours.

3) Rent — on the /rent command, send a Telegram payment invoice for $500.00 monthly rent, auto-approve the pre-checkout query, and on successful payment send a receipt confirmation message.

4) Documents — when a document is uploaded, show an "upload document" chat action, scan the file with the VirusTotal virus scanner node, extract the "flagged" value from the result, and use a boolean condition: if flagged is true, reject the file with a warning that it was not stored; if false, accept and acknowledge the file.

Use an OpenAI model for the AI node. I'll paste my VirusTotal API key, on-call webhook URL, and Stripe provider token into the relevant nodes, and adjust the rent amount, afterwards.

More use cases