Skip to content

Alerts ​

Insight › Monitoring › Alerts lists everything on your site that needs attention, from every check Kiwire runs. The checks run every 30 minutes for every site, whether or not KAIA is switched on, and they use no AI.

What gets checked ​

AreaWhat raises an alert
Guest messagesWhatsApp, SMS or email codes and links failing to send — for example the WhatsApp provider refusing every message. Guests on that login method cannot sign in.
Guest accessGuests turned away before the portal: licence expired or at its login limit, device limit reached, no page assigned to the journey, a deleted page, the controller not sending its NAS id or the device MAC. Login failures far above normal, or no logins at a time there normally are.
NetworkA controller that has stopped carrying sessions; unusual disconnect reasons; one account moving far more data than usual.
ConfigurationA zone with no login journey, no rule that sends logins into it, or a forced profile that no longer exists.
IntegrationsPMS check-ins and room moves that could not be applied (usually a room with no Wi-Fi account), PMS gone quiet, CRM syncs failing, paid Wi-Fi checkouts failing.
Licence & certificatesLicence expiring or over its limits; certificates expiring.
System tasksScheduled tasks (resets, clean-up, scheduled reports) failing; reports no longer updating.
VouchersVoucher stock running out at the current rate of use.
EngagementCampaigns past their end date or shown to no one.

Each alert says what is wrong, how big it is ("52 of 52 WhatsApp sends failed in the last 3 h"), the provider's own error where there is one, and what to check. Click an alert to see the details.

Severity ​

  • Critical — guests are affected now (nobody can sign in with a method, guests are being turned away, a licence has run out).
  • Warning — something is wrong or about to be (a controller gone quiet, logins failing more than usual, stock running low).
  • Info — worth knowing, nothing to do urgently. Info alerts are listed but never notified.

Notifications ​

When an alert opens, an open alert gets worse (for example from Warning to Critical), or a snoozed alert comes back because the problem is still there, every admin of the site gets a notification on the bell, linking to the Alerts page. You are told once per alert: it is not repeated while the alert stays open — not even the next day — and an alert that clears and comes straight back within a day is not announced again. An alert that becomes less serious is updated on the Alerts page without a notification.

Handling an alert ​

  • Acknowledge — you are on it. The alert stays listed under Acknowledged / snoozed; if it gets worse it reopens and notifies again.
  • Snooze — hide it for 4 hours, 1, 3 or 7 days. When the snooze ends and the problem is still there, it reopens and notifies again.
  • Alerts close by themselves once the check no longer finds the problem; closed alerts stay visible under Resolved for 7 days.

Several at once: tick the alerts (or Select all for the tab you are on) and use Acknowledge, Snooze, Ignore or Reopen from the bar above the list.

Ignore is for something you have decided not to fix — a test zone, a campaign you keep on purpose. The alert stays listed under Ignored, never notifies and never reopens, until someone reopens it. There is no delete: an alert whose problem is still there would simply be raised again by the next check.

Check now runs every check for your site immediately instead of waiting for the next half hour.

Settings ​

Settings on the Alerts page lets you switch bell notifications off for the site, and switch individual checks off — a site that does not use campaigns or vouchers can turn those checks off so they never raise anything.

Who can see and change alerts ​

The Alerts page needs the Monitoring › Alerts → View permission; acknowledging, snoozing, Check now and the settings need Manage. Both are given to the Admin and Manager roles (Viewer gets View) and can be changed under System › Roles. Acknowledging, snoozing and settings changes are recorded in the audit trail.

KAIA and alerts ​

KAIA uses the same checks and the same list. With KAIA switched on, it also explains alerts in plain language and suggests improvements; without it, the alerts still run and still notify.

Last updated:

Kiwire platform documentation