An agency asked us a question many partners eventually ask: how do you run chatbots for your clients without the platform getting in the way? They were building chatbots for a growing list of client businesses. The chatbots worked. The trouble was everything around them: a separate login per client, dashboards carrying another company's logo, and clients asking why their emails came from a vendor they had never heard of.
What they told us
When an agency runs a chatbot for a client, the client should experience the agency's product. Every time the client saw another vendor's name — on a sign-in page, in an email, in the address bar — the agency's work became harder to explain and easier to bypass.
There was also the operational side. Each client meant its own credits, its own team needing the right access, and its own chatbot built from nothing. They asked whether all of that could live in one place, under their name.
How we approached it
Brand and access are trust questions, not cosmetic ones. A client's staff need exactly the access their role allows, an agency's clients must never see into each other's data, and the agency's brand must hold everywhere a client looks. We planned around those constraints:
- The agency's brand replaces Gydr's across the Console, sign-in and emails, on the agency's own addresses.
- One partner account manages many client accounts, each still entirely separate.
- Access is set per person, and changes apply immediately.
- A proven setup can be reused for the next client instead of rebuilt.
How it works
Your brand, end to end. White Label replaces Gydr's branding in the Console with the agency's, and custom domains put the Console and the hosted chatbot on the agency's own addresses. Sign-in screens and the emails clients receive carry the agency's logo.
One partner, many accounts. A partner manages its clients' accounts and allocates credits to each from its own pool, so billing follows the relationship. Each client account stays separate from the others.
The right access for every person. Custom permission sets give each person exactly the pages and actions they need — a client's marketing lead can edit knowledge without touching billing.
Start from what already works. A widget or skill can be duplicated as the starting point for the next client.
Be found. Partners have a profile and can list themselves in the public partner directory on infinichat.dev, and prospects who book a demo can be routed to a matching partner.
Where it leaves the agency
Clients sign in on the agency's domain and see the agency's brand. The agency's time goes into the chatbots rather than explaining the platform. What the agency builds for each client stays in that client's account.
Frequently asked questions
Can I run chatbots for my clients under my own brand?
Yes. White Label puts your brand on the Console, and custom domains put the Console and the hosted chatbot on your own addresses, including sign-in screens and emails.
How do credits work across many client accounts?
As a partner you manage your clients' accounts and allocate credits to each one from your own pool.
Can clients have limited access?
Yes. Custom permission sets grant each person exactly the pages and actions they need.