For any UK business with premises: restaurants, hotels, gyms, offices, shops

Every fault on the premises, with its time and its owner, not lost in the staff group

Friday, 19:40, a full restaurant. A waiter notices the ice machine has stopped and posts it in the staff group, between the rota and a photo of tomorrow's order. The manager reads it at nine and nobody knows when it started. With Bedel, the waiter writes to the premises' WhatsApp instead: the notice rings on the phone of whoever fixes it, and three times are kept: reported, taken and fixed.

Published on 25 October 2026

What someone on the premises writes, and what happens to it

The staff message	What Bedel does
"The walk-in fridge is at 9 degrees"	It opens a repair ticket with the urgency you gave to cold rooms and sends it to maintenance's phone, with buttons to take it
A photo of a dripping tap, without a word	The photo alone opens the ticket. It asks where, if that is missing, and assigns it to whoever handles that category
"Rowing machine 3 is broken", at 22:10	If it is not urgent, it waits for the shift of whoever fixes it. If you marked it urgent, it rings on the on-call phone
"There's smoke coming from the fuse board"	It waits for no deadline: it alerts the team at once and tells whoever wrote to get out and call 112 if needed
A ticket open for two days	When the deadline ran out it went up once to the person above. If it is urgent, it rings again every day until it is closed

Which businesses it is for

Any business with premises, a team that sees the faults and someone who fixes them: restaurants (the cold room that stops cooling), hotels (the air conditioning a guest finds broken), gyms and leisure centres (the treadmill with an out-of-order sign), offices and coworking spaces (the meeting room that will not open), shops and franchises (the shutter and the till), schools, clinics and warehouses. The words and the deadlines change; the route does not.

How a notice travels

Bedel does not write to groups: each notice goes to one person's phone, by the org chart and the shifts you set.
Whoever fixes it gets buttons to accept it today or tomorrow, ask for more information or reassign it, and every tap keeps its time.
Each category has its deadline, with a reminder halfway and another near the end. If it runs out, the ticket goes up once to the person above, without being taken from anyone.
An overdue urgent ticket rings again every day until it is closed; what is not urgent goes into a weekly notice.
Whoever reported it is told when it is accepted and when it is fixed. Each night there were tickets, a summary reaches your email, and the dashboard shows times and overdue tickets over 7, 30 and 90 days.

What UK rules say, and what they do not

No rule requires you to use Bedel. These are the rules where a dated record of faults is relevant, cited with the article for your adviser, who confirms what applies to you:

Workplace (Health, Safety and Welfare) Regulations 1992, reg. 5 (England, Wales and Scotland): the workplace and certain equipment, devices and systems must be maintained in an efficient state, in efficient working order and in good repair, and where appropriate be subject to a suitable system of maintenance.
Regulatory Reform (Fire Safety) Order 2005, art. 17 (England and Wales): the responsible person must ensure the premises and their fire safety facilities, equipment and devices are subject to a suitable system of maintenance.
UK GDPR, Art. 28: your business is the controller and Bedel the processor, with the processing agreement published. Data from the UK to the EEA is treated as approved by regulations (Data Protection Act 2018, Sch. 21).

Worth knowing

A ticket is a record, not a maintenance system. It shows who reported what and when it was fixed. It does not replace a fire risk assessment, the inspections each installation needs or the advice of whoever is responsible for health and safety.

How it starts

A half-hour session between whoever runs the premises and whoever runs maintenance. Nothing to install, no inventory to load.
Who handles what, the categories with their deadline, what is urgent at 2:00 and who is on call.
The number: the one the team already has, or a new one connected to Meta's official platform.

What it does not do, said before the call

It is not a CMMS or an ERP: no asset inventory, purchasing or invoices.
It does not bring a group's sites into one view: each account is one site, with its own spreadsheet and the same columns in all of them.
It does not connect to other tools: not to your maintenance software, your till or your PMS.
Your team's side is in Spanish today: the notices, the buttons and the commands.
Customers do not report on their own: whoever is on the list does. It takes no payments or bookings, and asks for no personal data in the chat.

Questions

Do you already work with businesses in the UK?

Not yet. The places that use Bedel today are in Spain. What changes for a UK business, from the contract to the data transfer, is agreed before signing.

Does anyone need to install an app?

No. Whoever reports writes to the premises' WhatsApp. Whoever fixes it receives the notice on their own WhatsApp, with buttons.

In what language does the team receive the notices?

In Spanish, today: the notices, the buttons and the commands are written in Spanish. Say so on the call if your team needs them in English.

What happens with a fault at 2:00?

It depends on the urgency you set. What is urgent rings on the phone of whoever you leave on call; what can wait arrives when their shift starts. Gas, smoke, fire or an injury always alert the team at once.

Does it work if I have several sites?

Each site has its own account, number and spreadsheet. There is no combined view with the times of all of them: you compare them by opening each spreadsheet.

Bedel in Europe