ReachBell is a customer engagement platform that combines web push notifications, mobile push (FCM and APNs), email campaigns, and visual automations in one dashboard. You install a small snippet (or our WordPress plugin), design your opt-in prompt, and start sending targeted messages in minutes.

How is ReachBell different from OneSignal or Mailchimp?

Three things: every channel lives in one tool (no juggling a push vendor plus an email vendor), pricing is in Indian rupees with GST invoices and UPI payments, and automations are included on every paid plan instead of being an enterprise add-on. You get push, email, segments, A/B testing, and workflows without stitching together three subscriptions.

Do you support mobile apps as well as websites?

Yes. Web push works on Chrome, Firefox, Edge, and Safari via the W3C Push API. For native apps we support Android through Firebase Cloud Messaging (FCM) and iOS through Apple Push Notification service (APNs) — upload your credentials once and target every device from the same campaign.

How long does setup take?

Most sites go live in under five minutes: add a three-line snippet (or install the WordPress plugin), copy your service-worker file to your site root, and design your opt-in prompt visually from the dashboard — no code changes needed for prompt updates.

Is there a free plan?

Yes — the Free plan includes 1,000 push subscribers, 10,000 push sends, and 500 emails per month with one project. No credit card required, and you can upgrade only when you outgrow it.

Is ReachBell GDPR and DPDP compliant?

ReachBell is built privacy-first: subscribers get a hosted preference center to manage channels or unsubscribe with one click, consent events are recorded, and every admin action is captured in a 90-day audit log. We support the requirements of both the EU GDPR and India’s DPDP Act.

Can I pay in INR and get a GST invoice?

Yes. Plans are priced in Indian rupees, payable by UPI, cards, or net banking via Cashfree, and every invoice includes your GSTIN. International teams can pay by card in USD or EUR — Cashfree’s International Payments product handles global cards on the same checkout.

Can I migrate from another provider?

Yes. Import subscriber lists, tags, and templates via CSV or our REST API. Web-push subscriptions are origin-bound, so our high-converting prompt designer helps you re-collect them quickly — and our team will help you plan the cut-over at no cost.

All articles

TutorialWeb pushQuickstart 6 min read

How to Add Push Notifications to Your Website in 5 Minutes

A start-to-finish walkthrough: create a project, drop in the ReachBell snippet, host the service worker, and send your first push — all under five minutes.

DotSpheres Engineering

Engineering, ReachBell · 19 June 2026

Most tutorials for web push notifications turn into an afternoon of VAPID keys, service workers, encryption padding, and a half-finished admin UI. This one does not. If your site is on HTTPS and you can paste a script tag, you can be live in roughly five minutes.

Here is the exact path we walk every new ReachBell customer through.

Before you start

HTTPS — service workers are blocked on plain HTTP. localhost is fine for testing.
Root access to your domain — you need to host a tiny JS file at the root (more on this in step 3).
A ReachBell account — the free tier covers your first 1,000 subscribers, no card required.

Step 1 — Create a project (30 seconds)

Sign up, click New project, enter your site URL, and pick a default icon. ReachBell generates a fresh VAPID key pair scoped to your project — those keys are yours and you can export them at any time.

Step 2 — Drop the snippet into your <head> (1 minute)

On the Install screen ReachBell shows a snippet pre-filled with your project ID. Paste it into the <head> of every page that should be able to ask for permission — usually that means your global layout.

<script
  src="https://cdn.reachbell.com/sdk/v1/reachbell.js"
  data-project="prj_8f2a4b1c"
  async
  defer
></script>

That single tag loads the SDK, registers the service worker, and exposes a global ReachBell object you can call from your own code.

Step 3 — Host the service worker file (1 minute)

Service workers can only control pages at or below their own path. Browsers require yours to live at the domain root, so download the file from the install screen and upload it to `https://yoursite.com/reachbell-sw.js`.

Static sites — drop the file in `/public` (Next.js, Astro) or the root of your built output.
WordPress — upload via SFTP into the site root, or use the official ReachBell plugin and skip this step.
Shopify — use the ReachBell app from the App Store; Shopify will not let you write to the storefront root.

Hit `https://yoursite.com/reachbell-sw.js` in a browser. If you see the file contents instead of a 404, you are done with this step.

Step 4 — Trigger the opt-in prompt (1 minute)

By default the SDK does nothing visible — your visitors have to ask for the prompt. The cleanest way is a soft prompt button or a delayed banner. Here is the minimal call:

document.querySelector("#enable-push")
  .addEventListener("click", async () => {
    const sub = await ReachBell.subscribe();
    if (sub.granted) {
      console.log("Subscribed:", sub.token);
    }
  });

You can also call `ReachBell.showSoftPrompt()` to render the styled banner from the dashboard, with all your copy and timing rules already baked in.

Step 5 — Send your first push (1 minute)

Subscribe yourself, then head back to the dashboard. New campaign → Test send to me delivers a notification to the device you just registered. Title, body, image, and a click URL — that is it.

Title: It is alive 🎉
Body: Your first ReachBell push just landed.
URL:   https://yoursite.com/welcome

Click it. The browser fires the click event, the service worker opens your URL, and ReachBell logs the click against the campaign. Real numbers, real funnel, in under five minutes.

What to do next

Style your soft prompt and pick a sensible trigger (second pageview or 30 s on page works well).
Wire one transactional event — order shipped, sign-up confirmation — those land 20%+ CTR and pay for the integration on their own.
Set quiet hours and a per-day frequency cap before your first promotional campaign.
Add UTM defaults so clicks show up attributed in your analytics.

Everything beyond this — segmentation, automations, A/B tests, email and WhatsApp on the same subscriber profile — is in the dashboard the moment you need it. See the full pricing breakdown or jump straight to the Next.js integration guide if you want a framework-specific walk-through.

Put this playbook to work.

Push, email & automations — free for your first 1,000 subscribers.

Start free