> ## Documentation Index
> Fetch the complete documentation index at: https://docs.needalert.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Use cases

> Examples of how different businesses use Need Alert.

"Waiting for something that hasn't happened yet" is a problem in every industry. Here are a few examples.

> [!TIP]
>
> Create an item when there's already demand: a customer asked for it, complained it sold out, or asked when it arrives. You're not guessing, you're answering a request that already happened.

## Retail and entertainment

> [card] Bakery
>
> QR code on the window: "cheese bread is out of the oven". Only people who subscribed to the cheese bread are notified, when the batch is ready. Use a **one-time alert**.

> [card] Cinema
>
> QR code on the "coming soon" poster: people subscribe before there's a date and are notified when ticket sales open.

> [card] Neighborhood store
>
> A QR code on the shelf of an out-of-stock product. You notify people when you restock.

> [card] Online store
>
> "Notify me when it's back" through a phone notification, instead of an email that lands in spam.

> [card] Ice cream shop
>
> One item per flavor: "let me know when you make it again".

> [card] Food truck
>
> A fixed QR code at your spot. You [schedule](https://docs.needalert.app/en/establishments/schedule-alerts.md) the alert for when you arrive.

## Restaurants

> [card] Buffet
>
> One item per dish that isn't always served. Subscribers are notified when it's on today's menu, and you see how many people want each dish.

> [card] Seasonal dish
>
> Customers are notified the day the dish is back on the menu.

## Healthcare

> [card] Clinics and practices
>
> One item per specialty: when a patient cancels, all subscribers are notified and the first to confirm with the clinic gets the slot.

> [card] Blood bank
>
> One item per blood type, with a **recurring alert**: donors subscribe once and are called whenever their type runs low.

> [!NOTE]
>
> When subscribing reveals health data (blood type, medical specialty), mark the item as **Requires consent for sensitive data**. People confirm an extra consent when subscribing. See [Items and QR codes](https://docs.needalert.app/en/establishments/items-and-qr-codes.md).

## Services with limited spots

* **Courses and gyms:** an alert when someone drops out of a full class.
* **Hair salons and barbershops:** an alert when a slot opens up after a cancellation.
* **Car repair shops:** "your car is ready for pickup".
* **Equipment rental:** an alert when a rented piece of equipment is returned.

## Automatic integrations

With the [API](https://docs.needalert.app/en/api/overview.md), your own system sends the alert (see the [integration walkthroughs](https://docs.needalert.app/en/api/use-cases.md) and the [first request](https://docs.needalert.app/en/api/first-request.md)):

* Your **ERP** notifies people when a SKU is back in stock.
* Your **clinic's booking system** notifies people when an appointment is cancelled.
* Your **delivery platform** notifies people when a restaurant starts taking orders again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.