# The booking request that landed in a screen nobody opened: a notify pattern for service businesses

**URL:** <https://community.glideapps.com/t/the-booking-request-that-landed-in-a-screen-nobody-opened-a-notify-pattern-for-service-businesses/87820>\
**Category:** General\
**Created:** [October 28, 2026, 11:31am UTC](https://community.glideapps.com/t/the-booking-request-that-landed-in-a-screen-nobody-opened-a-notify-pattern-for-service-businesses/87820 "2026-10-28T11:31:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Huzaifa](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/huzaifa/32/96353_2.png) [@Huzaifa](https://community.glideapps.com/u/Huzaifa)\
**Post date:** [October 28, 2026, 11:31am UTC](https://community.glideapps.com/t/the-booking-request-that-landed-in-a-screen-nobody-opened-a-notify-pattern-for-service-businesses/87820/1 "2026-10-28T11:31:25Z")

</div>

A lot of Glide apps for local services (HVAC, clinics, cleaning) have a clean “Request a visit” form. The row appears in the Requests table, and then nothing happens. The owner is on a job, the office phone is ringing, and the new row sits unread until evening.

Here’s the pattern I use, with native Glide actions where possible:

1. The form writes one row: Name, Phone (digits only), Issue, Preferred window, Status = New, Created = now.
2. On submit, an action notifies the on-duty person right away by email or push, whichever that shop already checks. Keep the message short: “New request: Jane, AC not cooling, wants today. Open Requests.”
3. Status is a single choice the owner can change from their phone: New, Called, Booked, No answer or Spam.
4. A second, delayed path: if Status is still New after 15 minutes during business hours, notify a backup person. Outside hours, skip the ping and put the row at the top of a “Call first thing” list.
5. Deduplicate: before creating a row, look up the phone number in the last 30 minutes. If it’s there, bump a “Calls” counter on that row and notify once more (“called again, urgent”) instead of creating three identical requests.

What makes it stick is that changing Status has to be one tap on the phone. If the owner needs a laptop, the escalation fires for jobs that were already handled.

Question for builders here: for the 15-minute “still New” check, do you use a scheduled workflow, or is there something simpler in Glide I’m missing?