Troubleshooting & Deliverability

Troubleshoot Push notifications

Use this guide when a customer cannot subscribe to your store’s Push notifications, a notification does not arrive, or its appearance differs between browsers.

For alerts about conversations received by your team in Hellotext, use Inbox browser notifications.

Before you start

Use one test device and browser first. Note the store URL, browser and operating system versions, and the time of the problem. If a notification arrived, keep a screenshot before dismissing it.

Push is available on Pro and Enterprise. Shopify and VTEX connections install the required components automatically. Merchants using those integrations do not need to publish a service-worker file or initialize Hellotext.js manually. For the complete setup path, see Set up Push notifications.

1. A notification does not arrive

Work through these checks in order:

  1. Open the live store on the device you are testing. Use the same browser profile and exact store address where you subscribed. A subscription in one browser or device does not subscribe your other browsers or devices.
  2. Confirm that you completed the store’s notification opt-in. A browser showing notifications as allowed is only one part of setup: the store must also finish subscribing that browser to Hellotext. If the opt-in showed an error or never confirmed success, retry it once after reloading the store.
  3. Check the site’s notification setting. If you previously blocked notifications, change that setting in the browser before using the store’s opt-in again. The store cannot override a blocked permission.
  4. Check your device’s notification settings. Allow notifications for the browser or installed web app. Check Focus, Do Not Disturb, and the notification center: a notification may have arrived without showing a banner.
  5. Check recent browser changes. If you cleared site data, removed the installed web app, or switched browser profiles, open the store and complete its opt-in again. Use a regular browser window for testing.
  6. Confirm the delivery test. Ask Hellotext Support to check the subscription and arrange a controlled test to that browser. Record the test time and whether it appears in the notification center.

On iPhone and iPad, Web Push requires iOS or iPadOS 16.4 or later and a web app added to the Home Screen. Open the store from its Home Screen icon and complete its opt-in there. If it opens as a normal browser tab, ask your developer to check the store’s web app setup. See WebKit’s Home Screen requirements.

2. Setup fails or a service-worker warning appears

A service worker is the small background script that receives notifications for your store. A warning such as Push service worker is not available means the browser could not obtain an active worker for Push.

Shopify or VTEX

  1. Confirm that the store is connected to the correct Hellotext business.
  2. Confirm that the current Hellotext integration is installed and enabled on the live storefront.
  3. After an integration update, reopen or reload the live store before retrying the opt-in.
  4. If the warning persists, send Support the store URL and the exact warning text.

The integration manages the worker. Do not replace the platform’s worker or add a second manual installation to fix this warning.

A custom website using Hellotext.js

Ask your developer to follow Set up Push with Hellotext.js and check:

  1. The live site uses HTTPS.
  2. The configured worker URL serves the JavaScript file on the same origin as the storefront, without a login page or an error response.
  3. The worker has become active and includes the Hellotext notification handlers.
  4. The page initializes Hellotext.js with the intended worker URL and waits for initialization before offering the opt-in.

Include the exact error rather than repeatedly reinstalling the integration or clearing browser data.

3. The notification arrives without an image or buttons

The browser and operating system control the appearance of a notification. Receiving the text without every visual element does not, by itself, mean delivery failed.

Where you are testing What to expect
Safari Large notification images and custom action buttons are not supported.
Chrome and other Chromium browsers using native macOS notifications Large images are ignored. Actions may be behind the notification’s hover or More menu.
Other browser and device combinations Appearance and the number of visible actions vary. Expand the notification and test the actual browser and device your customers use.

See Safari’s notification options and Chrome’s macOS notification behavior.

If an image is missing in a browser that supports it, ask your developer to confirm that its URL loads without signing in. Keep the message understandable from its title and body, and check that clicking the notification opens the expected page.

4. Two notifications appear for one message

One notification with the complete content and another with only the title can mean the store displays the same delivery twice. This can happen when two notification handlers process one message.

  1. Note whether both notifications arrive at the same time and have the same title.
  2. Take a screenshot of both, including any difference in text or buttons.
  3. For Shopify or VTEX, confirm the current integration is installed, then reopen the live store and repeat one controlled test.
  4. If it continues, contact Support. For a custom site, ask your developer to check that a Hellotext message is displayed only once, following the developer setup guide.

Do not remove other store services or overwrite the platform worker to troubleshoot duplicates.

5. Clicking the notification opens the wrong page

Record the destination you expected and the URL that actually opened. Check whether the same happens when clicking the notification itself and, where available, an action button.

For a custom implementation, ask your developer to review the notification’s destination and click handler. For an integrated store, send the example to Support. Displaying a custom action button does not automatically give it a different destination.

When to contact Support

Include:

  • Your Hellotext business and live store URL.
  • Whether you use Shopify, VTEX, or a custom installation.
  • The browser, operating system, and device used for the test.
  • The approximate time and time zone.
  • Whether the opt-in completed and whether any notification arrived.
  • The exact warning, screenshot, or unexpected destination.
  • Any recent integration update, domain change, or browser data reset.

See Contact Hellotext Support for contact details.

Was this article helpful?

Haven't found your answer?

Contact Us