Partners

What the platform supports today

• One login, many clients

  A single account holds as many workspaces as you need, one per client, switched from the sidebar. Each has its own catalogue, assistant, settings and plan.

• Your client's brand, not ours

  The “Powered by ChatWidget” line is a setting you can switch off, and the widget takes the client's colours, logo, greeting and language.

• A team per workspace

  Invite your client's staff as admins, editors or viewers, so they can answer handovers without seeing your other clients.

• Evidence you can show a client

  When a client asks why the assistant said something, you can open the trace and show them, instead of promising to look into it.

• Handover to your systems

  Signed webhooks for leads, handover requests, finished chats and completed sign-ins or orders.

• Per-client spending limits

  A monthly message cap and a spend cap on each workspace, defaulting to a hard stop rather than an overage. A client who goes viral cannot hand you an invoice you did not expect.

• Per-client API keys

  Issued and revoked per workspace, and never readable again once created. A key you gave a client's developer cannot be used against another client.

• Removing a client cleanly

  Deleting a workspace removes its content, conversations and traces. When an engagement ends you are not left holding somebody's customer data.

What does not exist yet

There is no partner programme, no agreed reseller discount and no revenue share, because none has been agreed. We would rather agree terms with the first agencies that use the platform than publish terms nobody has tested. If you manage several client stores and want to talk about how that should work, the contact form reaches the people who will decide it.

• Consolidated billing

  Workspaces bill individually. There is no parent account that pays for its children, so today either each client pays for their own or you pay each subscription separately and invoice them yourself.

• A partner portal

  No deal registration, no lead routing, no co-branded collateral, no partner tier badges. The console is the same console your clients would use.

• Client-scoped roles

  Roles are recorded and shown throughout the console, but server-side enforcement lands with single sign-on. Until then, treat editor access as trusted, which means being deliberate about what a client's own staff can reach.

• A reseller agreement

  Our acceptable use policy prohibits reselling the service without one, and there is no template yet. In practice that means talking to us before you put it in a client proposal, not afterwards.

This probably suits you if

• You build and maintain WordPress or WooCommerce stores, and an assistant that sells from the catalogue is a natural addition to what you already deliver.
• You are asked for chat and would rather not maintain your own, but do want to own the configuration rather than hand a client to a third party.
• Your clients' questions are answered by content you already manage, so the setup is an afternoon rather than a project.

It probably does not if

• You need multi-channel, WhatsApp, voice, email, social. This is a website widget and platforms built as help desks reach further.
• Your clients need a SOC 2 report this quarter. We do not have one, and the security page says so plainly.
• You want to white-label the console itself. Removing our badge from the widget is supported; rebranding the operator console is not.

Questions agencies usually ask

Why agencies choose it

Because the trace lets you answer a client’s “why did it say that?” with evidence rather than a promise to look into it.

How agencies usually start

Put the assistant on one client's store on the trial plan. Use the trace for a week to fix what it gets wrong, then show the client the conversations and the review queue. That tends to answer the question of whether it is worth rolling out to the rest. Each workspace carries its own plan; the pricing page lists them.