Notifications and alerts: browser notifications, quiet hours and voicemail

Arino One handles notifications through three distinct, independent settings screens — Settings → Notifications for personal browser alerts, Settings → Quiet hours for pausing scheduled outbound campaigns, and the Voicemails page for recordings left when a call goes unanswered — and the most common mistake is assuming any one of the three controls the others.

Browser notifications

Settings → Notifications is a per-device, per-user setting that surfaces a desktop or mobile system notification whenever a new inbound WhatsApp message arrives while the app is open. It has three parts:

• Permission. The browser's own notification permission must be granted first; a status badge shows whether it's granted, denied, default, or unsupported in the current browser, with a "Grant permission" button when it isn't yet granted.
• Notify on incoming messages. A toggle that only takes effect once permission is granted — a system notification fires for every inbound message once it's on.
• Play notification sound. A separate toggle for an in-app audible beep, which works even without notification permission, since it doesn't rely on the browser's system notification API.

You can also customise the notification's title, its body (used only when the inbound message itself has no text), and its icon — upload an image up to 200 KB, ideally a square 192×192 PNG. A "Send test notification" button lets you preview exactly what will appear before relying on it.

These settings are stored locally to your device and account — they are not a team-wide broadcast setting, and each agent configures their own.

Install as an app

The same settings page also documents installing Arino One as a Progressive Web App — from the browser's install icon on desktop, or "Add to Home Screen" on mobile. Installing gives a full-screen experience and is a practical way to make notifications feel closer to a native app, though it's still subject to the same open-tab-or-installed-app limitation described below. Install only works on the published deployment, not inside an in-editor preview.

The background-push limitation

Notifications in the current version require the app to be open in a tab, or open as an installed app — they do not arrive if the browser or the installed app has been fully closed. True background push notifications require additional setup beyond what ships by default. If reliable after-hours alerting matters to your team, plan around this limitation — for example, keep a dedicated device with the app open, rather than assuming a closed laptop will still surface an alert.

Quiet hours

Quiet hours, at Settings → Quiet hours, is a separate, administrator-only, instance-wide setting. When enabled, it pauses scheduled outbound campaign sends during a defined time window, evaluated in the company's configured timezone. It does not affect:

• Inbound messages, which are always received regardless of quiet hours;
• Live agent replies in an open conversation, which agents can send at any time;
• Personal browser notification settings, described above, which are entirely independent.

Configuration is a simple enable toggle plus a start and end time (defaulting to 22:00–08:00). Because this affects every scheduled send across the instance, only administrators can change it — see the user roles reference for the full permission matrix. For the related question of automatically replying outside business hours rather than just pausing sends, see auto-replies and quiet hours.

Voicemail

The Voicemails page lists recordings left by callers when no agent answers — from both WebRTC-based voice calling and Ping Me Sender's device-recorded voicemail path (identified by distinct badges), plus caller metadata such as name, number, country and which link or channel the call came in on.

Each voicemail supports:

• Playback, inline with standard audio controls (or a text-based demo player when only a transcript exists without stored audio).
• Automatic transcription, powered by ElevenLabs or an internal AI path depending on your configuration — see AI and API keys for how that choice is made. A status badge shows Transcribing, Failed, or the transcript itself.
• Manual re-transcription, via a Transcribe button, for any recording where transcription failed, was disabled, or hasn't run yet.
• Translation, into any language you specify, generated on demand and shown alongside the original transcript.
• Marking as listened / unlistened and deletion — deletion is immediate and does not have an undo.

New, unheard voicemails carry a distinct badge so they're easy to spot in a long list, and linking directly to a specific voicemail (for example from a missed-call alert) scrolls to and highlights that entry automatically.

Putting the three together

A realistic setup for a support team looks like this: agents each enable browser notifications and sound on their own machines so live conversations get their attention immediately; an administrator sets quiet hours to stop promotional campaigns firing at 2am in the company's timezone regardless of who's online; and anyone can check the Voicemails page the next morning for anything left by a caller when no agent picked up overnight. None of the three settings substitutes for either of the others, and each is managed from its own settings page independently.

Cost

Browser notifications and quiet hours are both included in the flat $50/month Arino Core connection and management fee, with no additional charge. Voicemail transcription cost depends on which AI path is configured: the managed option is metered at cost with no Arino markup, while a bring-your-own ElevenLabs key is billed directly by ElevenLabs outside Arino's pricing — see billing and plans for the full breakdown.

Frequently asked