# Team Chat

The **Team Chat** view provides a shared event communication room between judges and Race Control.

It is designed for operational coordination during race day.

<figure><img src="/files/1Br6w3iiCdlQzP2Y4BHw" alt="" width="360"><figcaption><p>Team Chat Screen</p></figcaption></figure>

## What Team Chat Does

Team Chat allows real-time messaging between:

* Judges using the Race App
* Race Control inside Race Manager

It is separate from Live Activity and maintains its own message feed.

## Chat Behavior

Team Chat:

* Polls periodically for updates
* Refreshes immediately when focused
* Updates instantly after sending a message
* Persists across judge logins using the same token

If a judge logs out and another logs in with the same token:

* Chat history remains available.

## Sending Messages

Messages should be:

* Short
* Clear
* Operational

Example:

* “First woman approaching finish.”
* “Bib 245 collapsed near km 3.”
* “Checkpoint water running low.”

Avoid long explanations. Use Race Alerts for formal reporting.

## Operational Best Practices

* Mention checkpoint context when multiple checkpoints are assigned.
* Use precise language (what / where / when).
* Keep communication concise.
* Do not rely on Chat for classification decisions — use Penalty & Bonus instead.

## Summary

Team Chat enables fast, informal coordination between judges and Race Control, complementing structured tools like Race Alerts and Penalty & Bonus.


---

# Agent Instructions: 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:

```
GET https://help.runonrufus.com/rufus-cloud/race-app/team-chat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.