> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/contact-center-configuration/reusable-assets-routing-objects.md).

# Reusable assets & routing objects

Manage reusable content and classifications used across contact center routing.

Use these guides to manage content and objects that can be reused across callflows and dialogue handling:

## Audio assets

Start at [Audio assets](/contact-center-configuration/reusable-assets-routing-objects/audio-assets.md) for the audio navigation map. It brings together:

* [Manage audio assets and playlists](/contact-center-configuration/reusable-assets-routing-objects/audio-assets/manage-audio-assets-and-playlists.md)
* [Manage audio files](/contact-center-configuration/reusable-assets-routing-objects/audio-assets/manage-audio-files.md)
* [Where audio is referenced in call handling](/contact-center-configuration/reusable-assets-routing-objects/audio-assets/where-audio-is-referenced-in-call-handling.md)

## Other reusable objects

* [Manage canned responses](/contact-center-configuration/reusable-assets-routing-objects/manage-canned-responses.md)
* [Manage call classifications](/contact-center-configuration/reusable-assets-routing-objects/manage-call-classifications.md)

Review where an item is used before changing or removing it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/contact-center-configuration/reusable-assets-routing-objects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.