Skip to main content

​
Summary

Omnichannel in TruAgents should not mean “every channel lives in its own disconnected workflow.” The stronger interpretation, based on both the product story and the current app direction, is:
  • campaigns can involve channel-aware communication strategy
  • users should review activity in a unified communications model
  • contact context should survive across channel boundaries
  • the operating surface should converge on Communications, not splinter into permanent separate silos

​
Who this is for

Teams planning how to use TruAgents across one or more communication channels.

​
Why this matters

Teams usually make one of two mistakes:
  1. they force every channel to behave the same way
  2. they treat every channel as a separate tool with no shared history
TruAgents should avoid both.

​
The right mental model

  • channels are different in behavior
  • customer context should still be unified
  • campaigns and reporting should still connect the story across channels
  • operators should have one place to review what is happening

​
What omnichannel should look like in practice

An omnichannel workflow is working well when a teammate can:
  • understand the contact context without hopping through disconnected channel silos
  • review communications from multiple channels in one operating flow
  • connect an individual communication back to a campaign or run
  • reason about replies and follow-up without losing the earlier story
Simple version: different channels, one customer story.

​
What should stay channel-specific

Omnichannel does not mean every channel becomes identical. The following still vary by channel:
  • setup and infrastructure requirements
  • message format and length expectations
  • delivery constraints
  • how quickly a response loop tends to happen

​
What should stay unified

The following should still converge:
  • communications review
  • thread context
  • campaign reasoning
  • reporting and operational understanding

​
Common misunderstandings to avoid

  • omnichannel does not mean “blast every channel at once”
  • omnichannel does not mean “hide all channel differences”
  • separate setup pages do not imply separate long-term product silos
  • a unified communications view is more useful than three disconnected inbox mental models

​
What this means for documentation

Dedicated pages for email, SMS, and calls are useful, but they should explain channel-specific differences without suggesting that the long-term product is organized as disconnected channel products.