Skip to main content

Summary

TruAgents is designed to support customer communications across multiple channels without forcing teams to think about each channel as a separate disconnected system. At a high level, the current product story is:
  • Email for rich, context-heavy outbound communication
  • SMS for short, direct interactions
  • Calls for voice-based communication and richer live context
  • Communications as the long-term unified operating surface that ties those channels together

Who this is for

Prospective customers, new customers, and teammates who need the big-picture story.

Channel summary

The key idea

The app may still contain some channel-specific routes today, but the long-term product story should not be “three separate inboxes.” It should be one communications system with channel-specific behaviors.

What changes by channel

The channels share a common operating model, but they do not share identical setup or review requirements.

What stays shared

Across channels, the product is still trying to unify:
  • campaign definition
  • audience targeting
  • communications review
  • reporting
  • thread context over time
Simple version: the channel changes the execution details, but not the idea that your team is operating one communications system.

How to choose the first channel

If a team is starting from scratch:
  • choose email when message richness and approval discipline matter most
  • choose SMS when speed and brevity matter most
  • choose calls when live conversation quality is central to the workflow
The wrong move is choosing a channel only because it sounds easiest without checking setup and operational readiness.

What to understand before going deeper

  • Channel setup is still operationally different by channel.
  • Campaigns and communications should still be understood through one shared operating model.
  • Reporting and thread context become more useful when teams stop treating channels as isolated tools.

Common misunderstandings to avoid

  • Channel-specific routes do not mean the product should be thought of as separate products.
  • A team can be ready in one channel and not ready in another.
  • Choosing a channel is not just a content decision; it is also a setup and operations decision.