SMS sent within 60 seconds of booking confirmation if SMS is enabled

An SMS confirmation sent 10 minutes after booking is effectively useless — customers check their phone immediately after completing a transaction to verify it went through. A cron job polling every 5 minutes introduces an average 2.5-minute delay and a maximum 5-minute delay, which is long enough for customers to attempt a duplicate booking or contact support. CWE-391 and ISO 25010 reliability.fault-tolerance flag the missing retry path: a single synchronous SMS send with no retry means a carrier timeout silently voids the only channel some customers monitor. Event-driven dispatch removes the timing gap and the retry gap in one change.

Queue the SMS in the same confirmBooking() function as the status write, after checking opt-out status. Use the same job queue and retry settings as confirmation email:

// src/lib/bookings.ts
async function confirmBooking(bookingId: string) {
  const booking = await db.bookings.update(bookingId, { status: 'confirmed' })

  if (booking.customer_phone) {
    const isOptedOut = await checkOptOut(booking.customer_phone)
    if (!isOptedOut) {
      await smsQueue.add(
        'send-confirmation-sms',
        { bookingId, phoneNumber: booking.customer_phone },
        { attempts: 5, backoff: { type: 'exponential', delay: 2000 } }
      )
    }
  }
}

Remove any cron or polling job that handles SMS confirmation — the queue is the only dispatch path.