The WhatsApp of your build-to-rent, your rental building, your tenants, answered.

Thursday, 19:40. In a building with two hundred rental homes, the office has already closed. From the sixth floor comes a photo of a damp patch on the bathroom ceiling; a tenant asks whether her shopping has arrived; a couple who moved in on Monday cannot find the password for the coworking wifi, and someone wants to know whether they can keep a dog. The maintenance contractor's plumber starts tomorrow at eight. Bedel answers that WhatsApp: it replies with what the building has written down, opens the ticket for the damp patch with its deadline and leaves it on the phone of whoever has to go, and passes to a person what a machine should not decide.

What it is and what it is not. Bedel is support and communication software for the day-to-day running of a residential rental building, from build to rent with tenants who stay for years to flex living with stays of a few months. It is not the lettings management program: it does not sign contracts, collect rent, handle deposits, screen tenants or open doors. It sits behind the building's WhatsApp and puts order into what comes in through it.

What the tenant writes: A photo of a damp patch on the ceiling, at 19:40

What Bedel does: Opens a maintenance ticket with category, urgency and deadline, and notifies the maintenance post covering that hour according to the org chart. The tenant is given the ticket number

What the tenant writes: "Has anything arrived for me?"

What Bedel does: Looks only at what the office has logged under their name in parcels and tells them; it knows nothing about the neighbours' parcels

What the tenant writes: "I'd like the residents' lounge on Saturday afternoon"

What Bedel does: Offers the available slots for that day and books the one they choose. Time bands, capacity, notice period and weekly cap are set by the operator; if it does not fit, it says why

What the tenant writes: "Are dogs allowed in the building?"

What Bedel does: Answers from the house rules the operator has uploaded. If the answer is not written down, it does not improvise: it passes it to the right person with the conversation in front of them

What the tenant writes: "L'interphone du 2C ne marche plus depuis hier" (in French)

What Bedel does: Replies in French, the language it was written in, and opens the ticket exactly as if the message had arrived in Spanish

What the tenant writes: "How's my water heater going?", two days later

What Bedel does: Checks that person's open tickets and tells them where theirs stands, without anyone in the office having to look it up

What the tenant writes: The office: "/difundir Monday 9 to 13 the lift in block 2 is being inspected"

What Bedel does: Shows how many people will receive it, asks for confirmation with "SÍ" and sends it by template to anyone who has not written for more than 24 hours. Whoever has opted out of notices does not receive it

In a rental building the repair is often not done by anyone in-house: the plumber, the lift company and the heating and cooling firm come from outside, and the property manager acts as a switchboard between the tenant and them. Bedel removes that switchboard. Each report becomes a ticket that goes to a post in the org chart, and that post can be the contractor's technician, with their own WhatsApp.

• The tenant reports with text, a photo or a voice note; the ticket is born with its category, its urgency and the deadline the operator has set for that category.
• The technician accepts it for now, for today or for tomorrow, asks the tenant for another photo, writes to them or reassigns it, all with buttons from their WhatsApp and without logging into any program, and closes it with a photo of the fix or a note.
• A reminder to whoever owns it at 50 % and 85 % of the deadline. An urgent ticket that is overdue rings again every day and, after three days, reaches whoever runs the building.
• At night and at weekends, urgent matters go to the whole post covering those hours; what can wait is delivered when the shift opens, and the deadline counts from then.
• If a home numbered with digits (304, 1203) has the same fault again within twelve months, the technician's notice says so. The tenant does not see it.

Each tenant signs a contract under the Spanish Urban Leases Act (LAU), and its Article 21 shares out the repairs: the landlord carries out those needed to keep the home habitable, except for damage caused by the tenant (21.1); the tenant must report that need "as soon as possible" (21.3), and small repairs due to wear from ordinary use are the tenant's (21.4). The consolidated text is in the BOE, in Spanish.

• Since 8 October 2026, according to the consolidated text, there is a new paragraph, 21.5, added by Royal Decree-law 29/2026: for damage affecting habitability, safety or health, the tenant may require the repair in writing with a reasonable quote, and the landlord has fifteen calendar days from receiving it to accept the quote, propose a different repair or carry it out.
• If the landlord does not answer within that period, or refuses without justification, the tenant may carry out the work and deduct its cost from future rent, with the expense documented. Before applying it, it is worth reading the text in force on that day.
• Bedel does not decide whether a WhatsApp message counts as that request, nor does it count the fifteen days: that belongs to whoever advises the operator. What it leaves is the trail of each repair (when it came in, who was notified, how long it took and how it ended) in the dashboard and in the tickets spreadsheet.
• With a landlord that is a legal person, the habitual-residence lease is extended up to seven years if the tenant wishes to stay (Article 9.1). That is many years in the same flat, and having each repair with its home and its date is what shows what keeps coming back.

In a building without a 24-hour concierge, a parcel always brings the same three questions: has it arrived, where is it and how long will you keep it. Bedel's parcel log turns each delivery into a record with its notice.

• The office logs what arrives (a parcel, a letter, a courier delivery or a food delivery) from the dashboard or by writing /paquete and the name or the flat in its WhatsApp.
• The notice goes out straight away; if the tenant has not written for more than a day, by template, so that it is not lost to the 24-hour window.
• Whatever is still waiting to be collected is reminded with a button, one by one or all at once; the all-at-once reminder skips anything notified less than twelve hours ago.
• When they ask, tenants only hear about their own: the assistant does not have anyone else's parcel data.

The shared spaces are a good part of what sets a build-to-rent scheme apart from any other block of flats, and booking them on a sheet on the door or in a group ends in arguments. Building notices (the water cut, the lift inspection, the garage cleaning) have the opposite problem: they are sent, but get lost between email and the noticeboard by the entrance.

• Each space the operator configures (gym, coworking, terrace, laundry, residents' lounge) has its daily time bands, its capacity, the slot length, the days of notice and a weekly cap per person. Capacity and overlaps are checked together, so there are no double bookings, and whoever booked can cancel.
• Notices go out from the dashboard, with an image poster if needed, or with /difundir from the team's WhatsApp: to the whole building, to a list of flats or to people chosen by name.
• The same text to the same audience is not sent twice within ten minutes, and anyone who has opted out of notices does not receive them.
• Notices go out in the language they are written in: Bedel does not translate them. What it does answer in each tenant's language are their questions, with times and links left untouched. More in announcements.

The tenant list comes in with whatever spreadsheet the managing agent already has: Bedel recognises which column is the name, the phone number or the flat even if they are called something else or come in a different order, and shows the list to be checked before saving anything.

• On moving day, the wifi password, the gym's opening hours or how the bin room works are answered from what the building has written down, at any hour.
• The rules (pets, noise, guests, use of the terrace) come from your own documents. What nobody managed to answer is grouped every night into draft answers that the team approves or discards.
• When a tenant leaves, the operator carries out the right to erasure from the dashboard: their conversations and parcels are deleted, and the repairs they opened stay without their name.
• The database lives in Ireland; the AI model runs in the United States under Standard Contractual Clauses, and the data processing agreement is published for you to sign.

• It is not lettings management software: it does not sign contracts, collect rent, handle deposits or produce the record of the home's condition at move-out.
• It does not market homes, screen tenants or manage the building's occupancy.
• One account, one building: there is no view that brings together the schemes of the same operator or the same fund.
• It does not control access: no locks, no door entry system, no keys to the shared spaces.
• It does not track the contract's legal deadlines, including the fifteen days of Article 21.5 of the LAU: each repair's deadline is the one the operator configures per category.
• It does not record the maintenance company as a supplier, nor its hours or invoices: it records which person in the org chart took the ticket, when, and how they closed it.

• Faults and incidents
• Dining hall
• Allergens
• Parcels
• Space booking
• Announcements
• Arrivals and room rack
• Absence log
• Preventive maintenance
• Reporting channel
• Languages
• Escalation to people
• Dashboard and metrics
• Events and activities
• Admissions