Skip to main content

​
Brands

A brand is the company you are selling. It owns that company’s inboxes, campaigns, sequences, folders and chats, and it carries the context that makes the agent’s output specific rather than generic.

​
What to fill in

This is the highest-leverage five minutes in ManyPI. The brand is injected into every lead search — so the agent can judge “would this company want it?” — and into every AI-drafted email. A workspace with a thin brand produces exactly the generic output people complain about.

​
One brand or several

One workspace with several brands is the agency case: one client per brand, each with its own sending domain, its own idea of a good lead, and its own campaigns and replies.

​
What is and is not brand-scoped

Leads being pooled is deliberate: the public API has callers relying on it, and the brand filter in the grid is a lens you apply, not a wall the server imposes. Most list endpoints accept ?brand=<id> to narrow or ?brand=all to widen across the workspace. Per-brand deliverability settings — validate on enroll and skip unverifiable — let an agency’s cold-outbound brand and its warm-referral brand behave differently, which is the whole point of the separation.

​
Teams

Every paid plan is team-capable. Invite members from Settings → Organization; credits pool across seats rather than being divided per person.

​
What teammates share

Leads, campaigns, sequences, chats and folders inside the workspace are shared, not private to whoever created them. That is what makes a pooled lead list workable — a teammate can act on a lead you found without you handing it over. Members can be restricted to specific brands, in which case those are the only brands they see anywhere: the switcher, the picker and the brands screen.
Exceeding your seat limit blocks sending rather than silently over-billing you. The API returns 403 with a seats-exceeded error.