> For the complete documentation index, see [llms.txt](https://www.blainecountysheriffoffice.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.blainecountysheriffoffice.org/sop/section-5-department-procedure/5.4-call-response.md).

# 5.4 - Call Response

In the event of an emergency call (defined later in this section), any unit may choose to respond to the call. Additional responding units may be called off by the first Officer on scene should they determine that either the emergency situation has been resolved or that no additional units would benefit the situation.

In the event that an Officer calls for “additional(s)”, the first unit to accept the call may respond code 2 (priority, lights without sirens) to the location of the Officer. Should the Officer calling for additional(s) stipulate that they require more than one unit in their call, additional Officer may respond until the required number of Officer is met.

In the event that an Officer calls for “assistance”, the first three units to respond may respond Code 3 (lights and sirens) to assist the Officer already on scene. In the event that an insufficient number of units respond to the call for assistance, Officer already on a routine call or traffic stops are required to drop their call to respond to the Officer in need of assistance until the required number of responding units is met or the Officer on scene or Officer in charge (OIC) of that scene determines that the completed response is adequate for the situation. In the event that an Officer calls for “backup” all units that are not already engaged on an emergency call are required to drop their active call, traffic stop or other duty and responding code 3 to the location of that Officer. Should the Officer who called for backup or the Officer in charge of that situation deem that the completed response is adequate for the situation, they may call off any units still responding.


---

# 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://www.blainecountysheriffoffice.org/sop/section-5-department-procedure/5.4-call-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.