Karaoke Staff & MC/DJ Payouts on LOOP

How LOOP handles it

Room-turn forecast writes tomorrow's roster. MCs are a separate payee class with per-shift commission (base + per-song-request tip). Kitchen and bar use standard F&B roster module.

The specific pains here

1. #1MC no-shows on Saturday leave rooms without hosts.

   How LOOP solves it: AI MC Reliability flags risk 24h ahead; back-up MC auto-offered.

2. #2Late-night surge burns cash if you overstaff early.

   How LOOP solves it: AI Roster shapes shifts to hourly demand — split-shift auto-suggested.

3. #3Tip pool between MCs and bar is contentious.

   How LOOP solves it: Digital Tip Ledger requires per-staff Zalo signature.

4. #4Room hosts double as service — hard to track hours.

   How LOOP solves it: Zalo clock-in with per-room task log.

The LOOP playbook

A repeatable, step-by-step operator workflow — copy it into your ops manual or run it as-is inside LOOP.

1. Step 1MC no-shows on Saturday leave rooms without hosts.

   Do: AI MC Reliability flags risk 24h ahead; back-up MC auto-offered.

2. Step 2Late-night surge burns cash if you overstaff early.

   Do: AI Roster shapes shifts to hourly demand — split-shift auto-suggested.

3. Step 3Tip pool between MCs and bar is contentious.

   Do: Digital Tip Ledger requires per-staff Zalo signature.

4. Step 4Room hosts double as service — hard to track hours.

   Do: Zalo clock-in with per-room task log.

Frequently asked