The WhatsApp of your holiday lets, your aparthotel, your guests, your tenants, answered.

A Friday in August, 22:40. The building has thirty-eight apartments occupied and the office closed at eight. A family who has just arrived asks about the wifi in French, 304 sends a photo of the air conditioning that will not cool, someone wants to know whether they can leave their bags after Sunday's check-out, and a tenant who has been there four months asks whether a parcel has arrived for her. The air-conditioning technician works for an outside firm, and housekeeping comes in on Saturday between one check-out and the next check-in. Bedel answers that WhatsApp: what is in your manual it says in the language of whoever writes, the repair it puts with its deadline on the technician's phone, and what a machine should not decide it does not decide.

What it is and what it is not. Bedel is support and communication software for the day-to-day running of a building of holiday apartments, an aparthotel or a block of mid-stay lets. It is not a PMS or a channel manager: it does not handle bookings, prices or payments, it does not do the guest register and it opens no doors. It lives alongside the system you already use and handles what comes in through WhatsApp for as long as each stay lasts.

What the guest writes: "What's the wifi password?" at 23:10, an hour after arriving

What Bedel does: Answers in English with what your manual says. If the reply was about to go out in Spanish, it is translated before sending, without touching times, links or names

What the guest writes: A photo of the air conditioning in 304, with "it's not cooling at all"

What Bedel does: Opens a maintenance ticket with category, urgency and deadline and puts it on the technician's WhatsApp, even if they work for an outside firm. The guest is notified when it is accepted and when it is fixed

What the guest writes: "Can I leave my bags after 11?"

What Bedel does: Answers with what the manual says about check-out. If the manual says nothing, it does not invent a yes

What the guest writes: "The people upstairs are playing music at two in the morning"

What Bedel does: Opens it as a neighbourly-conduct incident, with its time, and puts it on the phone of the post that keeps order according to your org chart. Bedel does not write to the apartment upstairs

What the guest writes: "There's a smell of gas in the kitchen"

What Bedel does: The model does not decide it: a fixed rule treats it as an emergency, alerts the emergency posts at that moment and tells the guest to call 112. It only says the team has been alerted if the alert has reached someone

What the guest writes: "No need to come and clean this week" (a tenant who is on your list)

What Bedel does: Logs every day of that week; housekeeping sees it in their notice and with /limpieza from their WhatsApp, with the apartment number

What the guest writes: "Has anything arrived for me?" (a mid-stay tenant)

What Bedel does: Tells them only what is under their name. When the team logs a parcel, the notice reaches them even if they have not written for days

What the guest writes: "I want to talk to someone" (a guest who is not on your list)

What Bedel does: Bedel answers and refers them to the phone number or email in your manual: it does not alert the team about someone who is not registered, except in an emergency. If they are on the list, the alert goes to a person's phone

In a building of apartments two kinds of people write in, and it is worth knowing before you start how Bedel treats each one. The mid-stay tenant is usually on your list, with their phone number and their apartment. The three-night guest often is not: your PMS has them, and Bedel does not read the PMS.

• Someone who is not on the list still gets an answer, from your manual and in their language, and if they report a fault the ticket opens with their phone number: they are notified when it is accepted and when it is fixed.
• What they do not get is a handover to a person. If they ask to talk to someone, Bedel answers and refers them to the phone number or email you put in the manual. An emergency does get through: gas, fire or someone who is not breathing alert the team at that moment.
• The full treatment (asking for a person, sending a request to housekeeping, asking about their parcels, knowing where their ticket stands) is for whoever is in the directory. There are three ways in: with the list in Excel or CSV, with a one-time registration code the guest sends on WhatsApp, or by confirming from the dashboard the record Bedel proposes when someone introduces themselves by name.
• The list is read even if the columns have different names. Anyone without a phone number is not registered, because Bedel talks to them on WhatsApp; if the list has check-in and check-out dates, they are saved with the record.

In a four-night stay, an air conditioner that stops cooling on Friday and is fixed on Monday is the whole stay. Bedel turns each report into a ticket with category, urgency, owner and deadline, and puts it on the WhatsApp of whoever fixes it: someone on the team or the outside firm's technician, if that is how you have set up your org chart.

• The guest reports with text, a photo or a voice note. A photo on its own already opens the ticket, and any photos sent in the next fifteen minutes are added to the same one.
• Whoever receives it accepts it for today or for tomorrow, asks for more information or reassigns it with buttons, and closes it with a photo. The guest hears about every step without anyone from the office writing to them.
• A reminder to whoever owns it at 50 % and at 85 % of the deadline; an urgent one that runs out rings again once a day and, after three days, goes up to management.
• If the same apartment has the same fault again within twelve months, the technician sees it flagged as repeated in their notice; the guest does not. With the air conditioning or the washing machine, that is the conversation still to be had with the supplier. For this to work the apartment has to be written in figures, like "304".

Housekeeping in a holiday apartment is not a daily round: it is the gap between the morning check-out and the afternoon check-in, and an outside firm often does it. Bedel does not keep that schedule, which lives in your system. What it does is put on housekeeping's phone whatever is asked for on WhatsApp.

• A tenant who is on your list writes "no need to come this week", "I've spilt wine on the sofa, can you come?" or "come as late as you can", and housekeeping gets the notice with the apartment and the day.
• Housekeeping sees the day's list with /limpieza from their own WhatsApp: which apartments are not to be cleaned, which are urgent and which are for later.
• The team can also ask for it on behalf of an apartment ("don't clean 305 today"), and it works for apartments set up in the dashboard even if nobody is living in them right now.

A building with holiday apartments often shares its walls with neighbours who are not guests, and a noise complaint reaches the residents' association before it reaches the office. Bedel answers the rules with what you have written and logs the nuisance as what it is: a report with its time and someone in charge of it.

• Quiet hours, rubbish, pets, visitors, smoking on the balcony: it answers with your rules and with the answers the team has approved. What is not written down, it does not make up.
• "The people upstairs are playing music at two in the morning" opens as a neighbourly-conduct incident and goes to the post that keeps order according to your org chart. The time is on record, for when the residents' association asks.
• Every night, Bedel leaves as drafts the questions people have asked and the manual does not answer; the team approves them in the dashboard, and from then on everyone gets the same answer.
• Notices to the whole building (the water cut, the works in the entrance hall) go out from the dashboard or with /difundir from the team's WhatsApp, to whoever is on your list: Bedel shows how many people it will reach and asks for confirmation with "SÍ" before sending.

What separates a holiday apartment from a mid-stay one is no longer just the use: since 8 October 2026 it is also the contract. Letting a furnished apartment that is marketed through tourist channels and subject to tourism regulation falls outside the Urban Leases Act, and its maximum length, set by each administration, cannot exceed thirty-one days (art. 5.e, as worded by Royal Decree-law 29/2026). Above that, someone who is away from home for a justified cause signs a temporary residential lease (art. 2.3): more than thirty-one days and, as a general rule, no more than twelve months (art. 9 bis). Without that cause written into the contract, it is a habitual-housing lease (art. 7.2).

• To Bedel, the difference is the list: the tenant of several months is usually registered, and with that they get their parcels, their housekeeping requests and a person when they ask for one.
• "Has anything arrived for me?": it tells them only what is under their name, and when the team logs a parcel the notice reaches them even if they have not written for days. More in parcels.
• Questions about the deposit, a change of dates or leaving early are not answered by a machine: they go to a person on the team.
• The legal detail, with the article: residential lease or lease for other use and the guide to coliving rules, which explains the change of 8 October.

A building of apartments sees, in a year, many phone numbers that never write again. What does not go through Bedel is the guest register: if your activity is a lodging one, Royal Decree 933/2021 requires you to keep the documentary register and to report the details of each arrival, and that stays in your system.

• Conversations are not kept forever: they expire after the period the building decides (twenty-four months unless it decides otherwise) and are deleted in full, not anonymised.
• Someone on your list can be erased from the dashboard when they leave: conversations, housekeeping requests, parcels and presence disappear, the repairs they reported stay without their name, and a record of the request is kept.
• The notice that they are talking to an AI assistant, and that by writing PRIVACIDAD they can see how their data is handled, reaches them in their language.
• The database and the functions live 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 a PMS or a channel manager: it does not handle bookings, availability, prices or the check-in and check-out calendar, and it does not read yours.
• It charges nothing to anyone: no stays, no deposits, no extras.
• It does not do the documentary guest register or report its data, and it does not manage the tourist licence or registration number of each apartment.
• It opens no doors: keys, connected locks and access codes stay in their own system.
• A guest who is not on your list gets answers and their repair opened, but is not passed to a person when they ask, except in an emergency.
• One account, one building: there is no screen that brings together several buildings of the same operator.

• 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