Mobile Notifications & On-Call

Overview

ET Ducky can deliver alerts straight to your phone — or any enrolled desktop browser. A Push Notification channel sends each matching alert to the enrolled devices of the people you choose — everyone, admins only, specific members, or whoever is on call per your on-call schedule. Tapping the notification opens your workspace’s Alerts tab, where you can acknowledge or resolve the alert and read its AI analysis.

Notifications are delivered through your phone’s native push service (Google or Apple), so there is no polling and no meaningful battery cost. Each alert produces one notification — repeated firings of the same alert update it in place rather than piling up.

Requirements

Platform	Requirement
Android	Chrome, Edge, or Firefox. Installing ET Ducky to your home screen is optional (but recommended for the full-screen app experience).
iPhone / iPad	iOS 16.4 or later, and ET Ducky must be added to the Home Screen first — Apple only allows web push for installed apps. Steps below.
Roles	A workspace admin creates channels and manages the on-call schedule. Any member can enroll their own phone.

Step 1: Install ET Ducky on your phone

Android

Open your workspace (yourworkspace.etducky.com) in Chrome and sign in.
When the “Get the app feel” banner appears, tap Install. (Or use the browser menu ⋮ → Add to Home screen → Install.)
ET Ducky now opens full-screen from its own icon.

iPhone / iPad (required for notifications)

Open your workspace in Safari and sign in.
Tap the Share button (the square with the up arrow).
Scroll down and tap Add to Home Screen, then Add.
From now on, open ET Ducky from the home-screen icon — notifications can only be enabled from the installed app, not from a Safari tab.

The installed app opens full-screen from its own icon, and you can pull down from the top of any page to refresh it — handy on a dashboard you keep open.

Step 2: Create the Push Notification channel (admin)

Go to Systems → Alerts → Notification Channels.
Click Add Channel.
Name it (e.g. On-call phones) and set Type to Push notification (enrolled devices).
Choose Who should this notify? (see table below), then save.

Audience	Who gets the notification
No audience (default)	Every enrolled device in the workspace
Everyone in the workspace	All members’ enrolled devices
Workspace admins	The workspace owner and members with the admin role
Specific members	Only the members you tick
On-call person	Whoever the on-call schedule covers at the moment the alert fires. If no shift covers that moment, workspace admins are notified instead — a scheduling gap never silences an alert.

The same audience picker is available on Email channels: resolved member addresses are merged with the channel’s explicit recipient list at send time, so an email channel can also target “the on-call person” without hardcoding addresses.

Step 3: Enroll your phone

On your phone, open ET Ducky (on iPhone: from the home-screen icon) and sign in.
Go to Systems → Alerts → Notification Channels and open the Push Notification channel (or the create dialog in Step 2 — enrollment works from either).
Tap Enable on this device.
When your phone asks for notification permission, tap Allow.
The panel confirms: “This device receives push alerts.”

Repeat on as many devices as you like — each enrolls separately. To stop notifications on a device, tap Disable on this device in the same place. Every device you enroll is listed under Settings → My Devices — see the next section.

Managing your enrolled devices

Open the account menu (your avatar, top right) and choose Settings. The My Devices card lists every device enrolled for push on your account: its label (e.g. Android · Chrome), when it was enrolled, when it was last seen, and a “this device” marker on the one you’re holding.

Remove unenrolls a device immediately — it stops receiving push alerts on the next send. Use it for a lost phone or a retired laptop; nothing needs to be uninstalled on the device itself, and it can always re-enroll later.
Enable / disable push on this device toggles enrollment for the device you’re using — the same control as in the channel dialog.

You can only see and remove your own devices; admins cannot remove another member’s device from here. Devices that stop responding (uninstalled browser, cleared data) are also pruned automatically after repeated delivery failures.

Step 4: Attach the channel to alert rules and test

Go to Systems → Alerts → Alert Rules and edit (or create) a rule.
Under Notification Channels, select your Push Notification channel. One rule can feed several channels — e.g. push the on-call person and post to Slack.
Back on the Notification Channels tab, press the channel’s Test button. Every device in the audience should receive a test notification within a few seconds.

Receiving and actioning an alert

The notification shows the severity, rule name, affected agent, and trigger time. Critical alerts stay on screen until you dismiss them; others behave like normal notifications.

Tap the notification. ET Ducky opens directly on your workspace’s Alerts tab.
Find the alert (newest first) and tap Acknowledge to claim it, or Resolve if it’s handled.
Tap View Details for triggering metrics and the AI root-cause analysis with recommended actions.

On-call schedule (admin)

Manage the schedule at Configuration → Time → On-Call Schedule. The card shows who is on call right now, the upcoming shifts, and two ways to add coverage:

Add a single shift

Open Add a shift, pick the member, start and end times (shown in your local timezone), and an optional note.
Click Add shift. Shifts can overlap — everyone covered at that moment is notified.

Generate a rotation

Open Generate a rotation and tick the members in rotation order.
Pick when the first shift starts, the shift length (day, week, etc.), and how many shifts to create.
Click Generate. The rotation writes ordinary shifts — edit or delete any single one afterwards for swaps and vacations.

Coverage gaps: if an alert with the on-call audience fires when no shift is active, workspace admins are notified instead, and the gap is recorded in the server logs. Keep the rotation topped up to avoid surprise pages to the boss.

Faster sign-in on mobile

Two sign-in conveniences ship alongside notifications: verification-code fields now support your phone’s code autofill (the current code appears above the keyboard — no app switching), and after signing in on a capable device ET Ducky offers one-tap passkey setup, so future sign-ins use Face ID or your fingerprint instead of typed codes.

Troubleshooting

Symptom	Fix
iPhone: “Enable on this device” says install first	Web push on iOS requires the installed app. Follow Step 1 (Share → Add to Home Screen), then open ET Ducky from the icon and retry.
Button says “Notifications blocked”	You previously declined permission. Android: site settings → Notifications → Allow. iPhone: Settings → Notifications → ET Ducky → Allow, then retry.
Enrolled, but no notifications arrive	Check three things: the channel is attached to the alert rule, the channel’s audience includes you, and the channel toggle is enabled. Then use Test.
Test works, real alerts don’t	The rule’s conditions haven’t matched, or the alert was suppressed. Check the rule on the Alert Rules tab and the Alert History tab.
On-call audience paged the admins	Working as designed: no shift covered that moment. Add or extend shifts in the on-call schedule.
Stopped after clearing browser data / reinstalling	Clearing site data removes the enrollment. Open the channel (or Settings → My Devices) and Enable on this device again.
Lost or replaced a device	Go to Settings → My Devices and Remove it — it stops receiving alerts immediately.
“Push is not configured on the server yet” (self-hosted)	The server administrator must configure VAPID keys (`Push__VapidPublicKey` / `Push__VapidPrivateKey`). See the Self-Hosted Deployment guide.

Privacy notes

Enrollment stores a per-device delivery address (a push endpoint issued by Google or Apple) and encryption keys in your workspace — not your phone number or any device contents. Notifications are encrypted end-to-end to your browser. Unenrolling (or clearing site data) invalidates the endpoint; dead endpoints are pruned automatically. You can review and remove your enrolled devices at any time under Settings → My Devices.