# Delayed Case Board and Command Usage

The ability to have a record of long-distance, extended-duration cases has been a consistent feature request for a long time now. In the past, this was accomplished with large pins in private Discords, isolated holding channels where case information was stored, or simply word of mouth from one Dispatcher to another until the case was resolved.

Thankfully, as of HalpyBOT version 1.2, this ability has been hard-coded into the bot with a series of commands that may come in handy for Dispatchers and Seals alike. This system is designed for instances where a case is not fully continuous, when a meetup has to be scheduled in the future, or simply when there will be a significant delay between a Client coming in and that Client receiving repairs.

#### Commands

The following are valid commands in HalpyBOT for Delayed Case Management:

<table border="1" id="bkmrk-command-format-what-" style="border-collapse: collapse; width: 100%; height: 291px;"><tbody><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">Command Format</td><td style="width: 33.3333%; height: 29px;">What it Does</td><td style="width: 33.3333%; height: 29px;">Who can Use It</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!delaystatus</td><td style="width: 33.3333%; height: 29px;">Checks the system for Delayed Cases</td><td style="width: 33.3333%; height: 29px;">Everyone</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!checkstatus</td><td style="width: 33.3333%; height: 29px;">Checks the system for Delayed Cases</td><td style="width: 33.3333%; height: 29px;">Everyone</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!delaycase \[case status\] \[notes\]</td><td style="width: 33.3333%; height: 29px;">Adds a new case to the Delayed system, and responds with a unique Case ID.</td><td style="width: 33.3333%; height: 29px;">Trained Seals</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!updatestatus \[case ID\] \[case status\]</td><td style="width: 33.3333%; height: 29px;">Updates the Status Code of a case - see the table of different status codes below!</td><td style="width: 33.3333%; height: 29px;">Trained Seals</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!updatenotes \[case ID\] \[new notes\]</td><td style="width: 33.3333%; height: 29px;">Updates the Notes attached to a case - this replaces the old notes entirely, so be sure to be complete in your new notes!</td><td style="width: 33.3333%; height: 29px;">Trained Seals</td></tr><tr style="height: 30px;"><td style="width: 33.3333%; height: 30px;">!updatecase \[case ID\] (case status) (case notes)</td><td style="width: 33.3333%; height: 30px;">Updates both the Status Code and Notes of a case - this replaces the old notes entirely, so be sure to be complete in your new notes!</td><td style="width: 33.3333%; height: 30px;">Trained Seals</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!endcase \[case ID\]</td><td style="width: 33.3333%; height: 29px;">Closes a case and removes it from the Delayed Case system.</td><td style="width: 33.3333%; height: 29px;">Trained Seals</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!close \[case ID\]</td><td style="width: 33.3333%; height: 29px;">Closes a case and removes it from the Delayed Case system. It's encouraged to update the notes before you close a case!</td><td style="width: 33.3333%; height: 29px;">Trained Seals</td></tr><tr style="height: 29px;"><td style="width: 33.3333%; height: 29px;">!reopen \[case ID\] \[case status\]</td><td style="width: 33.3333%; height: 29px;">Reopens a previously-closed case, if a case is improperly closed.</td><td style="width: 33.3333%; height: 29px;">Moderator+</td></tr></tbody></table>

#### Case Statuses

You might notice several command require a Case Status element. Here are the different statuses and what they mean:

<table border="1" id="bkmrk-case-status-what-it-" style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 50%;">Case Status</td><td style="width: 50%;">What it Means</td></tr><tr><td style="width: 50%;">1</td><td style="width: 50%;">This Case needs Seals!</td></tr><tr><td style="width: 50%;">2</td><td style="width: 50%;">This Case has Seals, and the Seals are en-route, OR the Seals are on station, and awaiting the Client for a scheduled meetup.</td></tr></tbody></table>

Although status 2 may have Seals assigned and en-route, check the notes. If you are significantly closer than the current assigned Seals, try and contact them and the current dispatcher to see if joining the case is appropriate.

#### The Notes Field

Notes should contain AT A MINIMUM this information:

- Client Name
- Client System
- Clent Platform
- Details about a Client's Situation
- Assigned Seals (If Any)
- Scheduled Meetup Time (If Set)
- Any and all information needed to ensure a successful repair

If a notes field is too vague or information is not known, the case may be closed or deleted by a Moderator.

#### Viewing Statuses

To check the status of Delayed Cases, you can either run the `!checkstatus` command, or view the board at [https://hullseals.space/dispatch-tools/delayed/](https://hullseals.space/dispatch-tools/delayed/). The board auto-refreshes every 5 minutes, and is a live-view of the status of the Delayed system.

#### Disclaimer

This system is not the long-sought-after "Dispatch Board", and cases are not automatically uploaded to the Delayted Case system. Just because the Delayed system doesn't have any ongoing cases does not mean there are none ongoing!