The WhatsApp of your student housing, your PBSA, your front desk, your residents, answered.

A Sunday in September, nine at night. Two residents who arrived that day ask for the wifi in English, another sends a photo of a loose socket, and a mother wants to know whether her daughter has arrived. There is one person on reception, and thirty more residents move in tomorrow at eight. Bedel is the layer that answers that WhatsApp: it settles what repeats, opens a ticket for what is broken and puts on the phone of whoever is on shift the things a machine should not decide.

What it is and what it is not. Bedel is support and communication software for the day-to-day of a residence. It is not your property management system: it does not allocate rooms, bill fees or control access. It lives alongside the PMS you already have and the room-rack spreadsheet, which it reads and returns up to date.

What the resident writes: "What's the wifi password?" at 23:40

What Bedel does: Answers in English from the building's handbook, without waking anyone. It answers in the language of the last message; if a reply was about to go out in Spanish to someone who does not write in Spanish, it translates it first

What the resident writes: A photo of a loose socket, no text

What Bedel does: Opens a maintenance ticket, classifies it by category and urgency and notifies the maintenance post on shift. If urgent, the whole post

What the resident writes: "I'm leaving Thursday and back on Sunday"

What Bedel does: Goes into the absence log, one row per night; the front desk knows and, if there is a dining hall, the kitchen stops counting those meals

What the resident writes: "Has my parcel arrived?"

What Bedel does: Tells them only about their own. When reception logs a parcel, the resident gets the notice even if their 24-hour window is closed

What the resident writes: "I want the study room on Tuesday from 4 to 6"

What Bedel does: Books in closed slots, with capacity and a weekly cap per person; if it is full or out of hours, it says why

What the resident writes: "I'm Marta's father, is she all right?"

What Bedel does: Does not give the information. Asks Marta to authorise it with a button; with no answer in 48 hours, the team decides from the dashboard

What the resident writes: "My bike was stolen from the garage"

What Bedel does: An AI does not resolve this: it notifies the right post according to the org chart and leaves the resident in a person's hands

The difference between a residence that works and one that switches off at eight in the evening is who receives each notice. Bedel sends nothing to a group: it uses the org chart and shifts the centre configures, and every notice lands on one specific phone.

• Urgent matters go to the whole post; everything else, to the first person in that shift's rotation.
• If nobody is on shift, the ticket passes to the post that covers that time; at night and at weekends, what can wait is held and delivered when the next shift opens.
• Low priority does not interrupt anyone: it goes into a morning digest.
• Absences and delegations are declared in the dashboard, so a shift with nobody behind it is visible before a notice fails.

A maintenance ticket is born from the resident's message (text, photo or voice note) and ends when the technician closes it with a photo from their own WhatsApp. In between, the deadline is set by the category the centre has configured.

• A reminder to whoever owns it at 50 % and 85 % of the deadline; an urgent ticket past its deadline sounds again once a day and after three days goes up to management.
• On Monday mornings, anyone with tickets for their post left untaken for more than two days gets two lines to go and see them.
• If the same room repeats the same fault within twelve months, the technician sees "repeated" in their notice; the resident does not.
• The resident knows when it is accepted, when it is resolved and if it is reopened, and the centre exports the tickets spreadsheet with the columns of its own log.

The day-grid spreadsheet you already keep, the room rack, is the input. Bedel reads it, works out from when each person is in, until when, and which nights they are away, and returns it up to date. It registers nobody: it matches by name against people who already exist.

• Live presence worked out from last night, tonight and today's movements, without reception having to tick returns.
• An evacuation plan in a spreadsheet with who is inside right now.
• Whoever is due back today according to the absence log is asked in the morning "Arriving today?" with two buttons; if not, the front desk knows and, if there is a dining hall, so does the kitchen.
• More detail in arrivals and room rack.

In a residence with international students, language is not a detail: it is half the messages. Bedel answers in the language of the last message and protects what must not be translated: times, links, proper names.

• If a reply was about to go out in Spanish to someone who does not write in Spanish, it is translated before sending; if the translation fails, the original goes out rather than nothing.
• Voice notes are transcribed with the default model.
• The centre's announcements go out exactly as the team writes them: Bedel does not translate them, and we say so, so that nobody counts on it.

An operator signs with many suppliers and few show them the paperwork first. Here it is published: the data processing agreement, the record of processing activities and where the data lives, on the GDPR page.

• Database and functions in the European Union (Ireland); the AI model runs in the United States under the Standard Contractual Clauses.
• The right to erasure is executed from the dashboard: it deletes conversations, dining, allergens, parcels, presence and family, anonymises incidents and leaves a record of the request.
• A confidential, encrypted channel for what is not said in the group; if the operator reaches fifty employees, Spanish Act 2/2023 requires one.

• It is not a PMS: it does not allocate rooms, manage contracts or bill. It reads and returns your room rack, nothing more.
• It has no group view: one account is one building. An operator with several residences has one account per residence.
• It does not control physical access: no QR codes, turnstiles or locks. Presence is worked out from what people say and from the rack.
• It does not translate the messages the team writes to a resident through the direct chat, nor the announcements.
• It does not count people who do not say anything: if nobody says they are skipping dinner, the kitchen counts them in.

• 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