The operator-grade layer

Scale every WhatsApp operation with confidence.

RelayLoop gives teams one place to manage multiple WhatsApp accounts, automate inbound journeys, schedule campaigns, and connect webhooks without losing control of session health.

Create workspace View dashboard

Multi-account QR onboarding, session recovery, account-aware webhooks.

Flow-ready Menus, questionnaires, reviews, feedback, and follow-up journeys.

API-backed Same REST surface powers the dashboard, automations, and integrations.

RelayLoop console

Run the whole operation from one calm surface.

Live

Connected accounts

Across sales, support, onboarding, and review collection.

Queue-safe sends

48k

Campaign and flow messages processed with pacing rules.

Inbound journey

Keyword trigger -> menu -> feedback capture -> webhook handoff

Active

1. Welcome

Route users into the right branch.

2. Ask

Capture answers and score intent.

3. Push

Trigger follow-up or external systems.

Account safety

Warm-up, rate limits, retry logic

Architected for teams that need both control and speed.

A product surface for operators, developers, and customer teams running WhatsApp at real scale.

Multi-account connectivity

Spin up multiple number containers, authenticate by QR, recover sessions, and keep health visible without mixing tenant state or losing account scope.

Lifecycle

Connected, disconnected, expired, QR required

Recovery

Instant QR refresh and persistent session handling

Automation and webhooks

Trigger flows on inbound chats, fan events into tenant webhooks, and orchestrate message logic that reacts to account and message state in real time.

Inbound menus and questionnaires
Account-scoped webhooks
Review and feedback routing

Developer-first API

Ship with the same REST surface the dashboard uses: auth, accounts, messages, campaigns, webhooks, and tenant-ready API keys.

Safety and compliance guardrails

Protect account health with warm-up limits, randomized pacing, failure thresholds, opt-in enforcement, and queue-safe execution.

Warm-up logic

Start conservative on new numbers before unlocking volume.

Auto-stop thresholds

Pause when failures or block signals rise beyond safe bounds.

Opt-in enforcement

Keep outreach and inbound automation tied to clean contact state.

Architecture

A split system designed for session-heavy workloads.

Laravel owns tenancy, auth, API keys, contacts, campaigns, flow state, webhook retries, and the product surface.

The Node worker handles WhatsApp Web sessions, QR generation, inbound message capture, and outbound transport.

That gives you a SaaS core that stays clean while the memory-heavy browser/session work lives behind an internal engine boundary.

Tenant core

Users, tenants, contacts, flows, campaigns, webhooks, and API access live in Laravel.

Session engine

The WhatsApp worker owns QR auth, session boot, inbound events, and outbound delivery.

Automation fan-out

Events flow back into Laravel for flow execution, attachment hosting, and webhook delivery.

Enter the workspace

Keep the polished landing page, but don’t lose the functional entry point. Register or sign in directly into the RelayLoop dashboard.

Operator access

Launch a tenant workspace and start routing conversations.

1. Create the workspace

Provision the tenant, owner account, and dashboard session in one move.

2. Connect WhatsApp accounts

Generate QR sessions and keep each sender visible and isolated.

3. Activate outbound and inbound logic

Run campaigns, flows, webhooks, and API integrations from the same product surface.

Ready to make WhatsApp operations feel coordinated instead of chaotic?

RelayLoop is built for teams that need multi-account control, inbound automation, campaigns, attachments, webhooks, and API access from one product.

Create your workspace Open dashboard