Skip to main content

PWA and notifications

Install the PWA​

Open /bitrix/tools/zorka.chat/operator.php over trusted HTTPS, log in, and click Install application. From the admin iframe, the button first opens the separate workspace. Ordinary HTTP/IP cannot install the PWA. It shares Bitrix permissions and history; offline conversation caching is not provided.

In 0.4.22, an unanswered browser installation request releases the button after eight seconds and displays manual instructions. This does not mean installation succeeded.

For Yandex Browser on Windows, use the address-bar menu → Install as application → Separate window, then Add shortcut in application settings. Update the browser and use a regular, not incognito, window if unavailable. Yandex instructions. The UI timeout and Chromium manifest readiness were tested; actual Yandex/Windows installation is not confirmed. On iOS, use Safari → Share → Add to Home Screen; verify your browser/OS version on the device.

Sound​

Workspace sound defaults to on, but the browser may require an initial user action before playback. The volume slider affects default/uploaded sounds and remembers this manager's setting in the current browser. Zero mutes it.

The site reminder interval defaults to ten seconds. Unclaimed conversations remind eligible managers; assigned unread messages remind their owner. Claiming stops the shared-queue reminder; reading stops the owned-message reminder. Other waiting conversations continue. This is an open-workspace sound, not a locked-phone guarantee.

Windows notifications​

  1. Click Enable system notifications in the workspace.
  2. Allow the browser permission; if no prompt appears, inspect this site's notification setting beside the address bar.
  3. Click Test notification and check Windows/browser notification settings and Do Not Disturb.

Permission and subscription belong to a browser and origin. HTTPS does not enable them automatically. A new domain, login or account switch can require re-enabling. The test button verifies authorized data retrieval/display, not the complete external push route. PWA installation and notification permission are separate actions.

System notifications announce new events; they do not repeat the ten-second sound timer. Clicking opens the authorized conversation.

Closed tabs​

The browser must remain running and the server must regularly dispatch notifications. Web Push depends on Google/Mozilla/Microsoft/Apple services. Providers receive an empty wake-up signal; the worker fetches text from your chat server after checking session/subscription binding.

The server needs OpenSSL/cURL, outbound HTTPS and recurring \Zorka\Chat\Push::tick(); execution. The native interval is ten seconds, but page-visit-driven agents alone are insufficient. Configure Bitrix agent cron or the module's optional CLI runner; actual delay depends on scheduling and the browser. Delivery is not guaranteed with the browser fully closed, offline or blocked by the OS.

A push subscription is not manager presence. Closing all workspaces eventually hides the visitor widget when online-manager checking is enabled.

The test-site owner confirmed Windows/Chrome notifications after HTTPS permission setup. This is not verification of every browser, provider or locked phone.