Summary
TruAgents is a customer communications platform built around one main idea: every communication should be generated and managed with more context than a static template workflow can provide. Instead of treating email, SMS, and calls as separate disconnected tools, TruAgents centers day-to-day work around:- shared contact and conversation context
- agents that generate or review communications
- campaigns that define outreach behavior
- a unified Communications workspace for operating live activity
- analytics and public reports for monitoring outcomes
Who this is for
- Prospective customers evaluating the product model
- New customers who need the mental model before setup
- Internal teammates explaining the product to customers
The high-level product flow
The core building blocks
Organization
Your organization is the top-level operating space for settings, teammates, contacts, campaigns, tags, and communications behavior.Contacts and data sources
Contacts can be imported manually or synced from supported systems. Segments and tags help organize and target the right audience.Agents
Agents define how AI-assisted writing and review behave in TruAgents. Writers and reviewers are the clearest user-facing agent types in the current product flow.Campaigns
Campaigns combine audience, channel, instructions, and agent behavior into an executable outreach workflow.Communications
Communications is the main operational surface. It is where teams review sent and received activity, inspect threads, and keep channel-specific work connected to one shared narrative.Analytics and public reports
Analytics helps teams track performance in-product. Public reports let teams create shareable links for reporting outside the authenticated app experience.How the pieces depend on each other
The easiest mistake is to read these building blocks as separate features. In practice, they depend on each other:- organization settings shape default behavior and access
- contacts and segments determine whether targeting is usable
- agents influence how campaigns generate and review work
- campaigns define intent, but runs and communications reveal actual behavior
- analytics makes more sense only after the earlier layers are healthy
The real operating loop
Once setup is complete, most teams should think in this loop:- maintain contacts, segments, and channel readiness
- configure agents and campaign definitions
- launch controlled runs
- review drafts and live communications
- adjust setup, content, or targeting based on what actually happened
- use analytics and reports to monitor the result over time
Where teams usually get confused
Saving something is not the same as being ready
A campaign, agent, or settings page can be filled out without the broader system being operationally ready.Communications explains more than campaigns alone
When a team asks “Why did this happen?”, the answer often lives in communication detail, run context, or contact quality rather than the campaign definition by itself.Setup problems often look like workflow problems
Email, SMS, permissions, and contact-data issues can all surface later as draft, campaign, or communications confusion.What to understand before going deeper
- TruAgents is organized around Communications as the long-term primary operating surface.
- Dedicated legacy channel pages may still exist in the app temporarily, but they are not the long-term primary product story.
- Contact quality, channel setup, and organization settings all affect how successful campaigns and communications workflows will be later.
- Analytics and public reports are related, but they are not the same thing. One is in-product analysis, and the other is controlled sharing.