Building a WhatsApp-First Booking Flow Without a Backend

2026-11-16来源 dev.to UXEnglish

Why WhatsApp

In Morocco, WhatsApp is the universal messaging app. Our guests are tourists arriving at Marrakech Menara airport, and they already have WhatsApp open. A traditional booking form with login, payment gateway, and confirmation emails adds friction. WhatsApp adds none.

The Implementation

Every "Book Now" button on our site is a pre-filled WhatsApp link. The helper function is straightforward:

export function whatsappHref(text: string) { return `https://wa.me/${site.whatsapp}?text=${encodeURIComponent(tagged(text))}`; } 

The tagged() wrapper prepends a source tag so the office knows which site the message came from (we operate multiple domains):

const SOURCE_TAG = `[navetteforyou.com \u00b7 Marrakech Transport]`; const tagged = (s: string) => s.startsWith(SOURCE_TAG) ? s : `${SOURCE_TAG}\n${s}`; 

Pre-Filling the Message

Each route page composes a booking message with the transfer details already filled in: route, date placeholder, number of passengers, vehicle class, and quoted price. When the guest taps the button, WhatsApp opens with a message like:

[navetteforyou.com \u00b7 Marrakech Transport] Transfer: Marrakech Airport \u2192 Medina Vehicle: Mercedes E-Class (3 pax) Price: 300 MAD Date: [your arrival date] Flight: [your flight number] 

The guest fills in two blanks and hits send. The office responds within minutes.

Email Fallback

For guests who prefer email, we use the same pattern with mailto: links:

export function mailHref(subject: string, body: string) { const subj = `[navetteforyou.com] ${subject}`; return `mailto:${site.email}?subject=${encodeURIComponent(subj)}&body=${encodeURIComponent(tagged(body))}`; } 

Zero Backend

There is no server, no database, no payment processing. The entire booking flow is a static site generating deep links into WhatsApp and email. The operator's office handles confirmations, payments (cash or bank transfer), and driver dispatch. This architecture costs nothing to run and has zero downtime risk.

Tradeoffs

The obvious gap: no automated scheduling, no calendar integration, no payment capture. For a small transfer operator handling 10-30 bookings per day, a WhatsApp thread with context is faster than any dashboard. At scale, you would add a backend. We are not at that scale, and premature infrastructure is a cost, not a feature.

Operated by Serenity Morocco Tours. Visit navetteforyou.com or WhatsApp +212 701 664 704.

原文:https://www.a8q9.cn/en/article/building-a-whatsapp-first-booking-flow-without-a-backend-6d9c69.html

相关文章