Frequently asked questions

It connects the tools your SDR team sends from, your dialer and HubSpot, and shows one set of numbers per rep and per campaign: activity, replies, meetings and pipeline. It also gives you one reply queue, a weekly report, enrichment control and AI help on top of those numbers.

It does not run outreach. There are no campaigns or sequences. The only thing it sends is a reply that a person on your team writes and sends from the reply queue, through the tool that received the original reply.

No. Your team keeps sending from the same tools. OutboundManager reads from them with API keys. If you switch tools later, connect the new one and your history, reps and attribution stay in one place.

Email: Instantly, Smartlead, Woodpecker, Lemlist. LinkedIn: HeyReach, Lemlist. CRM: HubSpot. Dialers: Klenty, Aircall, Dialpad, RingCentral, JustCall, Nooks, PhoneBurner. Enrichment: MoltSets, Apollo, Crustdata, Lusha, ZoomInfo, FullEnrich. Details are on Integrations.

Not yet. HubSpot is the only CRM today.

Connect your sending tools first so the backfill starts, then HubSpot, then your dialer. Then add reps, map senders, check campaign owners, set targets, invite the team and turn on the weekly report. The reasons are in Set up OutboundManager in the right order.

An admin adds the connections, because they involve API keys. A manager can do everything after that: reps, mapping, owners, targets, invites and the report.

The first sync reads up to the last 90 days. A few tools hold less in their API: Klenty about 30 days of calls and JustCall 3 months.

Every connection syncs automatically every day, plus Sync now whenever you need it.

Yes. Add one connection per account or workspace and give each a label.

Only accept their invite. They do not connect tools or paste keys.

Auto-replies and unsubscribes are not counted as replies here. Most tools count them. See How every number is counted.

The most recent email, LinkedIn message, LinkedIn invite or call to one of the deal's contacts before the deal was created, within 120 days, wins. See Attribution and HubSpot write-back.

No. They are not imported from any tool.

It moves to the new rep at once, for every past period. Crediting is worked out when a screen is opened.

It holds activity whose sender is not mapped to a rep and whose campaign has no owner. Map the sender or set an owner and it moves.

No. A HubSpot call that matches a dialer call within 120 seconds, to the same person, is ignored.

No. Draft with AI only writes into the reply box. A person presses Send.

It is built not to. It can only read the product's own reports, every answer links to the report it used, and a statement whose number is not in the data is removed.

No. See the Privacy policy.

Yes. An admin can turn it off for the whole workspace in Settings → AI.

No. A rep sees replies assigned to them, and unassigned replies that arrived on their own senders.

No. You bring your own provider keys and the providers bill you. OutboundManager controls the order, the quality floor and the budgets, and records what was spent.

Not within the cache period, 90 days by default. A find already made in your workspace is reused at 0 credits.

Not past their budget. Each person has a monthly cap, the workspace has one too, and a run whose worst-case estimate would pass either is refused. Only a manager can override.

It uses the status each provider returns: valid, catch-all, unknown or invalid. It does not run a separate verifier.

Pro is $27 a month or $250 a year per workspace, with every feature and unlimited reps. There is a 7-day free trial with no card.

The workspace becomes read-only. Your data is kept and dashboards stay visible, but syncing, sending replies, enrichment and AI pause until you subscribe.

No. The price is per workspace.

Yes, from Manage billing in Settings → Billing. The workspace stays active until the end of the paid period.

It reads. It writes only a reply a person sends from the reply queue and, if an admin turns it on, four attribution properties on HubSpot deals.

Encrypted with AES-256-GCM. They are never shown again after saving and never sent to the browser. See Security overview.

No. OutboundManager is run by an independent developer and does not hold a SOC 2 report or ISO certification today. We answer security questionnaires.

Not yet. Use a long, unique password for each login.

Revoke the key in your own tool. That cuts access at once. Then remove the connection or replace the key here.

There is no public API with its own keys today. See API and data access for the ways to get data out.

Removing a connection deletes what was synced through it. Deleting the workspace in Settings → Workspace deletes everything. See Your data.