dont4get
Request access

API first

One normalized appointment model for every source.

dont4get starts with direct platform integrations, then adds controlled email and SMS intake for systems that do not have a clean API yet.

POST /api/v1/appointments 
{
  "customer": {
    "firstName": "Sanne",
    "phoneNumber": "+31612345678"
  },
  "platformHolder": {
    "name": "Noord Amsterdam",
    "logoUrl": "https://noord.example/logo.png",
    "phoneNumber": "+31201234567",
    "email": "bookings@noord.example",
    "location": {
      "city": "Amsterdam",
      "countryCode": "NL",
      "geo": {
        "latitude": 52.3841,
        "longitude": 4.9042
      }
    }
  },
  "appointment": {
    "title": "Restaurant booking",
    "startAt": "2026-07-04T19:30:00+02:00",
    "status": "confirmed"
  }
}

Intake channels

API when possible. Smart intake when not.

API

Direct platform integration

Reservation and scheduling platforms send confirmed, changed and cancelled appointments directly to dont4get.

MAIL

Gmail, Outlook and Microsoft 365

Users can connect inboxes so appointment confirmations can be recognized without storing unrelated mail.

SMS

Inbox Mode and outbound updates

Appointment SMS messages can become reminders, and users can send important appointment updates back out.

Connector roadmap

Start with appointment-heavy markets.

Odoo Google Calendar Microsoft 365 Guestplan OpenTable Resengo Mindbody Virtuagym Eventbrite Calendly Square Appointments Custom OpenAPI

Technical requirements

Prepared for scale, privacy and auditability.

The platform holder is the appointment source. Every appointment needs source identifiers, status mapping and enough context for the recipient to act.