Overview

The Appointments Requests tab is the single ledger of every appointment, termination, renewal, and line-of-authority change request your team has filed with NIPR through Turris, so you can watch each request move from Pending to Completed and step in the moment one fails or stalls.

What is the Appointments Requests Tab?

The Appointments Requests tab is the request-history view inside the Appointments section. Where the other Appointments tabs show status (who is appointed today, who still needs action), this tab shows work in flight: one row per change request submitted against an agency or an agent, with the product, state, lines of authority, current status, and any processing notes NIPR returned.

Who uses it. MGA and carrier licensing teams, appointment coordinators, and compliance operators who own the day-to-day work of getting agencies and agents appointed and keeping those appointments current. It is the screen they open when someone asks "did that appointment go through?" or "why did this renewal fail?"

Here you can:

See every request in any status (Pending, Submitting, Submitted, Completed, Failed, Submission Failed, Canceled, Archived) in one table, without opening individual agency or agent records.
Track agency-level and agent-level requests side by side, with a Category column under the Entity group that labels each row Agency or Agent.
Cover all four request kinds in one place: Appointment, Termination, Renewal, and Loa Change.
Narrow the table to a specific carrier product, distributing agency, or producer using the filter bar at the top.
Read the Processing Notes NIPR returned during eligibility, fee, or submission processing without opening a separate detail view.
Cancel a request that is still in Pending status before it leaves Turris for NIPR.
Bookmark or share a filtered view, since your filter selections are saved in the page URL.

Accessing the Appointments Requests Tab

Open Left sidebar → Appointments. The Appointments page loads with the Actions Required tab selected by default.
Click the Appointments Requests tab in the sub-navigation at the top of the page. The sub-navigation also exposes Actions Required, Agencies, and Agents.

What's visible on the page

Element	Description
Filter bar	A bordered panel at the top of the page with three multi-select dropdowns: Product, Agencies, and Agents. Each has a Select All option, and your selection is saved in the page URL.
Requests table	One row per change request, paginated, with sortable column headers.
Empty state	A centered message. When nothing has been submitted, the title reads No data available with the text You have not made any appointments requests yet. When filters are active but return zero rows, the title reads No matching requests with the text No appointments requests match the selected filters.

The table groups its first two columns under an Entity header. Columns, left to right:

Column	Description
Category (under Entity)	The kind of entity the request was filed for, shown as a gray Agency or Agent badge.
Name (under Entity)	The agency's legal name, or the agent's first and last name. Shows a dash when no name is on file.
Product	The carrier product the request is tied to. Shows a dash when no product is linked.
State	The US state or territory the request was filed for, shown as a state circle (the USPS code in a colored badge).
LOA	The lines of authority included in the request, each as a `Name (code)` badge. When more than three are included, the first two show inline and the rest open behind a +N button (see Visual and Status Elements).
Processing Notes	Notes NIPR returned during submission and processing, shown as a bulleted list. Shows a dash when NIPR has returned no notes for the row.
Category (request type)	The type of request, shown as a blue badge: Appointment, Termination, Renewal, or Loa Change.
Status	The current request status, shown as a color-coded badge (see Visual and Status Elements).
Actions	A three-dot button at the end of the row containing Cancel Request. This column appears only for users with the appointment-management delete permission, and Cancel Request is disabled on any row that is not in Pending status.

Rows are listed newest first (by the date the request was created). There is no separate detail page; everything about a request is shown inline on its row.

Note: Rows in Failed status are dimmed (shown at reduced opacity on a raised background) so they stand out from in-flight and completed rows during triage.

Filtering by Product, Agency, or Agent

When you'd do this. The table is too long to scan and you only care about a slice of it: appointments tied to one carrier product, every request for a single agency you are triaging, or every request filed for a specific agent across all of their states.

Locate the filter bar at the top of the page.
Pick one or more values from the dropdowns. Each is a multi-select combobox, sorted alphabetically, with a Select All option:

Filter	Required	Description
Product	No	The carrier products configured on your account. Example values: `Auto`, `Commercial Property`, or any custom product name. By default every product is selected, so all requests show.
Agencies	No	The distributing agencies on your book. Example values: `Acme Insurance Services`, `Coastal Brokers`.
Agents	No	The producers on your book. Example values: `Jane Doe`, `John Smith`.

The table reloads as you change the selection and resets to the first page. Your selections are saved in the page URL, so the view can be bookmarked or shared.
To clear a filter, reopen the dropdown and unselect the values (or click Select All again when everything was already selected).

Tip: Once your daily triage filters are dialed in, bookmark the page. Because the selections live in the URL, opening the bookmark restores the same view without re-entering anything.

Sorting the Table

Click a sortable column header to sort by it; click the same header again to reverse the order. The default order is newest request first.

Sortable column	What it does
Category (under Entity)	Groups all Agency rows together and all Agent rows together.
State	Orders rows by state code.
Category (request type)	Groups requests of the same type, such as all Appointments or all Terminations.
Status	Groups all Pending, all Failed, and so on together. This is the fastest way to pull every failure to the top.

The Name, Product, LOA, and Processing Notes columns are not sortable.

Note: This tab has no free-text search box. Use the Product, Agencies, and Agents filters to narrow the list. A filtered view can also be reached directly by URL, for example a saved link that opens only the Failed requests.

Cancelling a Pending Request

When you'd do this. Someone filed the wrong appointment, picked the wrong state, or duplicated a request, and you need to stop it before it reaches NIPR. Cancellation works only while the request is still in Pending status; once it has been submitted, NIPR controls its lifecycle.

Find the row you want to cancel and confirm the Status column shows Pending. Cancel Request is disabled on every other status.
Click the three-dot Actions button at the end of the row.
Click Cancel Request.
A warning dialog appears: Are you sure you want to cancel this request? Click Apply to confirm, or Cancel to dismiss the dialog and leave the request in place.
The table refreshes and the request shows as Canceled.

If the request is no longer in Pending when you click Cancel Request, an information dialog appears with the heading Request cannot be cancelled and the message This request is not in pending state, you cannot cancel it. No change is made to the row.

Warning: Only Pending requests can be cancelled. Once a request moves to Submitting or Submitted, it has been handed off to NIPR and must run its course. If a submitted request later completes and the change still needs to be undone, file a Termination request from the originating workflow instead.

Note: The Cancel Request action requires the appointment-management delete permission. Read-only roles do not see the Actions column at all. Ask an administrator to grant the permission if you should be able to cancel requests.

Visual and Status Elements

Request status badges. The Status column shows each value as a color-coded badge:

Color	Label	Meaning	What to do about it
Yellow	Pending	The request has been created in Turris but not yet submitted to NIPR.	This is your last chance to intervene. Open the row's Actions menu and click Cancel Request if it was filed in error; otherwise leave it to submit.
Gray	Submitting	The request is being submitted to NIPR right now.	No action needed. Refresh in a few minutes and the row should move to Submitted.
Blue	Submitted	NIPR has accepted the request and is processing it.	No action available from this tab. Wait for NIPR to confirm; the row will move to Completed or Failed.
Green	Completed	NIPR confirmed the change was processed successfully.	The appointment, termination, renewal, or LOA change is now reflected in NIPR. No follow-up required.
Red	Failed	The request failed during eligibility or fee processing. The row is dimmed.	Read the Processing Notes column for the NIPR-side reason. Common causes: the agent or agency is not licensed in the state, the carrier is not authorized for the requested LOA, or a prerequisite is missing. Fix the underlying issue and re-file from the originating workflow.
Gray	Submission Failed	The submission to NIPR's gateway failed after every retry.	The request never reached NIPR's processing pipeline. Re-file from the originating workflow, and contact support if it keeps failing.
Gray	Canceled	The request was cancelled, by a user from this tab or by the system.	No action needed. File a new request if the underlying need still applies.
Gray	Archived	The request has been archived and is kept for historical reference only.	Read-only; no further action available.

Request type badges. The Category column (request type) shows each value as a blue badge:

Label	Meaning
Appointment	A request to create a new appointment for the entity in the selected state.
Termination	A request to terminate an existing appointment in the selected state.
Renewal	A request to renew an appointment that is expiring or has expired.
Loa Change	A request to change the lines of authority on an existing appointment.

LOA overflow. When a request includes more than three lines of authority, the first two show inline as gray badges and a +N button holds the rest. Click +N to open a small popover listing the remaining lines of authority.

Frequently Asked Questions

What is the difference between the Appointments Requests tab and the Actions Required tab? Appointments Requests is the history of every change request your team has filed, in any status. Actions Required is the forward-looking worklist of agency, agent, state, and product combinations that still need a request filed. One tab tracks what has already been submitted; the other tells you what still needs to be submitted.

Why can't I cancel a submitted request? Once a request leaves Pending, it has been handed to NIPR and Turris no longer controls its lifecycle. If you need a submitted request reversed, wait for it to complete and then file a Termination request to undo the change.

Why is a request in Failed status? A request fails when NIPR rejects it during eligibility or fee processing. Common reasons: the agent or agency is not licensed in the state, the carrier is not authorized for the requested LOA, or a prerequisite is missing. The Processing Notes column on the row usually contains the NIPR-side explanation.

Why don't I see the same request listed for both an agent and an agency? Each request is filed against a single entity, either an agent or an agency, and the Category column under Entity tells you which. To review the same coverage from the other side, switch the Agencies or Agents filter.

Where does the Processing Notes content come from? Processing Notes are the responses NIPR returns during submission and processing. Turris stores them on the request and shows them inline so you don't have to open a separate view to understand a hold or failure.

Why is the Actions column missing on my view? The Cancel Request action requires the appointment-management delete permission. If your role is read-only on appointment management, the Actions column is hidden entirely. Ask an administrator to grant the permission if you should be able to cancel requests.

Best Practices

Start each shift by sorting on Status. Click the Status header to group Pending rows together. They are the only requests you can still cancel, so catching mistakes there is the cheapest fix.
Triage Failed rows quickly. Filter by Product or Agencies to scope the work, then read the Processing Notes column to decide whether to re-file from the originating workflow or escalate to support.
Combine the Product and Agency filters. When working a specific carrier or distributing agency, layer the two filters to drop noise from unrelated requests.
Cross-check with Actions Required. If you see fewer requests here than expected, switch to Actions Required to confirm the missing requests have actually been filed.
Bookmark filtered views. Your product, agency, and agent selections all live in the URL. Save a bookmark to your most common view and reopen it for daily triage.
Treat Submitted as final. Once a request leaves Pending, plan as if it will complete. File a Termination request later if the change needs to be undone.

Appointments: Actions Required: A single prioritized worklist of every agency, agent, state, and product combination on your book where an appointment-related step is blocking compliant production.
Appointments: Agencies Tab: A grid showing, for every distributing agency on the book, whether it is fully appointed for each of your products, with drill-down into blocking states and bulk request tools.
Appointments: Agents Tab: The agent-by-agent view of your appointment book, with one product-status badge per carrier product and bulk appointment, cancellation, and termination tooling.