Clear responsibility helps prevent duplicate outreach, missed replies, unsafe activation, and unclear decisions. If your team uses lists, campaigns, trackers, or replies without named owners, it becomes easy for the same person to be contacted twice, for a campaign to be activated without a final check, or for replies to sit unanswered.
This article describes a recommended operating model for Signalist. These are not mandatory Signalist system roles, and not every responsibility needs a different person. In a smaller team, one person may own several decisions. What matters is that each decision has a clearly named owner before your team scales outreach.
If ownership is still unclear, stop before activating any campaign or recurring workflow. It is safer to delay activation than to create duplicate outreach or unclear reply handling.
Start with functional responsibilities, not job titles. You are defining who owns a decision, who performs the last check, and who is accountable when something is unclear.
| Responsibility | Recommended owner | Key decision | Final checkpoint |
|---|---|---|---|
| List and data-source owner | The person who builds or maintains the list or recurring source | Whether the source, filters, limits, and list contents are appropriate for the outreach goal | The list is reviewed for lead quality, scope, and obvious issues before it moves into campaign or review work |
| Scoring and message reviewer | The person who reviews fit, signals, research, and prepared messages | Whether the lead quality, scoring logic, message content, and context are good enough for review readiness | A sample of leads and messages has been checked before any activation decision |
| Sending and activation owner | The person allowed to use the sender and approve campaign activation or pausing | Whether the sender, audience, channel, limits, timing, and preview are safe to activate | The final sender, account, audience, channel, limits, and preview check is complete |
| CRM or data-handover owner | The person responsible for CRM rules, ownership mapping, or data handover | Whether a lead should stay in Signalist, sync to CRM, or be treated as already known | Known-contact, owner, and handover rules are applied consistently |
| Reply and follow-up owner | The sender, campaign owner, or a shared team owner | Who handles replies and what happens next after a response arrives | Each active campaign or sender has a clear reply path and follow-up responsibility |
These are functional responsibilities. They are not required permission names in Signalist, and they do not need to map to five different people. A small team may combine them, but you should still name the owner for each responsibility.
The goal is to move from vague team habits to a repeatable operating model. Define the workflow once, document it, and reuse it across lists, campaigns, and recurring sources.
:::info
A practical small-team model is often: one person owns the source, one person reviews quality, and one person owns activation and replies. If your team is smaller, one person may cover multiple steps, but the checkpoints should still be documented.
:::
Do not activate outreach when ownership is unclear. If nobody can say who owns the list, who reviewed the message, or who approved the sender and audience, stop and resolve that first.
Do not bypass sender, permission, account, or workspace restrictions. If a sender is unavailable, an account is not connected, or a permission check blocks the workflow, resolve the underlying setup instead of working around it.
Do not contact a person again until duplicate, CRM, prior-outreach, customer, and opt-out checks are complete. This is especially important when multiple people build lists, import contacts, or run recurring sources.
Escalate unclear replies, ownership conflicts, and account restrictions to the responsible administrator or Signalist support. When the issue affects activation or sending, avoid making multiple campaign changes at once until the cause is clear.
| Problem | Solution |
|---|---|
| Two team members contact the same person. | Pause the affected workflow and review your duplicate rule first. Check related lists, known CRM status, prior outreach, and who owned the approval decision. Then update the owner and deduplication rule before you continue. |
| Nobody knows who should handle a reply. | Define a reply owner by sender, campaign, or team process. If your workspace uses separate reply views, document which owner checks each one and how unclear cases are escalated. |
| A campaign is ready but nobody is authorized to approve activation. | Do not activate it. Assign a clear activation owner who is allowed to perform the final sender, audience, channel, limits, and preview check. |
| A recurring review contains more leads or signals than the team can process. | Reduce source scope, tighten review criteria, or lower limits for the next run. It is better to process a smaller reviewed set well than to let a large queue build without ownership. |
| A CRM contact or existing customer appears in a new outreach workflow. | Apply the documented known-contact rule before using the lead. Check CRM ownership, customer status, prior activity, and whether the contact should be excluded, reassigned, or handled outside the campaign. |
The following related articles are planned for this help center:
This walkthrough helps you reach the smallest safe first result in Signalist. You will check the essentials, choose a suitable lead source, build a small test list, review lead quality, and reach the message review stage.
This article walks you through verifying users, permissions, connected accounts, and campaign senders step by step.
Tracker lists are the collections of companies Signalist watches for you. Every signal we detect is matched against your lists.