New client onboarding
Spin up {{client_name}} as its own project
Fresh VAPID keys, fresh audience, fresh sending domain — nothing leaks between clients.
Industry
ReachBell for agencies & resellers.
Run engagement for every client brand from one account. Separate projects keep each audience isolated, per-project analytics prove the ROI, and four channels mean no vendor sprawl to mark up.
The problem
A different login for every client, times four channels.
Running engagement for a roster of brands turns into a spreadsheet of credentials nobody wants to own.
Agency life is a tab-management problem. One client wants web push, another wants email, a third insists on WhatsApp, and somewhere a retail account needs SMS reminders. Stitch that across OneSignal, Mailchimp, a WhatsApp BSP, and an SMS gateway — then multiply by every brand on your roster — and you’re maintaining dozens of logins, each with its own dashboard, its own export format, and its own monthly invoice. The account manager who knew where everything lived just went on leave, and onboarding the next client means repeating the whole setup from scratch.
The scarier failure mode is a crossed wire. When client audiences live as tags or lists inside one shared account, it only takes one mis-selected segment to send Client A’s flash sale to Client B’s subscribers. That’s not an awkward typo — it’s a trust-ending incident. Agencies need each brand’s audience, keys, and sending identity walled off by default, not by remembering to filter every single time.
Then there’s the margin. When every channel for every client is a separate per-tool subscription billed in dollars, the vendor stack quietly eats the markup you were supposed to keep. And come renewal season, the client asks what they actually got for it — a question that’s hard to answer when the numbers are scattered across four dashboards that don’t agree on what a click is.
Templates
Templates you can reuse across the whole roster.
Build a campaign shape once, then drop it into each client's project with their own merge tags and audience.
Retail flash sale, web push
{{client_name}}: {{discount}} off ends tonight
Sent to the client's own subscribers only. Schedule respects their quiet hours, not yours.
Cart recovery, email + WhatsApp
Still thinking it over, {{first_name}}?
Push first, fall back to email, then WhatsApp if there's still no click — one waterfall per client.
Monthly client report
{{month}} engagement for {{client_name}}
Sends, clicks, CTR, and revenue attribution pulled straight from that project's analytics.
Client reviewer access
{{client_name}} can watch, not touch
Invite the client as a VIEWER so they see results without editing campaigns or keys.
SMS appointment reminder
Reminder: {{service}} on {{date}}
DLT-compliant SMS for the client's bookings — billed on your account, priced in rupees.
Agency workflows
Workflows for managing many brands at once.
Onboard a client, reuse your best playbook, and prove the result — without the audiences ever touching.
Stand up a new client in an afternoon
Take a brand from kickoff call to live campaigns without touching anyone else's data.
- 01Create a dedicated project for the client — its subscribers, segments, and keys live only there.
- 02Generate web push VAPID keys for the client's origin and drop the snippet on their site.
- 03Connect the channels the engagement actually needs — email sending domain, WhatsApp, and SMS sender.
- 04Rebuild the client's saved segments (by country, device, tags, or last-seen) inside the project.
- 05Invite the account manager as an ADMIN and the client's stakeholder as a VIEWER.
- 06Ship the first campaign — every send, click, and impression is scoped to this project alone.
Run the same playbook across every client
Reuse a winning campaign shape without copy-pasting audiences or risking a cross-client send.
- 01Build the template once — say a three-step cart-recovery waterfall — in your reference project.
- 02Recreate it per client, swapping in that brand's merge tags, segments, and quiet hours.
- 03Trigger on the client's own events (`cart.abandoned`, `order.placed`) piped to the events API.
- 04Branch on a condition step: if push isn't clicked within 2 hours, fall back to email, then WhatsApp.
- 05Cap frequency per project so one client's subscribers never see a duplicate from overlapping flows.
- 06Exit the flow on the client's conversion event so buyers stop getting nudged.
Prove ROI at the monthly review
Walk into each client check-in with numbers from that client's project, not a blended export.
- 01Open the client's project — analytics are already scoped to their audience and campaigns.
- 02Pull sends, delivery, CTR, and revenue attribution for the period across all four channels.
- 03Compare web push vs. email vs. WhatsApp vs. SMS to show where the budget worked hardest.
- 04Check the 90-day audit log to answer exactly who sent what, when, during the period.
- 05Share read-only results with the client's VIEWER seat so the report is self-serve next month.
- 06Roll the wins into next month's playbook and apply them to the next client in the roster.
How it works
One account, a project per client.
No separate reseller console to learn — just the multi-project model the platform already runs on.
The unit of separation in ReachBell is the project. Give each client their own project and everything that defines their engagement — subscribers, saved segments, templates, channel configuration, and analytics — lives inside it. Web push VAPID keys are generated per project, and REST API keys are scoped per project too, so a credential for one client physically cannot reach another client’s list. Isolation is the default state, not a filter you have to remember to apply. Projects on Growth and above are unlimited, so taking on the next brand is a new project, not a new contract.
Access maps cleanly onto how agencies are staffed. Team roles are OWNER, ADMIN, MEMBER, and VIEWER. Keep billing and ownership with the agency’s OWNER, let account managers operate as ADMINs, and invite the client’s stakeholder as a VIEWER so they can watch their own results without touching campaigns or keys. Every administrative action is captured in a 90-day audit log, so when a client asks who sent what and when, the answer is one screen away rather than a forensic exercise.
Because web push, email, SMS, and WhatsApp all live on the same platform, a single campaign can run a channel waterfall per client instead of being spread across four vendors — and the whole thing is priced in rupees with GST invoices, so the markup stays yours instead of leaking into a stack of dollar-denominated subscriptions. You can start a client on the free tier to trial the work before they commit, and the same playbook you refine for one brand carries straight over to the next. (For the deeper product-event automation patterns, the SaaS use case covers the event-driven side in detail.)
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
How do I keep one client's audience from mixing with another's?
Every client gets its own project. Subscribers, saved segments, templates, channel config, and analytics all live inside that project, and API keys are scoped per project — so a key for one client can never broadcast to another client's list. There's no shared global audience to accidentally send to.
Is there a limit on how many client brands I can run?
Projects on Growth and above are unlimited, so you can add a new project for every client you take on without a per-brand surcharge. Each project carries its own subscribers, channels, and reporting, which is what keeps client work cleanly separated.
Can I give a client access to see their results without letting them edit campaigns?
Yes. Team roles are OWNER, ADMIN, MEMBER, and VIEWER. Invite a client stakeholder as a VIEWER and they get read-only visibility into that project's analytics — no ability to change campaigns, segments, or keys. Your account managers can be ADMINs, and billing stays with the OWNER.
Do all four channels work per client, or is push the only one?
Web push, email, SMS, and WhatsApp are all available per project. You configure each client's own sending domain, WhatsApp sender, and SMS sender ID inside their project, and a single campaign can run a channel waterfall — try push first, fall back to email or WhatsApp on no click — without juggling a separate vendor contract per channel.
Does ReachBell have a formal reseller or white-label program?
ReachBell is built so you can run all of your client engagement from one account using separate projects — that's the model today. We don't advertise a packaged reseller, revenue-share, or white-label tier here, so if a partnership arrangement is what you're after, email us and we'll tell you honestly what's possible rather than over-promise on this page.