Tenant portal or WhatsApp: which job goes where in a rental building

The short answer

If your problem is that tenants have nowhere to pay, check a receipt or find their agreement, you need a portal, and no chat will fix that. If your problem is that the office spends the morning answering the same thing, repairs arrive half-explained and nobody reads the notices about building works, a fuller portal will not fix that either, because tenants are already writing to you somewhere else.

Most rental buildings end up with both, each doing its own job. What goes wrong is asking the portal to be the channel for conversations, or asking WhatsApp to act as the till and the filing cabinet.

What a tenant portal is and what it is for

Tenant portal, resident portal, customer area or tenant app are names for the same thing: a website or an application where each person logs in and sees what is theirs. It is not usually bought on its own. It comes with the rental management software, which is where agreements and payments live, and it shows the tenant a slice of that data. With variations, nearly all of them cover five things:

• Payments. The month's rent, utilities passed on to the tenant, a returned direct debit that has to be put right. Each with its proof of payment.
• Invoices and receipts. The whole history, to download when the tenant's employer, the bank or the tax return asks for it.
• Agreement and documents. The signed tenancy agreement, its annexes, the inventory of the flat, the energy certificate, the building's rules.
• Details and requests. Changing the direct debit account, adding an occupant, asking for a certificate, giving notice of not renewing.
• Repairs. A form to report a fault, with its category and, sometimes, a status tracker.

The first four have something in common: they are jobs with an amount, a signature or a document behind them. They need the tenant to be identified, to see an exact figure and to be able to download a piece of paper. There a portal has no substitute. Nobody should have to find an agreement three months later by scrolling up a conversation, and proof of payment cannot depend on someone forwarding it.

It has another strength that gets noticed less: the portal reads from the same place the accounts team works in. If March's rent shows as paid in the software, it shows as paid in the portal, without anyone copying it across by hand.

What a portal struggles with: getting anyone to log in

A portal is designed for jobs that come up rarely. A tenant who pays by direct debit can go months without a reason to open it. And what is seldom used gets forgotten, with three consequences every lettings office knows:

• The password. It was created on signing day, among the removal boxes. The first time it is really needed it no longer works, and the job starts with an email to the office asking for a new one.
• The notice nobody sees. The portal notifies by email or with a notification of its own. A water shut-off announced that way reaches, with luck, whoever checks that inbox before nine.
• The empty repairs form. With the dishwasher leaking, nobody goes looking for a username. They ring the office, message the phone of whoever showed them the flat or tell the caretaker. The repair gets reported, but outside the system.

None of this is a flaw in the software. It is what happens when a tool built for what comes up now and then also has to deal with what comes up every day. The result is a building with a perfectly good portal and, next to it, an office phone that never stops.

WhatsApp with an assistant: what it settles and where it stops

We do not mean the neighbours' group chat or the manager's personal mobile, but a number belonging to the building that the tenant saves on the day they sign. At the other end an AI assistant answers with what the building has in writing, and whatever is not its call it puts on the phone of someone in the team. How that differs from a group is covered in WhatsApp group or assistant.

It settles exactly what the portal handles badly: the frequent, the urgent and whatever starts with a stray sentence. There is no username to remember. The message gets read because it lands in the same place where the tenant reads their family's. And a photo of a ceiling with a stain says more than any drop-down list of categories.

Where it stops, plainly:

• It is not a till. Rent is not paid through a chat, and bank details should not travel in messages.
• It is not a filing cabinet. A conversation is no place to keep an agreement or to look for last year's invoice.
• It does not sign. A renewal, an annex or a key handover each need their document.
• It cannot see the figures in your software. Unless it is connected to the management system, it does not know what anyone owes or which receipt is outstanding.
• It answers what is written. If the rules are silent about barbecues on the terrace, the assistant does not make something up: it hands the question to a person.
• The channel's rules are Meta's. Once a tenant has gone more than a day without writing, the building can only open the conversation with an approved template. The detail is in the 24-hour window.

Tenant portal or WhatsApp, task by task

Nine things that happen in any rental building, and how each one goes by each route. The WhatsApp column takes for granted an assistant and a team that receives its share, not a phone ringing on a desk.

When the portal wins outright

• When tenants pay through it. Rent, utilities and returned debits: anything with an amount needs the portal or a direct debit, not a chat.
• When documents have to be shown. Agreement, invoices, proofs of payment and certificates have to sit in one fixed place, with identified access and a download.
• When there is a signature. Renewals, annexes and changes of tenant call for a process with identity checked.
• When the accounts team works in that software. If payments are reconciled there, the tenant has to see the same figure that accounting sees.
• When you run many buildings from a head office. Seeing every scheme together, with its agreements and its occupancy, is a job for the management software and its portal.
• When your tenants already report repairs through it. If faults really do come in through the form and get closed properly, there is nothing to fix there.

When WhatsApp is enough and when you need both

WhatsApp alone can work in a small building where rent goes by direct debit, the agreement was handed over on paper or by email and nobody asks for invoices. That is rare in build to rent and somewhat more common in a coliving with a handful of rooms.

In every other case, the split is the portal for whatever carries an amount or a signature, and WhatsApp for whatever carries urgency or a question. For it to work, the team needs to agree on three things:

• One way in per task. If repairs go through WhatsApp, the portal's form is removed or redirected. Two ways in mean two lists, and the second always falls behind.
• The assistant knows where each job lives. When someone asks on WhatsApp how to download an invoice, the reply is the path inside the portal, written in among the building's rules like any other fact.
• Payment details never leave the portal. Nobody in the team sends an account number or a payment link through the chat, not even "just this once".

If your question is not about a web portal but about an application residents download, with bookings, access and community, that comparison is in residence app or WhatsApp. And if what you are unsure about is which kind of WhatsApp account an assistant needs, in WhatsApp Business or API.

Where Bedel fits, and what it does not do

Bedel is the third column of the table. It is an AI assistant that looks after the WhatsApp of a build-to-rent or flex living building, a coliving or a student residence. It is not a tenant portal and does not replace one. What it does today in a rental building:

• It answers questions from the rules and documents the building has uploaded, at any hour and in the language people write in. What is not written it does not improvise: it hands it to a person with the conversation in front of them.
• It turns every fault report, whether it arrives as text, a photo or a voice note, into a ticket with a category, an urgency and a deadline, and sends it to the WhatsApp of the post covering that hour. That post can be the technician of an outside contractor, who accepts it, reassigns it and closes it with buttons.
• It tells the tenant where their ticket stands when they ask, without the office having to look it up.
• It notifies each parcel the office logs, and when someone asks it speaks only about theirs.
• It books the shared spaces the operator opens, in slots, each with its capacity and its weekly cap.
• It sends the building's notices to everyone, to a list of flats or to particular people, by template to anyone who has gone more than a day without writing.

What it does not do, which matches what the table leaves to the portal. It does not collect rent or receipts, and no payment link goes out through the chat. It does not sign agreements or store them, and it does not store invoices or any other tenant documents either. It does not handle deposits. It does not market flats: it does not bring in tenants, screen them or schedule viewings. It does not take calls or make them; voice notes that reach the chat are transcribed with the AI model it ships with. It does not connect to the rental management software or to any other system: the tenant list comes in as a spreadsheet, and what comes out is a spreadsheet export. It has no view that brings several buildings together, because one account is one building. It does not control access or keys. And it does not translate notices or tell you who has read them.

The detail of what it does in a rental building, including how Spanish tenancy law splits repairs, is in software for build to rent. And what an AI settles on its own and what it leaves to a person, in AI for student residences.