“I can't work this shift”.

From the team's phone to the supervisor's inbox.

Part 15 of 17 · 1 min 18 s

See all seventeen

Transcript

What the narration says, word for word (translated from the Spanish voice-over).

In this video: what happens when someone on the team can't make a shift. Today that arrives by WhatsApp, at any hour, and lives in the supervisor's head until they remember to move it. When they forget, the shift goes uncovered and nobody finds out until the day itself.

The person raises it on the exact shift, from wherever they are. They can leave a reason, and Batuta makes something important clear to them: the shift is still theirs until the supervisor replies. It isn't automatic permission.

On the other side, the request lands in the supervisor's inbox, with the person, the date, the reason and the specific shift at stake. And with something a loose message never carries: the impact. Batuta tells them how many shifts it clashes with and how many of those are already published, meaning how many the team has already seen. The supervisor decides and replies from there. The person gets the answer, and it's on record who asked for what, when, and how it was resolved.

Want to see this with your own venue's shifts and staff? Write to us at usebatuta.com.

Recorded on a demo restaurant: invented names, no real person's data. There is no pilot running yet, so you will not see customer results here.

We're just getting started — and that works in your favor.

Our first customers work directly with the people building Batuta: we configure it with you, tune it to your operation, and your feedback shapes what comes next. We start with a hands-on pilot, and the price — simple, per location — is set together once it has proven its value.

Prefer email? hola@usebatuta.com