Skip to main content

​
Summary

Contact management in TruAgents is not just a list-maintenance task. It is where teams verify whether the audience data behind campaigns and communications is actually usable. The current product flow suggests three distinct contact-management jobs:
  • reviewing the overall contacts list
  • inspecting and editing an individual contact record
  • looking at contact-specific communication history

​
Who this is for

  • Operators maintaining audience quality
  • Campaign managers validating target records
  • Teammates reviewing individual contacts before or after communications activity

​
Where to find it in the app

  • Contacts
  • Contact detail
  • Contact history

​
What the current contacts flow suggests

​
Contacts overview

The main contacts page appears to combine:
  • import actions
  • create-contact actions
  • list filtering and pagination
  • high-level contact metrics
That means this page should eventually guide users on when to start from the main contacts table versus when to jump into data sources or segments first.

​
Contact detail

The current contact detail flow suggests that a contact record can hold more than simple name and email fields. It can include:
  • core identity fields
  • contact data or structured data
  • activation state
  • unsubscribe preferences
  • tags
  • additional generated or profiler-related context in some cases

​
Contact history

The separate history view shows that contact management is connected directly to communications behavior. Users can review a contact’s thread history and filter it by channel.

​
A practical contact-management loop

  1. find the contact in the main list
  2. inspect the core identity and routing fields
  3. review tags, activation state, and communication preferences
  4. open contact history when communication context matters
  5. decide whether the fix belongs in the contact record, the source data, or the campaign logic

​
What to verify on an individual contact

The current contact detail flow suggests a contact can include:
  • core identity and routing fields
  • timezone and active state
  • unsubscribe preferences
  • tags
  • structured data
  • profiler-related context
That means a contact record can explain much more than “do we have an email address?”

​
When to start from contact history

Go to contact history when the real question is:
  • what has this person already received or sent
  • which channels have been involved
  • whether the latest communication fits the larger thread
Simple version: the contact overview explains the record, and contact history explains the relationship.

​
Common mistakes

  • blaming campaign logic before checking contact quality
  • ignoring unsubscribe or activation state
  • forgetting that tags and structured data can influence how a record is interpreted
  • treating contact history like a separate concern from contact cleanup

​
Success checklist

  • Contacts are easy to find and inspect from the main list.
  • Individual records contain the fields required for real outreach.
  • Teams know where to view a contact’s communications history.
  • Contact cleanup and enrichment can happen before campaign issues get blamed on the wrong part of the system.