The WhatsApp of your coliving, your flex living, your house, your community, answered.

A coliving with eighty units has residents from fifteen countries, a team of two and a maintenance contractor who comes when called. On Monday at eight there are nine messages: three in English, one in Portuguese, a photo of a washing machine that will not spin, and a booking of the coworking room for a video call at nine. Bedel answers each one in its language, opens the washing-machine ticket with its deadline and puts on the community manager's phone only what a machine should not decide.

What it is and what it is not. Bedel is support and communication software for the daily operation of a coliving. It is not the contracts or payments system, it does not manage occupancy and it does not control access. It lives alongside what you already have and reads your room rack spreadsheet to know who is in.

What the resident writes: "How do I book the coworking room?" at 8:05

What Bedel does: Answers in English and books in closed slots: time bands, capacity, notice period and weekly cap are set by the operator. If it is full, it says why

What the resident writes: A photo of a washing machine that will not spin

What Bedel does: Opens a maintenance ticket, classifies it and notifies the maintenance post on shift with the photo; reminds of the deadline at 50 % and 85 %

What the resident writes: "Há encomenda para mim?"

What Bedel does: Replies in Portuguese with what is under their name and nothing of anyone else's. The notice that something has arrived reaches them as soon as the team logs it, even if they have not written for days

What the resident writes: "I'm off to Lisbon for two weeks"

What Bedel does: Logs the fourteen nights away; the team knows who is sleeping in the house without asking in the group

What the resident writes: "Can I have guests to stay?"

What Bedel does: Answers from the house rules the operator has written; what is not written, it passes to a person

What the resident writes: "I want to report something I won't say in the group"

What Bedel does: The building's own link, anonymous by default, the account encrypted and read only from the dashboard with logging

What the resident writes: The team: "/difundir: water off tomorrow from 9 to 11"

What Bedel does: Shows the real number of recipients, requires confirming with "SÍ" and sends by template to anyone whose window is closed

In a house of stays measured in months, the mix of languages changes with every move-in, and the team cannot hire one language per resident. Each person writes in theirs and gets the reply in that same language, with times, links and names left intact.

• When a reply comes out in Spanish for someone who writes in another language, a second pass puts it into theirs; if that pass fails, it is sent as it is rather than leaving them unanswered.
• Anyone who would rather talk than type sends a voice note: it is turned into text before the reply.
• What the team writes (the water-cut notice, the direct message to 3B) goes out in the language it was written in. If the house needs English, the team writes it in English.

The problem of a coliving is not that there are repairs: it is that one person handles them along with everything else. Bedel turns each notice into a ticket with category, urgency, owner and deadline, and chases the deadline for them.

• The resident reports with text, a photo or a voice note; a photo on its own already opens the ticket, and photos arriving in the next fifteen minutes attach to the same one.
• Whoever owns it accepts, resolves or reopens it with buttons from their WhatsApp and closes with a photo; the resident knows at every step.
• The washing machine that fails for the third time in a year reaches the technician flagged as repeated: that is the conversation to have with the supplier.
• The tickets spreadsheet comes out with the columns of the operator's own log. What it does not record: the external contractor or the technician's hours.

What makes a coliving a coliving are the shared spaces and life in common, and both are badly managed through a group. Bedel books in slots and communicates without a group.

• Any space the operator configures (coworking, shared kitchen, terrace, cinema room) with its time bands, capacity, slot length and weekly cap per person; capacity and overlaps are checked in a single operation, so there are no double bookings.
• Announcements go out from the dashboard or with /difundir from the team's WhatsApp, to everyone, to a range of units or to specific people, with an image poster if needed.
• The same text to the same audience within ten minutes is not sent twice.
• House events are convened with confirmation and a reminder; more in events and activities.

Flex living lives on turnover, and turnover is what breaks spreadsheets. Bedel reads the room rack you already use and works out who is in, until when and which nights they are away.

• Who is sleeping in the house tonight comes from what people have said and from the rack, with no roll call; if the alarm goes off, the evacuation plan carries that list.
• On the day someone is due back, Bedel asks them in the morning with two buttons.
• Move-ins, move-outs and contracts stay in your system: the rack gives the name and the dates, and each row is matched with a resident who is already registered.

There is no coliving act in Spain: there is a contractual fit within the Urban Leases Act and a planning regulation that differs in each region. We have written it with the article and the gazette in the coliving regulation guide and, region by region, in coliving regulation by region.

• 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.
• When someone leaves the house, the operator can erase their data from the dashboard: conversations, parcels and presence go, and the repairs they opened stay without their name.
• The confidential channel is there from day one. The duty to have one comes with Spanish Act 2/2023 from fifty employees, adding up all the operator's houses.

• It is not the contracts, payments or occupancy system: it does not sign, bill or allocate units.
• One account, one house: there is no screen that brings together several buildings of the same operator.
• Doors, keys and connected locks stay in their own system: Bedel opens nothing.
• It does not translate announcements or the team's messages through the direct chat.
• Bookings have no team approval, reminders, waiting list or payment.

• 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