Skip to content

Managing all your clients' sites from a single console

Clients, sites, agents, statuses, consumption and budgets: how the blabla.bot console organises a multi-client portfolio, plus a weekly follow-up routine.

Agencies and white label5 min read

Installing an AI assistant on one site is quick. Looking after ten, twenty or fifty of them, spread across as many clients, is another matter. You need to know which ones are properly installed, which consume the most, which are nearing their budget, and where knowledge is still being imported.

If each assistant lives in a separate account, that follow-up soon becomes a chore. The blabla.bot console is designed the other way round: one space for your agency, with all your clients inside. This article walks through how it is organised and suggests a follow-up routine.

The structure: agency, clients, sites, agents

The console mirrors how an agency already works.

  • Your agency owns the account, the credit balance and the alert settings.
  • Each client groups their sites. A client may have a brochure site and an online store, for example.
  • Each site has its domain, the addresses allowed to load the widget, its monthly budget and its consumption.
  • Each site has one active agent: the assistant answering visitors, with its knowledge, behaviour, AI option and appearance.

All data is isolated per agency. One client’s knowledge is never used to answer on another client’s site.

The portfolio: everything at a glance

The console’s home screen is the portfolio. It lists your clients and their sites, with the following for each site:

ColumnWhat it shows
SiteThe site’s name
AgentThe active agent
StatusThe site’s current situation (see below)
Conversations (30 d)Number of conversations over the last 30 days
Billed cost (30 d)What the site cost you in credits over 30 days
Budget this monthThis month’s spend against the budget, if one is set

At the top of the screen you will find your credit balance and the estimated runway in days, based on your consumption over the last 7 days.

Site statuses

Each site carries a status, with its own label and icon:

  • Online: the agent is answering visitors.
  • To install: the agent or an allowed address is missing, or the widget has never been opened from the site.
  • Import in progress: a knowledge source is being indexed.
  • Low credits: the site is live but your balance is exhausted or close to it.
  • Paused (budget): the site’s monthly budget has been reached; its assistant stops answering until next month or until you raise the budget.

An “Alerts first” sort brings the sites that need your attention to the top. The top of the screen also summarises the portfolio: the number of sites, and how many are low on credits, to install, importing or paused. One look tells you whether the day will be calm.

Adding a new client in a few steps

Adding a client takes a few minutes:

  1. New client: enter their name.
  2. Add a site: its name and domain.
  3. Create the agent: the console offers a guided flow that starts from the site’s address and produces an agent ready to test.
  4. Adjust: knowledge, behaviour (from a template by sector and use case), AI option, appearance.
  5. Test in the simulator, then install by copying the embed code.

The site first shows as “To install”, then switches to “Online” as soon as the widget is opened from an allowed address.

Each site has its own screens

When you open a site, you get its working screens:

  • Knowledge: the agent’s pages, sitemaps and PDFs, their status, their last indexing and its cost.
  • Behaviour: role, mission, tone, greeting, forbidden topics, contact address for human handoff.
  • AI model: the chosen option and the estimated cost of each one.
  • Appearance: colours, logo, position, with a live preview on desktop and mobile.
  • Test: the simulator, which answers exactly like the real widget.
  • Install: the embed code to paste into the site.

Cost tracking at account level

The “Credits” screen brings together everything about money: balance, top-ups, alert thresholds, and a table of each site’s consumption for the current month, with its budget and state (no cap, within budget, alert threshold reached, budget reached). It is the basis for your invoicing and margin tracking.

A weekly follow-up routine

A portfolio is easier to manage with a short ritual. Here is a suggestion to adapt.

  1. Open the portfolio and sort by alerts. Deal with “Paused” sites first, then “Low credits”, then “To install”.
  2. Check your runway. If it drops below two weeks, plan a top-up.
  3. Look at the 30-day billed cost. A site whose cost climbs for no obvious reason deserves a look: a client campaign, a newly popular page, overly long instructions.
  4. Review budgets nearing their threshold. Decide with the client whether to raise the cap or accept a pause.
  5. Pick one or two sites to improve. Run a few real questions through the simulator, add a source or sharpen an instruction.

This routine takes little time and heads off most unpleasant surprises.

What comes next

The console keeps evolving. Several sections are planned but not available yet: browsing conversation history, a client area under your agency’s brand, and data settings (export, deletion). We will announce them when they are ready. Multiple team members per agency with different permissions are not defined yet either.

In short

One console, one balance, and all your clients organised the way you already manage them: client, site, agent. Statuses and the alerts-first sort tell you where to look; the conversation, cost and budget columns tell you what each site consumes. The rest fits into a weekly routine.

Tags

  • console
  • portfolio
  • agencies
  • multi-site