Summary
Campaigns are one of the main control surfaces in TruAgents. They define what kind of outreach should happen, to whom, through which channel, and with what instructions or agent support. But a campaign is still different from the actual execution history that follows later.Who this is for
- Anyone learning how TruAgents organizes outbound work
- Campaign managers
- Operators who need to connect campaign configuration to run and communication outcomes
Where to find it in the app
- Campaigns
- campaign detail pages
- Campaign Runs
- related draft and communications views
The campaign model
At a high level, a campaign brings together:- audience selection
- channel choice
- goal selection
- instructions
- agent behavior
- response behavior
- operational state
- related templates or supporting content where relevant
The practical building blocks
Audience
Campaigns usually target a segment rather than an arbitrary hand-picked list. That matters because outbound runs are expected to have a real audience definition behind them.Goal
A campaign goal is not just descriptive metadata. In the current product model, it is part of the configuration needed to explain what the campaign is trying to achieve and how later runs should be judged.Channel
Channel selection changes what “ready” means. Email, SMS, and phone flows share a common campaign model, but they do not have identical operational requirements.Agents and review
Writer and reviewer choices help define how content is generated and reviewed. For some channels, reviewer involvement is part of the normal safe path rather than an optional extra.The important distinction
- A campaign is the reusable definition.
- A campaign run is a specific execution event.
- The resulting drafts and communications are downstream evidence of how that run behaved.
Campaign lifecycle in plain English
Simple version:- define the campaign
- make sure it is actually runnable
- run or schedule it
- inspect the resulting run history, drafts, and communications
- edit the campaign again if the definition itself needs to change
What makes a campaign “runnable”
The current product logic already enforces a real preflight idea. Depending on the channel and run type, a campaign may need:- a goal
- a writer
- a reviewer
- a template
- a segment
- an active state
Channel-specific expectations
Email campaigns
Email campaigns are the most operationally strict in the current model. They are more likely to depend on a reviewer, a template, and verified email infrastructure.SMS campaigns
SMS campaigns still need campaign structure and review discipline, but they are usually less template-heavy than email.Phone campaigns
Phone flows still belong to the same campaign model, but some run requirements differ from email and SMS.How campaigns connect to the rest of the product
Campaigns should be read together with:- Segments, because audience choice changes who can be reached
- Goals, because campaign purpose affects how the work should be judged
- Campaign Runs, because execution history is where the definition becomes real
- Communications, because that is where you see what actually happened
Common misunderstandings to avoid
- Editing a campaign is not the same thing as understanding a past run.
- A campaign can look well-configured and still produce a problematic run if surrounding conditions are wrong.
- Goals, runs, drafts, and communications are all related to campaigns, but they are not interchangeable concepts.
- A campaign with no clear audience or goal is not a usable shortcut. It is just deferred confusion.
Good habits
- keep the goal easy to explain in one sentence
- make the audience explicit instead of vague
- treat test runs and real runs as different levels of confidence
- review communications and run history before changing the base definition
- let channel requirements shape the setup instead of pretending all channels behave the same