ViaSocket
AI step, inside the workflow editorThemed to their editor, named as an AI step rather than an agent, served from their own domain.
White-label
It’s your product, not ours
Your logo, your colours, your domain. Your customers never see GTWY.
Same panel, two products
Identical infrastructure. Nobody would guess.
ViaSocket Agent Builder
Agent nameLead qualifierToolsMSG91 Bot Config
Bot nameSupport triageToolsLive
Re-skin it yourself.
The same GTWY infrastructure, running inside two real customer products. Switch between them — the screen, the naming and the workflow are entirely theirs.
Scope
What you can change — and what you can’t.
The limits are here rather than in your integration week.
| Element | Customisable | Notes |
|---|---|---|
| Logo and favicon | Yes | Uploaded per platform account |
| Colour palette | Yes | Full token set, light and dark |
| Typography | Yes | Your font family and scale |
| Component styling | Yes | Theme tokens, plus custom CSS for edge cases |
| Copy and labels | Yes | Rename “agent” to whatever your product calls it |
| Custom domain | Yes | CNAME to your subdomain, SSL issued automatically |
| Email templates | Partial | Sender and branding configurable; layout is fixed |
| Language / localisation | Partial | Confirm currently shipped locales with us |
| Builder layout | No | Panel structure is fixed — theming, not re-architecture |
Custom domain
Served from your domain.
Point a CNAME at us and the embed is served from your subdomain. SSL is issued and renewed automatically — there is no certificate for your team to manage.
agents.yourproduct.com CNAME embed.gtwy.aiThe no-branding guarantee
No GTWY logo. No “powered by.” No GTWY domain.
Nothing your users see identifies GTWY as the vendor behind the panel — not in the UI, not in the URL, not in the emails it sends.
The one exception: outbound webhook payloads and API responses your own engineers read carry GTWY field names. Your users never see them.
In production
Same infrastructure, two different-looking products.
ViaSocket and MSG91 both run this embed. Neither of them looks like the other, and neither looks like us.
MSG91
Assistant builder, inside the consoleThemed to the MSG91 console, isolated per account, with their own naming throughout.