Short answer
Yes. A contact can be in any number of campaigns, each with its own entry, attempts and history. But it's one person: they're never dialed in two campaigns at the same time, every dial from any campaign (and manual calls) counts toward call-frequency limits, and you can skip leads that have a callback booked in another campaign.
Plenty of teams run overlapping campaigns: a *New leads* campaign and an *Aged leads* campaign, or one campaign per product. The same person can easily end up in several.
Separate entries, one person
Each campaign keeps its own entry for the contact, with its own:
- status (waiting, finished, skipped),
- attempt count and max attempts,
- cadence step, retry timing and last outcome.
Finishing the lead in one campaign doesn't change their entry in another.
Protections that work across campaigns
| Protection | How it works |
|---|---|
| Never two calls at once | A lead that's being dialed in one campaign, or is on any live call, is skipped everywhere else. |
| Shared call counts | Call-frequency minimums and maximums count every outbound dial to the number, from any campaign or a manual call. |
| DNC and DND | Company-wide. An opt-out anywhere stops calls everywhere. |
| Callback booked elsewhere | Turn on *Skip leads with a future callback elsewhere* and the lead won't be called here while a callback waits in another campaign. Optionally limit this to leads with certain tags. |
Why shared counts matter
Say Campaign A allows 2 calls a day and Campaign B allows 2 calls a day. Without shared counting, one person could get 4 calls a day. With it, the second campaign sees the 2 calls from the first and waits. See calls per lead per day, week and month.
Callbacks follow the agent
A due callback reaches the agent who booked it in whatever campaign they're dialing, not just the campaign it was booked in. See how scheduled callbacks work.