# Restaurant kiosks, updated by chat

> Canonical HTML: https://screenrig.ai/use-cases/restaurants/

Marco runs the kiosks for a 60-restaurant burger chain from his phone. One message to Meta Muse pulls a sold-out sandwich from every Denver kiosk, switches the idle promo and brings back screenshots.

[Set up your agent](https://screenrig.ai/docs/start/) · [Get a Demo](https://screenrig.ai/demo/)

<a id="watch"></a>

## Watch the restaurants film

- [Restaurant kiosks, 2:00 (MP4, 1080p)](https://screenrig.ai/videos/media/use-case-restaurants-1080.mp4)
- [Restaurant kiosks, 2:00 (MP4, 720p)](https://screenrig.ai/videos/media/use-case-restaurants-720.mp4)
- [English captions (WebVTT)](https://screenrig.ai/videos/media/use-case-restaurants.en.vtt)

A fictional 60-store burger chain with sample data, run from [Meta Muse](https://screenrig.ai/docs/start/muse/) on Android kiosks.

<a id="walk-through"></a>

## A restaurant self-order kiosk, run from a phone

The demo, scene by scene. Marco types one message, and every kiosk in the region changes while he watches the screenshots come back.

1. **Ordering when they’re here.** A portrait kiosk plays an idle shake promo. A customer taps and orders: burger, fries, “Add a shake?” When they walk away, the promo loop resumes.
2. **The old way.** The kiosk vendor’s console, a separate signage CMS, a 60-store spreadsheet, and a sold-out item edited kiosk by kiosk.
3. **One message.** In Muse, Marco types: “The spicy chicken sandwich is sold out in Denver until Friday. Pull it from the kiosks and switch the idle promo to the new shake.”
4. **Every kiosk changes, with proof.** The sandwich drops off the menu at eight Denver stores and the idle loop flips to the shake. Muse replies “Done, 8 Denver kiosks,” with three screenshots.

<a id="one-screen"></a>

## Ordering and idle-time promos on one kiosk

The ordering app and the restaurant’s promos live in one playlist. When nobody is ordering, the kiosk hands itself back to the promos.

5. **One playlist.** A tap brings up the ordering app, and an idle kiosk returns to the promo loop. Checkout stays in the restaurant’s own app.
6. **Dayparting in local time.** “From 6 to 10:30, run the breakfast promo, in each store’s local time.” Denver, Phoenix and Los Angeles each switch at their own 6:00.
7. **Checked on the glass.** At 6:02 in Denver, Marco asks “Is breakfast up?” Muse answers with a grid of screenshots, every kiosk on breakfast.

<a id="features"></a>

## QSR digital menu board and kiosk features

More of what a restaurant chain runs from its agent.

- **Daypart schedules in each store’s local time.** Breakfast, lunch and dinner switch on every store’s own clock.
- **Roll out to tagged stores in one request.** Tag a region once, then change every kiosk in it with one sentence.
- **Android kiosk lock mode.** The managed Android Player keeps the kiosk on your experience.
- **Touch events reach your agent.** A tap on the kiosk arrives as an event your agent can act on.
- **Cached media keeps playing offline.** Each kiosk keeps playing what it has when the network drops.
- **Screenshots from every kiosk.** Proof from one store or the whole chain.

<a id="next-steps"></a>

## Give your agent a screen

Install the official plugin, pair your first screen, and run it from the agent you already use.

- [Set up your agent](https://screenrig.ai/docs/start/)
- [Get a Demo](https://screenrig.ai/demo/)
- [All use cases](https://screenrig.ai/use-cases/)