> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truagents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deprecations and legacy pages

> Track legacy navigation patterns and product surfaces that should not be treated as the long-term TruAgents model.

## Summary

This page exists so the docs can acknowledge route and navigation churn without teaching users the wrong long-term product story.

The most important rule is simple: if a route is legacy or transitional, the docs should explain where the product is heading instead of over-optimizing around yesterday's menu structure.

## Who this is for

Readers who need a fast lookup rather than a narrative guide.

## Current legacy or transitional patterns to watch

| Transitional or legacy surface                        | How to document it                                                                                                       |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Dedicated `emails` routes                             | Treat as implementation detail or transitional surface. Prefer the unified **Communications** story in user-facing docs. |
| Dedicated `messages` routes                           | Treat as transitional. Prefer **Communications** with channel-specific filtering or explanation.                         |
| Dedicated `calls` or `calls-old` patterns             | Acknowledge only where needed for historical context. Do not imply this is the long-term top-level model.                |
| Channel-specific menu groupings from older navigation | Use channel pages to explain differences, but keep the operating model unified.                                          |

## Stable documentation anchors

When routes or menu labels move, prefer these stable product concepts:

* **Communications** for day-to-day channel operations
* **Campaigns** for reusable outreach definitions and runs
* **Contacts** and **Data Sources** for audience and import workflows
* **Analytics** and **Public Reports** for reporting behavior
* **Settings** for account and infrastructure setup

## Documentation rule of thumb

If you have to choose between:

1. documenting the exact current route name
2. documenting the stable user mental model

prefer the stable user mental model unless the route name itself is critical to completing a task.

## Simple version

* old routes can exist for a while
* docs should still teach the future-facing product shape
* for TruAgents, that especially means keeping **Communications** central

## Related pages

* [Page map](/reference/page-map)
* [Channels and capabilities](/overview/channels-and-capabilities)
* [Omnichannel communications](/channels/omnichannel-communications)