Outreach planning · Practical guide
Outbound team roles: assign decisions, not just activity targets
Assign an owner to each decision that can block or change the campaign. One person may hold several roles, but the responsibilities should still be explicit.
Reviewed · Examples are illustrative
Who this helps: Business owners and operators planning audience, offer, ownership and review decisions.
Define the decision
A campaign can have a named manager while no one owns source verification, opt-out reconciliation or reply acceptance. Splitting responsibilities by decision makes gaps visible. It also reduces the risk that every operator assumes another person has approved the audience or fulfilled an information request.
Work through the procedure
- List the decisions from audience selection through commercial handoff.
- Assign a responsible owner and a backup for time-sensitive work.
- Define what evidence crosses each handoff and how acceptance is confirmed.
- Review workload and access so owners can actually perform the responsibilities assigned to them.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Research owner: verifies identity and relevance
Launch owner: approves audience, copy and settings
Inbox owner: reviews human replies and stop requests
Sales owner: accepts qualified next steps
Reporting owner: reconciles definitions and cutoff
In a two-person team, combine roles explicitly rather than leaving rows blank.Read the result
The map is not an instruction to hire five people. It is a way to make the work visible and decide which responsibilities can be combined safely. If the inbox owner is absent, a documented backup matters more than the number of people nominally assigned to the campaign.
Check before moving on
- Match access permissions to actual responsibilities.
- Keep credentials out of handoff documents.
- Confirm who may pause a campaign during an incident.
Limits and next action
This is an organizational design aid, not a description of every native team permission in Zintara. Verify actual workspace access and ownership behavior before relying on a role label in an external document.
Source: Zintara product context; procedures and examples are editorial guidance
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Write an outbound campaign brief that another operator can execute →
- Outbound audience exclusion rules: define who must stay out before import →
- Cold email learning agenda: choose what the next cohort should teach you →