Set the rule.
Let it find you.
Ping is the Peaqplus alert engine. You define what matters — a threshold, an anomaly, a stagnation — and the platform watches for it on the schedule you set. When it fires, the right person hears about it on the channel that fits their day.
Stop opening five dashboards every morning. The numbers that need a decision come to you — and so does every other cross-module event, on the same unified notification surface.
| Date | Occupancy | vs LY |
|---|---|---|
| Fri, Aug 15 | 82% | +8 pp |
| Sat, Aug 16 | 91% | +12 pp |
| Sun, Aug 17 | 74% | +5 pp |
Suggested action. Review pricing and operational staffing for the weekend — three properties in your compset moved up overnight.
Push, not pull.
Most platforms hand you the data. You then have to remember to open the dashboard, scan it, and notice what changed. Ping inverts the flow: you tell the platform what's worth noticing, the platform watches the data, and you only hear from it when there's something to react to.
The morning routine compresses to one inbox glance. The cognitive load of monitoring drops. Decisions land back where they should — on the days that move the needle, not the days that didn't change.
- Scheduled checks — daily, weekly, or hourly cadences supported
- Per-hotel scope — each rule attached to one property
- Multiple recipients per alert — RM + GM + owner can all be on the same trigger
- Per-alert language — picked from the recipient's account language
- Silent logging on SMTP failure — no trigger is ever lost, even when email isn't delivered
Threshold. Movement. Anomaly. Stagnation.
Every alert is a rule across one of these four logical families. The brief is simple, the underlying logic is precise.
The current value reaches, exceeds, or falls below a threshold you set. The "is the number where it should be?" check.
How much a metric moved over the last N days. The movement itself is the signal — not the absolute value.
How far the current value drifts from a reference: your window's average, the same week last year, or an 8-week weighted-decay baseline.
The pickup is at or near zero — nobody is booking and nothing has moved. The "forgotten day" pattern.
11 templates. Pick one. Tune it.
You don't start from a blank page. Eleven pre-configured alerts cover the patterns most hotels watch in their first week. Pick a template, adjust the threshold to your context, choose recipients, set a schedule — done.
Custom alerts come next, when you've seen what matters to your property specifically.
- High-occupancy alert — coverage > 70% in the next 30 days
- Low weekend occupancy — < 40%, 14 days ahead, weekends only
- Fast room-night pickup — 7-day pickup ≥ 15
- Stuck rates — ADR unchanged for 7 days
- Stagnant occupancy — occupancy flat for 5 days
- Material deviation — ADR ±20% off window average
- Revenue anomaly — room revenue +30% above average
- Occupancy budget monitoring — vs your plan
- Revenue budget alert — total revenue vs plan
- No-change occupancy — pickup = 0 over 14 days
- Frozen rates — ADR 7-day pickup = 0 over 21 days
Every metric. All four types.
Any supported metric can be paired with any of the four alert logics. Mix and match for the watch pattern that matches your operating style.
Occupied-room count. The capacity metric.
Capacity-utilization ratio. The headline number.
Average daily rate — the headline pricing metric, accommodation-inclusive.
Room-rate-only ADR — strips F&B and ancillary to isolate the room price signal.
Room + ancillary stay revenue.
Room-rate-only revenue line.
Food & beverage line — separated for strong-MICE properties.
Ancillary revenue line — spa, parking, fees.
Top-line — sum of all revenue categories.
Every trigger, in a calendar heatmap.
Every evaluation is logged — whether it triggered or not. When it did trigger, the log captures which specific dates met the condition, with which actual values, and which recipients received the email (and whether it landed).
The web UI surfaces all of this in a calendar heatmap: the days with more triggers are darker; today is highlighted. Click any day to see the matching alerts. Filter by alert, by date range, or by recipient.
- Calendar heatmap — monthly view, intensity = trigger count
- Per-trigger detail accordion — which condition matched, on which dates, with what values
- Email-delivery status — silent on success, flagged on SMTP failure (the log persists either way)
- 7 / 30 / 60 / 90-day filter range
- Click-through from any heatmap cell to the matching alerts of that day
Email. Calendar. Pulse. Home tile.
The triggered dates as a formatted table inside the email. Plain language, actionable on a phone glance — no need to log in to act.
See AI / Daily Briefing →Monthly heatmap of trigger density. Click a cell to drill into which alerts fired, with what values, on that exact day.
See Decisions →"Are there any pickup spikes I should know about?" Pulse runs the evaluation right inside the conversation — same logic as the scheduled runs, just on-demand.
See Pulse AI →A live tile flags the most recent triggers so the first thing you see when you open Peaqplus is what needed your attention overnight.
See the Insights →An alert is a conversation, not a notification. It opens the right thread on the right day.
Pulse Chat runs alert logic on demand.
The four alert families don't just power scheduled checks. Pulse Chat — the platform's natural-language assistant — uses the same evaluation engine. Ask "Is there a pickup anomaly anywhere this week?" in plain English and the agent runs the matching check on your live data, in the conversation, with a 90-day lookahead limit.
Same logic as the scheduled alerts — but nothing is saved. The answer is a conversation, not a stored rule. When the answer surfaces something worth tracking, you can promote it to a scheduled alert in two clicks.
- On-demand evaluation in the chat thread — same logic as the scheduled runs
- Ad-hoc questions: "anomalies this week?" · "stuck rates anywhere?" · "70%+ occupancy days?"
- 90-day lookahead — beyond that, the alert needs to be scheduled
- Conversation-only — no log entry, no email; an exploration, not a commitment
One bell. Every event that matters.
Rule-based alerts are one source of signals. The whole notification surface is broader — and shares the same delivery infrastructure. When a task is assigned to you, when a deadline is tomorrow, when a meeting starts in two hours, when an AI analysis finishes, when a support reply lands, when the team announces a new feature — everything arrives through the same bell, on the same channels, with the same priority logic.
You decide which channels to use. The in-app bell is always on. Sound, desktop browser pop-up, and email digest are each a per-user toggle. High-priority events (a deadline tomorrow, a meeting in 30 minutes, a critical alert) light up the bell with a subtle shake, play a distinct sound, and break through the desktop browser pop-up — so the urgent never has to compete with the routine.
- Task assigned · task status change — when a decision lands a task on your plate
- Deadline tomorrow — every open task with a due date the next day
- Meeting in two hours — sent to every participant, every revenue meeting
- AI analysis ready — when an AI report or forecast correction completes
- Alert triggered — the rule-based alerts surface here too
- Support reply · new ticket activity — your support thread updates without an extra login
- Admin announcement — Peaqplus product news, targeted only to the hotels affected
- Discussion @mentions and replies — sibling surface · the sidebar unread badge lights up in real time
The signal travels however you want to hear it.
Four channels, one underlying event. Each user decides which channels they want active — preferences saved per-user, per-browser. The signal always reaches the in-app bell; the others are opt-in extras.
The bell icon in the top bar carries the unread count. Click it for the dropdown, see the full list at /notifications. Updates instantly when something new happens — no refresh needed.
Always on →A subtle chime for routine events, a more pronounced sound for high-priority ones. Pre-loaded so there is no delay on the first event of the morning. Toggle in the panel header.
Per-browser toggle →For high-priority events, a desktop notification surfaces even when the tab is in the background. One-time permission grant in the browser; turn it off anytime.
Opt-in · high priority →For team members who would rather not live in the app. Daily at 22:00 covers the last 24 hours; weekly on Monday morning summarises the prior week. Grouped by event type. Off by default.
Per-user setting →Every signal arrives in the bell. The other three are how loud you want the rest of your day to be about it.
When something new ships, only the affected hotels hear about it.
When the Peaqplus team ships a new feature, the announcement targets the hotels that actually have it. A new AI capability? Only AI-enabled hotels see the banner. A new Forecasting tier? Only the hotels with Forecasting active. Each user gets the announcement in their own language.
No mass email blast. No popup that everyone has to dismiss. The signal reaches the people whose product just got better — and stays out of the way for everyone else.
- Feature-flagged targeting — announcements go only to the hotels with the matching capability
- Per-user language — every recipient reads it in their own language
- Audit-logged — who sent what, when, to how many recipients
- Same delivery surface as everything else — bell, sound, email digest if enabled
The Forecast Advisor is live — ask about any day and it explains why the AI moved the forecast.
Der Forecast Advisor ist live — fragen Sie nach jedem Tag, und er erklärt, warum die KI die Prognose angepasst hat.
Set the rules. Let your numbers — and your team — find you.
In our 45–60 minute walkthrough, we run Peaqplus on our live demo environment — a simulated property with data that moves day to day — configure three of the templates against the demo property's pattern, and walk through the alert email, the calendar heatmap, and the notification bell when the rules trigger.
No setup fee. Opt-in, per hotel.