The WhatsApp of your clinic, your practice, your surgery, your medical centre, answered.

Thursday, 8:05. The healthcare assistant opens up sterilisation and the autoclave won't heat; the first appointments are at nine. Until now, she goes looking for the practice manager, who is with someone, leaves a note and rings an engineer who doesn't pick up. With Bedel she writes "the sterilisation autoclave isn't heating up" to the clinic's WhatsApp, with a photo of the display. The alert lands on the maintenance phone with buttons; if the deadline passes, it goes up to management. The whole report holds a place and a fault. No patient.

What it is and what it isn't. Bedel handles the faults of a clinic, a practice or a private health centre, from the report to the close. It isn't practice management software: it doesn't keep the diary, appointments, clinical records or billing, and no patient or health data should pass through it. The ticket holds the place and the fault, never a person. Reports are opened by the team, who are on the list; patients don't write to Bedel.

Message from the team: "The sterilisation autoclave isn't heating up", with a photo of the display

What Bedel does with it: Logs it as a fault ticket and puts it on the phone of maintenance or the outside engineer, with buttons and the deadline for its category. Whoever reported it hears back once it's accepted and again once it's resolved

Message from the team: A stain on the waiting room ceiling, as a photo with no text

What Bedel does with it: The photo is enough to open the ticket; if the location is missing, it asks. What counts as urgent and who gets it at night is settled in the setup session

Message from the team: A voice note: "the couch in room 3 won't go up"

What Bedel does with it: Turns it into text and opens the ticket with the place and the fault. Nothing else goes in: not who was on the couch, not why

Message from the team: "What time is the closing round?"

What Bedel does with it: Answers from the clinic's rules document. Whatever isn't written down passes to a person

Message from the team: "There's water on the floor of the waiting room toilet"

What Bedel does with it: Sends it as a one-off cleaning job to the phone of the cleaning role, without going through management

Message from the team: A patient's name, typed by mistake

What Bedel does with it: That isn't what Bedel is built for and it doesn't promise to catch it: the rule against writing one is put in writing on day one

In a small or mid-sized clinic, maintenance is rarely a department: one person some of the time, an outside engineer and a practice manager who is always somewhere else.

• The healthcare assistant tells reception, reception tells management, and management rings the engineer once they're out of clinic.
• In the WhatsApp group, "the air con's broken" ends up buried under twenty messages about the rota.

Everything that goes wrong on any premises, plus equipment that can't wait until Monday.

• Sterilisation: the autoclave, the heat sealer, the ultrasonic bath. These go to the manufacturer's service engineer or to maintenance.
• Air conditioning and water: the air con in the waiting room, a leak, the water heater.
• Waiting room and toilets: the bulb, the tap, the wet floor. One-off jobs go to the cleaning role.

The report doesn't go to a group: it reaches the phone of the right person, according to the structure you set up for the clinic.

• The outside engineer joins as one more role, with their own WhatsApp: they accept, ask for details, reassign or close with a photo.
• Each category has its deadline, with reminders while it runs. When it expires, the report goes up once to management; urgent ones ring again every day until they're closed.
• At night and at weekends, whatever you mark as urgent rings for whoever you leave on call; the blown bulb waits for the shift.

This isn't legal advice: it's what we've read in Spain's official gazette (BOE) and in EUR-Lex, for your adviser to check. None of these rules requires a fault log on WhatsApp. What applies to your premises depends on the country; your adviser confirms it.

• The EU's GDPR defines health data (art. 4.15) and prohibits processing it outside the cases in art. 9.2. That's why the ticket doesn't carry it.
• In Spain, Law 41/2002 on patient autonomy and clinical documentation protects the confidentiality of health data (art. 7.1) and has each centre keep its own patients' clinical records (art. 14.2). The record stays in your clinical software.
• On occupational risk prevention in Spain, workers report any risk immediately (Law 31/1995, art. 29.2.4), work equipment is maintained following the manufacturer's instructions (Royal Decree 1215/1997, art. 3.5) and workplaces are looked after periodically (Royal Decree 486/1997, annex II, section 4). The ticket times leave a record; whether they're enough is for your prevention service to decide.

Nothing gets installed. In one session the clinic's WhatsApp is up and running with the following.

• Who handles what: maintenance, the autoclave engineer, air conditioning, cleaning and on call.
• The categories, their deadlines and which ones are urgent, in your own words: "sterilisation", "waiting room".
• The written rule for the whole team: a report holds the place and the fault, never a patient's name or condition.

• It isn't practice management software: no diary, appointments, records, prescriptions or billing, and no connection to the system you already use.
• No patient or health data needs to pass through it, and it doesn't promise to detect or filter one typed by mistake.
• Patients don't write to Bedel: the people on the list report, which means the team.
• It isn't the channel for a medical emergency: for that you call 112 and follow the centre's protocol.
• It doesn't keep the records or checks that regulations may require for each piece of equipment.
• Each account is one clinic: if you have more than one, you see each separately.

• Incident management on WhatsApp
• Restaurants
• Hotels
• Gyms
• Sports centres
• Offices
• Coworkings
• Shops
• Franchises
• Blocks of flats
• Schools
• Academies and training centres
• Warehouses and plants