The Needs Attention widget surfaces system events your team should know about, so problems that used to happen quietly now show up where you'll see them. You'll find it on your dashboard, and there's a bell in the header that shows a count when something needs a look.
Today it focuses on automations — the most common place where something can silently not happen the way you expected.
A failed automation run. If an automation errors out while running, you get a notice naming the automation and what went wrong.
A skipped action. If an automation couldn't do something because a prerequisite was missing — for example, it tried to text a guest who has no phone number on file — you get a notice naming the automation, the guest (or guests), and the reason. Previously this happened silently, so you'd have no idea a message never went out.
A failed message delivery. Sometimes an automated text reports success when it sends, but the carrier later reports it didn't actually deliver. That late failure now surfaces as a notice too, instead of disappearing.
Each notice has two actions:
Resolve — you've handled it (for example, you added the missing phone number and re-ran the automation, or followed up with the guest manually). Resolving clears it from the widget. If the same issue happens again later, a fresh notice appears.
Silence — you've seen it and don't need it in the list, but you don't want to mark it handled. Silencing is reversible — you can bring silenced notices back later.
Click through any notice to jump straight to the exact automation run that caused it, so you can see the full context.
The widget updates live — new notices appear and resolved ones disappear without needing a refresh, including across your team.
"No phone number" skips. The guest doesn't have a mobile number on file in your PMS. Add one and re-run, or reach the guest another way. To prevent these going forward, add a Guest Profile → Has Phone condition before the Send SMS action so the automation branches cleanly instead of skipping. See Using Conditions.
Delivery failures. These are usually carrier-side (a landline, a disconnected number, or a number that can't receive SMS). Check the guest's number and follow up by phone if it's important.
Automation run errors. Open the linked run to see the error. If it's not obvious, reach out to support.
Check the bell at the start of a shift. A quick glance tells you whether any guest messages quietly didn't go out overnight.
Resolve, don't just silence, when you've actually fixed something. Silencing hides the notice but leaves the underlying issue marked as unhandled — resolve is the one that means "done."
Reach out via the chat widget in your Hello Hotel app, or email [email protected].
