> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/circulation-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/circulation-user-manual/customer-service/viewing-customer-information/miscellaneous.md).
# Miscellaneous
The Miscellaneous tab is a composite of six different categories of information, which are described below.
## Tax Authority
A tax authority is a geographical tax area, such as “MN” for Minnesota state taxes. If a tax authority is set up in a city, county, state, and/or country in which the subscriber resides, that tax will be applied to the cost of the subscription, unless an exemption is entered. Tax authorities and exemption reason codes must be defined in Setup. The Tax Authority panel shows tax authorities and the tax exemption reasons (if any) that apply to a subscriber. Tax exemptions are entered during new starts and billing changes.
## Recent Transactions
This panel displays the last start, restart, and complaint for this subscription. The start and restarts are listed with their source and reason codes. The complaint is listed with its complaint code, and the total number of complaints called in for this subscription is shown.
## TM Products Delivered
This tab lists of all Targeted Marketing (TM) products delivered to this address. TM products can include grocery store flyers, shoppers, and other commercial items. A TM product is delivered only to certain addresses, targeted by the product’s selection criteria. The selection criteria might include Zip, demographic answers, publication received, or other variables.
## Inserts Delivered
If you have InsertPlus, a list of all inserts delivered to this customer, along with the delivery date, is displayed. If the insert has a version, the version also displays. The Runout column indicates whether the customer is in a runout zone for this insert (if the zone is a runout, the customer may or may not have received the insert in their paper). Burt Route Code 1 and Code 2 will display only if used in conjunction with the Burt Export and for sites that export alternate information. These fields will be suppressed for a subscriber who does not have inserts that utilize the Burt codes.
Only inserts for the current publishing date or earlier will be shown. A Business Rule in the InsertPlus section determines the number of days that are initially displayed. Click Selection to change the product or date range (inserts can be viewed for both publications and TM products).
## Tax Impact
The Tax Impact query displays the tax on all relevant subscriber transactions, including payments and auto renews, within a date range. This option will be available only if the subscriber has had a payment or other transaction taxed. Click Selection to specify the date range, then click OK. The transactions that were taxed will appear.
## Authentication Logins
This tab displays a list of iServices authentication logins for the subscriber within the last 30 days. A Selection button is available to modify the date range for which the user’s logins are listed.
## Communication History
Communication history reflects the newsletters or alerts that have already been sent to customers. For example, a customer might call because they have not received their “Sports” newsletter. You can check the customer’s communication history to determine if the communication should have been sent. Initially history for the current date and past 30 days displays. You can change the date range by clicking the Selection button.
---
# 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://docs.navigaglobal.com/circulation-user-manual/customer-service/viewing-customer-information/miscellaneous.md?ask=&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.
