12 lines
1.0 KiB
HTML
12 lines
1.0 KiB
HTML
<p>Overnight lives fail for predictable reasons: sleepy operators, silent alerts, and nobody who can restart a frozen client. Coverage is a staffing problem first.</p>
|
|
<h2>Shifts, not heroics</h2>
|
|
<p>Four-hour blocks with a 15-minute overlap beat a single person “watching until morning.” Overlap exists so the incoming person sees a live handoff, not a dead laptop.</p>
|
|
<h2>Alert budget</h2>
|
|
<p>Night alerts should be rarer and louder. If the phone buzzes for every follow, it will be in another room by 3 a.m. Keep night rules to disconnects and high-value gifts.</p>
|
|
<h2>Physical setup</h2>
|
|
<p>Charger, headset, written restart steps, and a backup hotspot. The overnight kit is boring on purpose. Novelty gadgets are for daytime experiments.</p>
|
|
<h2>Health</h2>
|
|
<p>Do not schedule the same person for consecutive overnights as a default. Error rates climb. So do accidental bans.</p>
|
|
<h2>Morning recap</h2>
|
|
<p>The day team needs: disconnect count, top gifts, unresolved moderation, and whether the host is still live. They do not need a novel.</p>
|