Appearance
Product map
Where things live and what talks to what.
The three places EMS happens
┌──────────────────────────────────────┐
│ THE DASHBOARD │
│ where vendors work │
│ │
│ Experiences · Rates · Add-ons │
│ Availability · Bookings · Payments │
│ Guest forms · Partners · Settings │
└───────────────┬──────────────────────┘
│ publishes to
┌───────────────┼───────────────┐
↓ ↓ ↓
┌───────────────┐ ┌───────────┐ ┌──────────────┐
│ BOOKING PAGE │ │ HOTEL │ │ MARKETPLACE │
│ the vendor's │ │ PARTNER │ │ e.g. Get │
│ own public │ │ sells to │ │ Your Guide │
│ site │ │ its guests│ │ │
└───────┬───────┘ └─────┬─────┘ └──────┬───────┘
│ │ │
└───────────────┴──────────────┘
↓
Bookings and payments
land back in the dashboardWhat the dashboard contains
| Section | What is in it |
|---|---|
| Bookings | The booking list, requests, channels, guest forms, promotions, tasks |
| Experiences | The experience list, categories, add-ons |
| Settings | Account and company, staff accounts, payment, payment windows, policies, integrations, booking page appearance |
Who does what
| Who | Where they work |
|---|---|
| Vendor | The dashboard |
| Guest | The booking page, or a hotel's own site |
| Hotel partner | Their own system, which talks to EMS |
| Marketplace | Their own site, which talks to EMS |
| Delta | Support, setup, and building it |
What sits behind it
A service holding all the rules and data, a payment provider for cards, a separate system for property and rooms that EMS partners with, and a shared library of definitions used by both.
Next
Follow one booking, the same picture, but as a story.