Prompt

How do I add booking links and reminder emails to my app?

Technology / Scheduling & Booking Software2 observationsLast seen Nov 21, 2026

Latest observation

Nov 21, 2026OpenAI APIWeb search: off

To add booking links and reminder emails to your app, you usually need two pieces:

  1. A booking flow that creates an appointment and generates a unique link
  2. An email scheduler that sends reminders before the appointment

Here’s a practical way to build it.


1) Add booking links

A booking link is typically a URL that points to a page where a user can confirm, reschedule, or join an appointment.

Common pattern

  • Create an appointment in your database
  • Generate a unique token or ID
  • Build a link like:
https://yourapp.com/bookings/abc123

or, for meeting join links:

https://yourapp.com/meetings/abc123

What to store

In your appointments table/model, store:

  • id
  • user_id
  • start_time
  • end_time
  • status
  • booking_token or slug
  • email
  • created_at

Example flow

  1. User selects a time slot
  2. App creates appointment
  3. App generates a unique booking URL
  4. App shows or emails that link to the user

Example in pseudocode

const token = generateUniqueToken();
const appointment = await db.appointments.create({
  userId,
  startTime,
  endTime,
  bookingToken: token
});

const link = `https://yourapp.com/bookings/${token}`;

2) Add reminder emails

Reminder emails are usually sent automatically before the appointment time, such as:

  • 24 hours before
  • 1 hour before
  • 15 minutes before

You need:

  • An email service: SendGrid, Mailgun, Amazon SES, Postmark, Resend, etc.
  • A background job system: cron, queue, or scheduled worker

3) Use a background scheduler

You should not send reminder emails directly in the web request. Instead, schedule a job.

Options

  • Cron job: runs every minute and checks upcoming appointments
  • Job queue: enqueue a reminder job when the appointment is created
  • Cloud scheduler: e.g. AWS EventBridge, GCP Cloud Scheduler

Simple cron approach

Every minute:

  • Query appointments happening soon
  • Check whether reminder email has already been sent
  • Send if needed
  • Mark reminder as sent

Example logic

const upcoming = await db.appointments.findMany({
  where: {
    startTime: {
      gte: nowPlus24HoursMinusWindow,
      lte: nowPlus24HoursPlusWindow
    },
    reminderSent: false
  }
});

4) Email template example

Subject: Reminder for your upcoming appointment

Hi {{name}},

This is a reminder that your appointment is scheduled for
{{startTime}}.

Join or manage your booking here:
{{bookingLink}}

Thanks,
Your App

5) Recommended implementation approach

If your app is small

  • Generate booking links with a unique token
  • Use a cron job every minute
  • Send reminders with an email provider

If your app is larger

  • Use a queue like BullMQ, Celery, Sidekiq, or SQS
  • Schedule reminder jobs at creation time
  • Add retry logic and logging

6) Important considerations

Prevent duplicate reminders

Add fields like:

  • reminder_24h_sent_at
  • reminder_1h_sent_at

or a separate reminders table.

Time zones

Store times in UTC and convert for display. This avoids confusion.

Security

  • Use random, unguessable tokens
  • Expire links if needed
  • Verify the user before allowing changes

Deliverability

  • Set up SPF, DKIM, and DMARC for your email domain
  • Use a reputable email provider

7) Minimal architecture

  • Frontend: booking page and link display
  • Backend: create appointment + generate token
  • DB: store appointment and reminder status
  • Email service: send emails
  • Scheduler: send reminders at the right time

8) Example stack

If you’re using:

  • Node.js: Express + Prisma + BullMQ + SendGrid/Resend
  • Python: FastAPI/Django + Celery + SES/SendGrid
  • Ruby: Rails + ActiveJob + Sidekiq + Postmark

If you want, I can give you a step-by-step implementation for your specific stack, like React + Node, Next.js, Django, or Rails.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (2 observations for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.