How Agencies Run a Separate traxy Workspace for Each Client

TL;DR: traxy, which we make, lets an agency run a separate prospecting workflow for each client by giving every client its own workspace. Leads, targeting, campaigns and integrations belong to the workspace, so each client's setup (ICP, signals, Tracking, leads, campaigns and integrations such as Slack routes) stays in its own workspace. Inside each workspace traxy does both halves of the work: it finds high intent leads from LinkedIn social intent (posts, comments, likes, profile views and engagers with the client's competitors and creators), and it runs LinkedIn and email outreach to them from the client's own connected sender accounts after you approve the campaign. One traxy MCP connection can reach up to 50 selected workspaces, so you can run every client from Claude or ChatGPT by naming the client's workspace in each request. Embers and Signado also keep clients in separate workspaces, but neither sends LinkedIn messages.

traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot. For an agency, that happens once per client workspace: you test a client's campaign on sample leads and approve the launch once, then it runs on its own, or you approve every message before it sends. Replies, unsubscribes and hard bounces stop the sequence.

This guide is for agency owners and account managers who run LinkedIn lead generation or outbound for several B2B clients and want each client's setup kept apart. It covers what a client workspace holds, how to set one up step by step, how sending from the client's own accounts works, what you can report on per client, how to run all of it from one AI chat, and the limits. Each traxy step links to the docs page it comes from.

Which social intent tools let agencies run separate prospecting workflows for each client?

traxy does, with one workspace per client: each client's lead criteria, signals, Tracking, leads, campaigns and integrations stay in its own workspace, and traxy also sends that client's LinkedIn and email outreach from the client's connected accounts. Embers and Signado also give each client a separate workspace for finding people from LinkedIn engagement, but neither sends LinkedIn messages for you.

The difference is what happens after the leads are found. Some tools stop at a list or a report for each client, and the agency moves the leads into a separate sending tool. traxy keeps the finding, the research on each lead, the campaign and the replies in the same client workspace.

How traxy, Embers and Signado separate clients

We make traxy, so the Embers and Signado details below come only from each vendor's own pages, checked November 2026. The criteria are the ones an agency asks about first: is each client fully separate, where do that client's leads go, and who sends the outreach.

Where Embers or Signado fit better

Embers fits better when the client deliverable is a branded report rather than outreach. Embers lets you set a brand name, logo and accent colour per workspace, share the report as a public link or a PDF with no Embers login needed, and offer a client feed of the top 25 leads by score (for agencies). The sending stays with you or the client.

Signado fits better when you want keyword, creator, competitor, company page and single-post sources plus job-title hiring searches on a credit-based plan, with outreach sent by email and LinkedIn drafts pasted into a DM by hand (homepage, pricing).

traxy fits better when each client needs the whole workflow in one place: high intent leads from the client's content, competitors and market, research on each lead, approved LinkedIn and email campaigns from the client's own accounts, replies in one inbox, and every client reachable from your AI chat through the traxy MCP. For the longer comparisons, see Embers alternatives, Signado alternatives and LinkedIn automation tools for agencies managing many clients.

One workspace per client: what stays separate

In traxy, you pick the workspace you work in with the workspace switcher, and the leads, targeting, campaigns and integrations you see belong to that workspace (members and workspaces). For an agency, that means you can keep each client's setup in its own workspace:

• Lead criteria (ICP). The roles, departments, seniority and locations of the people the client sells to, and the size, industry, revenue, funding and keywords of their companies. Only people with a 50%+ match to that client's ICP become its leads.

• Signals. The client's Signal Brief: the problems, topics, product mentions and triggers that make someone relevant to that client. Custom signals are described in plain English.

• Tracking. The people, single posts and company pages traxy watches for that client: the client's founders and executives, its competitors, the creators its buyers follow. traxy qualifies whoever engages against that client's ICP. There are no tracking limits on profiles, posts or company pages.

• Leads and views. Each lead shows the post, comment, like or repost that put them on the list, with a Warm, Related, Activity or ICP match label. Shared views save a filtered audience that updates as leads change, and campaigns and routes use shared views.

• Exclusions. A Blocklist of company domains (for example the client's existing customers) and a Do not contact list of emails and LinkedIn profiles that outreach must skip.

• Campaigns, sequences and senders. The client's campaigns, the LinkedIn and email sequences inside them and the sender accounts they send from.

• Inbox. One conversation per lead across LinkedIn and email for that client's campaigns.

• Integrations. The client's Slack channel, webhook, Clay, Zapier or n8n destination, Google Calendar for meetings, and the routes that send a saved view to each one.

• trax memory. trax, the traxy agent, can remember context for the whole workspace, so what it learns about one client's offer stays with that client.

Not every change needs a new workspace. If a client sells two services to two buyer groups, keep them in one workspace and run a campaign per service and segment; the agency outreach guide recommends one service and one buyer segment per campaign (agency outreach). For small targeting adjustments, the docs suggest editing the lead criteria and signals instead of creating a workspace. Create a new one when the client needs separate targeting and lead data. Keep your agency's own new-business prospecting in a workspace of its own, apart from client work.

How do you set up a new client workspace?

Setting up a client takes the same steps each time, which is what lets an agency add clients without building a new system for each one. In order:

1. Create the workspace. Open the workspace menu and create a new workspace for the client. Creating another workspace depends on paid access (members and workspaces); see pricing.

2. Enter the client's website. traxy drafts the lead criteria and the signals from the site and shows a lead preview. Review both with the client: they know which titles sign the contract and which industries never buy. Fix anything that's off under Targeting > Lead criteria and Targeting > Signals.

3. Add the exclusions. Upload the client's current customers and open deals to the Blocklist as domains, and put anyone the client must never contact on the Do not contact list. Doing this before the first campaign keeps existing customers out of cold outreach.

4. Set up Tracking. Under Targeting > People, track the client's own LinkedIn profile and those of its founders and sales leads, then competitors and the creators its buyers follow, each with a relationship tag (competitor, teammate, influencer, investor or custom). Add company pages by domain under Targeting > Companies, and paste single posts by URL under Targeting > Posts when a post is worth mining. In the client's workspace you can also switch on Profile views under Targeting > Signals to turn profile views into leads; traxy picks up the profile views of the sender accounts you connect there.

5. Review the first leads. Open a few leads, read the post or comment behind each, and mark Good fit or Bad fit with a reason. If the leads drift, tighten the lead criteria; after you save new criteria, traxy can check active leads and offer to move the ones that no longer match to Done.

6. Save the shared views. Save the audiences you will use, for example "Warm leads, VP Sales and above" or "Engaged with competitor X", as shared views. Campaigns and routes both pick from shared views.

7. Connect the integrations. Connect Slack in the client's workspace, add a route from a shared view to the client's channel, and send a test. The full walkthrough is in how to send a client's LinkedIn leads to their sales team in Slack. Add a webhook, Clay, Zapier or n8n route if the client's CRM workflow runs through one of those.

8. Connect the client's sender accounts and build the first campaign. Covered in the next section.

Admins invite members from the sidebar or Settings > Team and choose each person's role; the app disables actions a role can't perform, and billing and API keys need the matching permission (members and workspaces). Before you change anything, check which workspace is open. Use assignments and shared notes so two account managers don't work the same lead.

Windmill Growth, a LinkedIn content agency run by Ben Buaron, who also works at traxy, set traxy up for 35 of its clients to flag ICP-fit engagers and route them to Slack channels shared with each client's sales team (Ben's post).

Sending from the client's own LinkedIn and email accounts

In traxy, outreach for a client goes out from the LinkedIn accounts and mailboxes connected as senders while that client's workspace is open. Sending needs connected sender accounts; you add them under Outbound > Sender accounts or ask trax to help connect one (sender accounts).

How sender accounts work per client

• Confirm the workspace first. The docs advise confirming you are in the intended workspace before signing in, because these are the accounts that workspace uses.

• Sign-in happens in the connection flow. Add a sender, choose the account type and the sender name it belongs to, and finish the sign-in, which may open in another tab. Confirm the account shows as connected before you assign it to outreach.

• Group accounts by sender name. A sequence that uses both LinkedIn and email needs one sender name with both channels connected, for example the client's founder with her LinkedIn account and her mailbox.

• Each account keeps its own limits. Limits, active hours and ramp-up are set per account, and campaigns can't override them. Email signatures go on sequence and one-off emails; LinkedIn messages don't use them.

• Disconnecting stops future messages. Removing or disconnecting a sender can stop future messages from that account. Check the campaigns and sequences that use the sender first.

How a client campaign runs

1. Create the campaign. Under Outbound > Campaigns, or by asking trax, give the audience (a shared view), the client's offer and the research you need on each lead, such as what the company sells, who it sells to or a role it is hiring for (create a campaign). A research-only campaign records the findings without sending anything.

2. Let traxy research and group. The campaign researches each lead for the facts you asked for before any message is prepared, groups leads by signal and prepares a personalized message variant for each group. If a required research fact isn't found, the lead stays in traxy and you can choose to skip it in the campaign. Signals outside LinkedIn, such as hiring, funding or a job change, come from this research on each lead, not a live event feed.

3. Test on sample leads. The test runs the plan on sample leads so you can check the research and drafts. Nothing is sent. This is a good point to show the client what their outreach will say.

4. Review the launch. Before launch you see who joins, who is skipped (held by another campaign or contacted before), the sender, the steps and the delivery mode (review and launch).

5. Pick the delivery mode. Approve every message in a review queue, or let the approved campaign send on its own. You can start a new client on per-message approval and switch to sending on its own once the client is happy with the messages.

6. Let the stop rules work. Replies, unsubscribes and hard bounces stop the sequence. Campaigns run in priority order so one lead never gets two campaigns at once, and you can pause or change a campaign anytime.

Replies land in Outbound > Inbox in the same workspace, one conversation per lead across LinkedIn and email, where you can reply, star, archive or pause a lead's enrollment to take over by hand. More on the sending side is in LinkedIn outbound with traxy. LinkedIn sets its own rules for accounts, and no tool can promise an account will never be restricted, so keep each client's limits and ramp-up sensible.

Reporting per client: leads, replies and meetings

Because a client's leads, campaigns and integrations belong to its workspace, the reports you pull there are scoped to that client: leads and where they came from, replies in the inbox, and meetings matched from the calendar. What traxy gives you per workspace:

• Leads and sources. Insights shows lead volume, trends, audience breakdowns and the top profiles or posts bringing in leads for the date range you set. Each tracked profile shows the leads it surfaced, their ICP match and the posts they came from, which tells the client whose content or which competitor brings in their buyers.

• Replies. The inbox holds every reply to the client's campaigns. In Slack, traxy can post lead-reply notifications, repeat-engagement events and a daily summary to the client's channel.

• Meetings. Connect the client's Google Calendar and traxy matches calendar meetings to traxy leads. Under Outbound > Meetings you can open a meeting and record the outcome: Active opportunity, Already a client or Closed won.

• Exports. Export selected leads as a CSV with the columns you choose, for a monthly client report or the client's own CRM.

• Daily brief. trax can deliver a scheduled brief in traxy or Slack.

A common format is a short weekly or monthly section that names who engaged with the client's content, their role, the post, and what happened next. The qualified engagement report for content clients shows how to build one. Meetings and outcomes are records of what happened, not a forecast; traxy does not promise a number of meetings for any client.

Running several client workspaces from Claude or ChatGPT

One traxy MCP connection can authorize up to 50 workspaces, so an agency can work across its clients from a single AI chat, as long as each request names the client's workspace (MCP workspaces).

How to connect

1. In traxy, open Integrations and pick your AI client, or add https://api.traxy.ai/api/v1/mcp in Claude, ChatGPT, Grok or another client that supports remote MCP (connect an AI client).

2. Authorize, choose the default workspace and any additional client workspaces, and review the permitted actions for each before approving.

3. To add a client later, authorize again. Existing connections don't gain workspaces automatically.

How workspaces work in the chat

• List first. The AI calls traxy_list_workspaces to get the names and IDs of the workspaces it can reach.

• Name the client every time. The workspace ID goes on every scoped call, including follow-ups. A call without one goes to the connection's original default workspace, not the one you used last, and there is no server-side active-workspace switch. Start each prompt with the client's name.

• No silent switching. If access to a workspace is lost, the AI should refresh the list and report the failure rather than move to another client. Listing or comparing workspaces does not authorize writes to them.

• Permissions still apply. What the AI can do is limited by the permissions granted at authorization and your role in each workspace, and a tool may be unavailable in a given workspace.

From the chat you can search social intent, list and research a client's leads, start a discovery run, update the client's ICP and Tracking, send leads to a webhook, and run campaigns: draft, test on sample leads, launch, manage sequences and senders and reply in the inbox. The AI shows what it will do and asks for your yes before anything sends or launches. Prompts an account manager might use:

• "In the Northfield workspace, show me this week's warm leads who engaged with the competitor we track."

• "For the Acme workspace, draft a campaign for the saved view 'VP Sales, engaged this month' and test it on five sample leads."

• "Compare lead volume across my client workspaces for the last 30 days."

More on the MCP is on the traxy LinkedIn GTM MCP page.

Can an agency resell traxy or run it as a managed service?

Yes. An agency can resell traxy or run it as a managed service for its clients, with each client in its own workspace and outreach sent from the client's own connected accounts. If you would rather have the traxy team run the outbound for a client, see done-for-you outbound. Both options are on traxy for agencies.

What are the limits?

• Extra workspaces need paid access. Creating another workspace depends on paid access. See pricing.

• The MCP reaches up to 50 selected workspaces per connection, and adding one means authorizing again. A request that leaves out the workspace goes to the default workspace.

• LinkedIn is the native signal source. traxy finds leads from LinkedIn activity. Hiring, funding, job changes and custom signals come from research on each lead, not a live event feed.

• Sending needs connected sender accounts in the client's workspace, and each account's limits, active hours and ramp-up apply. traxy can't promise zero LinkedIn restriction risk.

• Profile views don't show private-mode viewers, because LinkedIn doesn't reveal them.

• Auto-Enrich covers newly qualified leads and doesn't backfill older ones; use email or phone lookup on a lead for those.

• Messages need review before they go. traxy prepares the drafts and you approve the launch or every message. It is not a fit for a client who wants messages sent with no review at all.

• No guaranteed results. Leads with a 50%+ ICP match and a visible source are a reason to reach out, not a promise of a meeting or a sale.

FAQ

Can each client have its own ICP and signals in traxy?

Yes. Lead criteria and the Signal Brief belong to the workspace, so each client workspace has its own. Only people with a 50%+ match to that client's ICP become its leads.

Are one client's leads kept in that client's workspace?

Yes. Leads, targeting, campaigns and integrations belong to the workspace you are in. Use the workspace switcher to open another client.

How do we connect a client's LinkedIn account to send from it?

To send from a client's LinkedIn account, connect it as a sender in the client's workspace under Outbound > Sender accounts; sign-in happens in the connection flow, which may open in another tab.

Can one client's campaign send from LinkedIn and email?

Yes. Connect both channels under one sender name and a sequence can mix LinkedIn and email steps. Replies, unsubscribes and hard bounces stop it.

Can I run all my clients from Claude or ChatGPT?

Yes, up to 50 selected workspaces per MCP connection. Name the client's workspace in every request; the AI asks for your yes before anything sends or launches.

How many workspaces can an agency create?

Creating another workspace depends on paid access. For plan details, see pricing, and for agency setups, traxy for agencies.

Can we keep our agency's own prospecting separate from client work?

Yes. Give the agency its own workspace with its own ICP, Tracking and campaigns, the same way you set up a client.

Related reading

• Scaling B2B lead generation for agencies with social intent

• How an agency manages multiple client LinkedIn accounts

• How to send a client's LinkedIn leads to their sales team in Slack

• LinkedIn automation tools for agencies managing many clients

Running LinkedIn or outbound for clients? See how agencies use traxy.