Closing cases is important so that we have accurate records of our successes, failures and other cases.
For purposes of this SOP: - Dispatching rats is defined as dispatch telling them to go. It does not require them to be !assigned to a case in Mecha
- A successful Fuel Rescue is defined as following SOP, including debrief and ensuring the client can reach a scoopable star or station, except as noted below
- A successful non-Fuel Rescue is generally defined as jumponium or repair cases in which the client can continue on their previous activities.
|
Cases that should always be filed as Valid Cases
- If Rats are dispatched, Fuel or Non-Fuel Rescues (e.g. Jumponium, Emergency-repairs or Unstuck) should always be filed as valid cases.
- If a client is fueled or otherwise provided with jumponium, repairs or other help (i.e. Rescued) by Rat(s) file the case as a "Success".
- When a rescue does not occur because the client was able to rescue themselves (i.e. make it to a station, star, etc.), changed their mind, or became unresponsive, after Rats are dispatched, the case should be filed as "Other".
- If the client is destroyed due to a lack of fuel, after Rats are dispatched, the case should be filed as a "Failure".
- If the client is destroyed due to NPCs or player attacks, after Rats are dispatched and before a limpet or rescue is completed, the case should be filed as "Other".
- If the client is destroyed due to NPCs or players, after Rats are dispatched but after a limpet or rescue is completed, the case should be filed as "Success".
Cases that can be marked for deletion
Generally, cases where Rat(s) have not been dispatched can be marked for deletion using the command !md <case# or clientname> <reason> (see below for other related commands).
- PEBKAC - When a rat or other visitor mistakenly raises a ratsignal, or improperly uses the !inject or !grab commands.
- Duplicates - More than one case from the same client, usually caused by reconnecting using the IRC client in rescue mode, after the rescue has been cleared.
- Clients who change their mind (such as make it to a station or scoopable star, reboot/repair or otherwise save themselves even with help from us) - without dispatching rats to their case. If rats have been dispatched, it is a valid case (see above).
- Clients who immediately leave chat - Clients that start a rescue, but do not respond to our communications, or immediately leave IRC.
- Clients who have pushed the wrong button - i.e, their intent was just to chat with us, but they did not understand the green button, or want to see how the system works.
Cases that should NOT be deleted
Cases where Rat(s) have been dispatched should be filed and assigned a rescue outcome:
When to close inactive cases
Inactive cases should be closed and filed after they have exceeded the times below. In the event that the client returns after their case has been closed, a new case should be created.
- 15 minutes after a client leaves chat immediately.
- 1 hour after the client leaves chat mid-rescue.
- 24 hours after a LRR client fails to make a meeting time, and cannot be contacted.
Associated Commands
Command | Function |
---|
!md <case#/clientname> <reason> | Marks a case for deletion. Usable by any Rat. |
!delete <caseID> | Confirms that a case should be deleted from the database. NOT REVERTABLE. Use with care. Overseers+ |
!mdremove <caseID> | Removes a case from the Marked for Deletion list, returning it to the case pool, but not reopening it on the board. This means that paperwork will need to be filed for it. Overseers+ |
!mdlist | Lists cases marked for deletion. Overseers+ |
!invalid <caseID> | Marks an already closed case as "Invalid", this also removes it from Marked-for-deletion-list if applied. Usable by any Rat. |