Reservation SMS

Every confirmation, change, and reminder — sent automatically, from one dock or fifty.

The messaging layer the incumbents skipped: multi-dock routing, opt-in, no-show logic, reciprocity-aware, A2P 10DLC compliant.

The problem

What operators actually say.

  • Members show up without a boat because the confirmation never went out.

  • Dock staff send individual reminders by hand, or not at all.

  • Switching numbers and providers breaks member trust.

How it works

Three steps from install to live.

  1. Step 1

    Provision compliant numbers

    A2P 10DLC campaigns, per-dock numbers, consent flow.

  2. Step 2

    Connect your reservation source

    Salesforce + GoMeddo, Fareharbor, or any webhook-capable system.

  3. Step 3

    Tune the cadence

    Confirm on booking, remind 24h out, reconfirm 2h out, post-trip follow-up.

What's inside

Everything in Reservation SMS.

Multi-dock routing

The member hears from the dock they are going to, not a corporate number.

Opt-in and consent

Clean consent log, audit trail, and per-member unsubscribe.

No-show reminder logic

Confirms, nudges, and escalates in the last two hours of the reservation window.

Weather-aware

Automatic NOAA-triggered messaging when conditions change materially.

Member replies handled

Inbound replies route to Voice & Chat AI or to a dock manager's inbox.

The AI moment

The AI moment

Twilio A2P 10DLC campaign with multi-dock routing, member opt-in flow, no-show reminder logic, and NOAA-aware messaging. Responses are interpreted by the Voice & Chat AI model for consistent context.

Built on real operations

Proven at Freedom Boat Club Northeast Florida.

Across five FBC Northeast Florida docks, confirmation-to-show rate is the highest in the network since launch.

SOC 2 Type I in progress. AES-256 at rest, TLS 1.3 in transit. Customer data is never used to train foundation models.

See our security posture

See Reservation SMS on your fleet.