One agent, every channel — branded as your own
Answer on phone, WhatsApp, SMS, email, and an embeddable web-chat widget — one agent brain wearing your theme, logo, and custom domain, on a platform where branding never widens access.
Web chat · WhatsApp · SMS · Email · Voice · Embed
One agent behind the scenes, your front door out front
White-label isn't a widget-only feature. A retail brand, a university campus, an agency, or an insurance broker each gets a chat, inbox, and phone experience that looks like theirs — while one agent brain runs underneath.
Your brand, applied everywhere — no code
Set a workspace or brand's palette, logo, favicon, and typeface once. Every channel it touches re-skins instantly — configured from settings, versioned, and previewed live before it ships.
- ✓Per-workspace colors, logo, favicon, typography
- ✓Configured in settings — no builds, no forks
- ✓Live preview before you publish the theme
Every brand on its own domain
Point a brand's own subdomain at Mirakash and load the web-chat widget there. The host is verified before it resolves, TLS is issued and auto-renewed, and CORS grants match the same verified host — so a custom domain is a front door, never a back door.
- ✓Bring-your-own domain, verified before the widget loads
- ✓Automatic TLS with auto-renew
- ✓CORS scoped to the verified host — isolation holds
Branded on every channel, not just the widget
The brand follows the customer through every touchpoint — the web-chat widget, the emails, the WhatsApp thread, and the domain they all live on.
Web-chat widget
The whole chat widget carries your colors, logo, and typeface — desktop and mobile.
Email channel
The agent answers email threads and sends notifications from your look and, optionally, your domain.
Chat transcripts
Transcripts and post-chat summaries render under your brand and letterhead.
Launcher & favicon
The widget launcher, favicon, and browser tab title are branded — no Mirakash chrome leaks through.
Sender domain (DKIM)
Bring your own SMTP and DKIM keys — encrypted at rest — so email authenticates as your domain.
Embedded widgets
Drop the web-chat widget or a single flow straight into your own product.
Every brand gets its own space, isolated from the rest
Brands, campuses, and sub-teams each run their agent on their own branded domain, sealed off from siblings. Roll-up reporting stays with the operator at the top.
Retail brand
shop.asterandco.com chat.asterandco.com
One support agent answers on the brand's own chat subdomain, on WhatsApp, and over email — isolated from sibling brands, rolled up to the operator.
University with campuses
university.edu chat.university.edu
Each campus runs an admissions agent on its own branded widget and phone line; the system office sees the whole network.
Agency network
agency.com help.agency.com
Client-facing chat and voice run on an agency-branded widget — the end client never sees a third-party tool.
Or put the agent inside your product
Some teams want the conversation, not another tab. Drop the web-chat widget straight into your own site or app with a themed embed — or drive the same agent through scoped machine keys against the API.
Open the API docs<script src="https://cdn.mirakash.com/widget.js" data-agent="aster-support" data-brand="aster" data-theme="tenant" ></script>
Branding that can't widen access
Every white-label channel is bound to a verified host. The safe path is the only path — you can't brand your way into someone else's data.
Security & RBACVerified-host resolution
The web-chat widget only loads once its host is verified, and CORS grants match the same host — so branding can never widen access.
Encrypted BYO credentials
SMTP passwords and DKIM keys are AES-256-GCM encrypted at rest, masked on return, and never logged.
Isolated by construction
Each workspace or brand is a tenant; every query is scoped to its org in the data layer, not the UI.
Ready to put an AI agent on every call?
Book a walkthrough and see the voice pipeline, telephony, workflows, QA, and human handoff working together — on one platform.