Agency: a channel per client

Updated 1 October 2026 · BugsRadar team

Ten client sites, three stacks, two people who could fix any of them, and the client who calls before you know anything is wrong. The fix is not a bigger dashboard; it is one message per new error, in the chat of the people responsible for that client.

Projects and channels

Create a BugsRadar project per client site; the project name is the first line of every message, so "Acme shop · Error" needs no explanation. Then decide where each project reports:

• A chat per client - a Telegram group or Discord channel for the people who work on that client. Add it as a channel of that project.
• One chat for everything - one channel can serve several projects, so an internal "all clients" group that gets every project's errors costs nothing extra.
• Both - a project can have several channels. The client's own group gets their errors; your internal group gets everyone's.

Each channel goes through your own bot or webhook, so you control who is in the chat. A client who wants to see the alerts is one invitation away; a client who shouldn't see another client's errors never can.

Routing with rules

On the Pro plan every channel of a project can have a filter: level, modules, environments. The payments module to the developer who owns payments, staging to a channel that never wakes anyone, Critical to the Pushover of whoever is on call this week. See Rules.

Keys and the end of a contract

Every project has two API keys, and a key does one thing: it sends events to its project. The key lives in the client's deployment configuration, never in the repository. When a contract ends, press Regenerate and the site stops reporting to you; nothing else changes. If the client takes the project over, they create their own account and swap the key in configuration; the code stays as it is. See Keep the API key secret.

What it costs

Pro is $5 a month or $50 a year for unlimited projects and channels; it is one price, not a price per client or per seat. The Free plan covers 2 projects and 3 channels if you want to try the setup on two clients first. See Pricing.

What it doesn't do

There is no client-facing report and no history: BugsRadar stores nothing, and the chat is the record. Team accounts with their own channels, SSO and an audit log are coming with the Business plan; today the account is yours and the chats are where the team meets.

Where to go next

Maintenance after handover covers the project you delivered and still look after. Production, staging, dev shows how to keep staging out of the client's chat.