> For the complete documentation index, see [llms.txt](https://docs.insuraviews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insuraviews.com/getting-started/additional-tools/objection-response.md).

# Objection Response

Handle DOI reviewer objections efficiently with AI-powered response drafting.

**What it does:** Transform DOI objections into professional, well-supported response letters using comparable filing data and industry precedents.

**How to use:**

1. Navigate to "Objection Response"
2. **Input the Objection**: Copy and paste the DOI reviewer's objection text directly into the system, or upload objection documents directly
3. **Provide Additional Context**: Include additional context to the "copy and paste" section, and enter any relevant filters to narrow the scope of filings considered

<figure><img src="/files/pVHguIaOt6tpxP8AFwsq" alt=""><figcaption><p>Objection Response page</p></figcaption></figure>

4. **Review Analysis**: The system analyzes the objection type and identifies key concerns
5. **Generate Response:** After generating a response, a proposed response is generated in the Regulator Objection Response Workspace.&#x20;

<figure><img src="/files/005FGypFMMn7IJ3iSQJT" alt=""><figcaption><p>Regulator Objection Response Workspace with a draft for a short objection letter</p></figcaption></figure>

4. The **Regulator Objection Response Workspace** is where edits can be made to ensure that the content of the letter aligns with the desired tone and alignment with the objection.&#x20;
   1. Change the overall tone of the response by selecting one of the tone options near the Proposed Response header. By default, the tool will generate with a standard professional tone
   2. Each generated section, like the introduction or the actual objection responses, can be edited through the Section Controls, that appear when clicking on a section. Here, you can have the AI rewrite the section in a different way (Agree/Disagree or Clarification), or modify the section through supporting evidence and other simpler rewrites.&#x20;
   3. You can also edit the text directly in the response box, to add additional context or rewrite sections in your own words.&#x20;

<figure><img src="/files/fjAkVFrh9yZ1bB50Nesu" alt=""><figcaption><p>Screenshot of the Objection Response Workspace with the Tone options, Section Controls, and Export options highlighted</p></figcaption></figure>

5. **Finalize and Export:** Once the response has been finalized, the Export button provides two options:
   1. Export as Plain Text: perfect for copy/pasting into an email or other submission form
   2. Export as PDF: example below
   3. You can also bookmark an Objection Response session, which allows you to edit a completed response, or export the response.

<figure><img src="/files/EWdlMS9jELsj8wBZ6pPC" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**NOTE: All Filing Sources are included at the bottom of each Objection Response generated under 'View Filing References'**
{% endhint %}

**Key Benefits:**

* Saves hours of research time finding comparable cases
* Ensures consistent, professional tone in regulatory correspondence
* Leverages comprehensive database of successful responses
* Reduces back-and-forth with regulators through well-supported arguments


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.insuraviews.com/getting-started/additional-tools/objection-response.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.