For any business with premises in Ireland: hospitality, leisure, offices, retail

Faults on the premises reported on WhatsApp, each with an owner and a deadline

Saturday, 11:05, a hotel at full occupancy. Housekeeping finds the air conditioning dead in a room due to be let at three and sends a photo to the staff group, where it sits under the day's rota. With Bedel, the photo goes to the premises' WhatsApp: it opens a ticket, rings on the phone of whoever handles air conditioning and keeps three times: 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
A photo of an air conditioning unit with an error light	The photo alone opens the repair ticket. It asks where, if that is missing, and assigns it to whoever handles that category
"The keg cooler is warm"	It opens the ticket with the urgency you gave that category and sends it to maintenance's phone, with buttons to take it
"The changing room door won't lock", at 21:50	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
"I can smell gas in the kitchen"	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

Who it suits, and who it does not

It suits a place where the people who notice a fault are not the people who fix it: the bar staff and the cellar, reception and the contractor, the gym floor and the technician who comes on Tuesdays. Pubs, hotels and guesthouses, leisure centres, offices, shops, schools, clinics and warehouses all work the same way. It does not suit a business that needs asset registers, purchase orders or contractor invoicing: that is a CMMS, and Bedel is not one.

From the message to the fix

The notice never lands in a group. It reaches one named person, picked from the roles and shifts you configure.
That person answers with a tap: today, tomorrow, need more detail, or pass it on. Each tap is stamped with the time.
You decide how many hours each kind of fault may take. Bedel nudges the owner twice before the limit; past it, the person above is told once and the owner keeps the job.
Urgent faults left open keep coming back every day; minor ones are gathered into one notice a week.
The staff member who reported it hears when it is taken and when it is done. On nights with activity, a summary goes to your email, and the dashboard keeps response times and overdue counts for 7, 30 and 90 days.

What Irish 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 section for your adviser, who confirms what applies to you:

Safety, Health and Welfare at Work Act 2005, s. 8(2)(c): the employer must ensure, so far as is reasonably practicable, the design, provision and maintenance of the place of work, its access and its plant and machinery in a condition that is safe and without risk to health.
Fire Services Act 1981, s. 18: in premises with sleeping accommodation or open to the public, among others, the person in control must take all reasonable measures to guard against the outbreak of fire.
GDPR, Art. 28: your business is the controller and Bedel the processor, with the processing agreement published.
AI Act, Art. 50: anyone talking to an AI has to know it. Bedel says so from the first message.

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 your safety statement, the inspections each installation needs or the advice of whoever is responsible for safety.

Getting started

One call of about thirty minutes with the manager and whoever looks after maintenance. Between you, you agree the kinds of fault and how long each may take, what counts as urgent after closing and who carries the on-call phone. The staff keep writing to the number they already know, or to a new one on Meta's official platform. There is no app to roll out and no equipment list to type in.

What it does not do, said before the call

No asset register, no purchase orders, no contractor invoices: it is a fault channel, not a CMMS or an ERP.
One account is one site. A group with several premises has an account and a spreadsheet for each, and no combined view.
It does not link to your maintenance software, your till or your hotel system.
Notices, buttons and commands for your staff are in Spanish today.
Guests and customers cannot open a ticket themselves; the staff on your list can. No payments, no bookings, no personal data asked for in the chat.

Questions

Is anyone in Ireland using Bedel already?

No. The places using Bedel today are in Spain. GDPR and the AI Act apply in Ireland exactly as they do there; the contract is agreed before signing.

Where does the data live?

In Ireland, inside the EU. You are the controller and Bedel the processor, under the processing agreement published on the website.

Will my staff read the notices in English?

Not today: the notices, buttons and commands they receive are in Spanish. If that matters for your team, raise it on the call.

Can a guest report a fault directly?

No. Only the people on your list open tickets. What a guest tells reception, someone at reception writes to the number.

What if the fault is a gas smell or smoke?

It does not wait for any deadline: the team is alerted at once, and whoever wrote is told to get out and call 112 if needed.

Bedel in Europe