Your stack, discovered first.
The systems named here are ones you can connect, and each is scoped on request: it starts with a paid discovery week on your workflow, is built on the platform’s outbound webhooks and Partner API, and is switched on only after it has passed a test on your data. Integration work is priced separately from your licence.
- Scoped on requestevery named system, after discovery
- A paid discovery weekbilled separately from your licence
- Built on the platformoutbound webhooks and the Partner API
Systems you can connect, by category
Named systems only, each with its status. No logos, and no partnerships we do not have. Each one is built for you after discovery, not switched on from a list, and the chip on every card says so.
Supplier systems
Scoped to send contract data, stop-sales and quotes where your suppliers’ systems expect them.
Safari Portal
Would send structured quote data into Safari Portal in the format it expects, so agents can paste quotes directly.
Scoped on requestSejour
Would push parsed contract data and stop-sale updates into Sejour for UAE properties.
Scoped on request
Tour operator systems
Scoped to move contract and booking data between your tour operator system and your inventory.
Tour Plan
Would let contract and booking data flow between Tour Plan and the platform.
Scoped on request
CRM
Scoped to create deals, sync quote status and log emails against the right record.
Pipedrive
Would create deals in Pipedrive, sync quote status and log emails against the right deal record.
Scoped on request
Rates and inventory
Scoped to set live rates beside the rates you have contracted.
Sabre
Would bring live hotel rates from Sabre for selected properties into your quotes, beside your contracted rates.
Scoped on request
Channels
Built-in notification channels, alongside email and SMS: your numbers and your senders, per event, with your templates.
WhatsApp Business
Notifications and status updates over WhatsApp from your own WhatsApp Business number, per event, with your templates.
IncludedTelegram
The same notifications over Telegram, for markets where WhatsApp is restricted or less used.
Included
Included means part of the core platform in every plan: the WhatsApp and Telegram notification channels, set up with your own numbers. Scoped on request means delivered as a custom connection after a paid discovery week, built and tested on your data before it is switched on. What you connect with today is in the core platform, included in every plan: outbound webhooks and the Partner API.
Your contract rate beside live rates, scoped with you
Your search already prices every stay from the contracts you approved. A multi-source comparison, setting those rates beside the GDS and bed-bank aggregators so you can pick the best option for the booking in front of you, is a connection scoped on request.
- 1Your contracts
Rates read from the contracts you have loaded and approved, in every plan.
- 2Sabre hotel rates
Real-time availability and pricing for selected luxury portal properties, scoped on request.
- 3Bed-bank aggregators
Aggregated rates from the bed banks you work with, connected only after discovery.
Scoped on request
Connections we scope with you
The named systems are where most conversations start. Anything else is scoped the same way: an option on top of the product, scoped in a discovery week, quoted openly, then built on the platform. Data migration and custom development follow the same route.
Back office and finance
Bookings, invoices and commissions flowing into the ledger you already run.
Scoped on requestOther CRMs
The CRM your team already works in, with deals and quote status kept in step with your proposals.
Scoped on requestOther reservation systems
Contract and booking data exchanged with the reservation system your operation runs on.
Scoped on requestBed banks
Bed-bank aggregators set beside your own contracts, in a rate comparison scoped with you.
Scoped on requestWhat you connect with today
Two pieces of the core platform are there for other systems to use, included in every plan. Every scoped connection is built on them, so it stays maintained as the platform moves.
- 1Outbound webhooks
Real events, such as contract approved, booking confirmed or inventory synced, pushed to an endpoint you choose as they happen. Deliveries are signed and retried, and you can send a test and inspect every attempt.
- 2The Partner API
Your trade partners get secure access to search, quote and book against your inventory at sell prices only, with documentation generated from the API itself. See the Partner API.
- 3A shared reference-data layer
Amenities, meal plans, property types, hotel chains, countries and destinations stay consistent across every contract, so a mapped field means the same thing everywhere.
(opens the full-size screenshot in a new tab)
(opens the full-size screenshot in a new tab)Integrations are scoped, not included.
The product covers what it does on its own. Connecting your CRM, back office, supplier systems or inventory sources is separate work on a separate bill, it is scoped on request, and it starts with a paid discovery week. We would rather say that here than halfway through an implementation.
What the week gives you
- 1Feasibility, answered
We read your vendor’s API, confirm what it actually exposes, and tell you what is possible, what is not, and where a workaround costs more than the thing is worth. The honest no is part of the deliverable.
- 2An implementation cost you can budget
A written number for the build, based on the events and fields we mapped together, not a range invented on a call.
- 3A roadmap with an order to it
What gets built first, what depends on what, and which parts you can defer to a second phase without blocking go-live.
- 4If the answer is no, you find out in a week
You will have spent a week, not a build budget. The write-up is yours either way, including the reasons it did not work.
A paid discovery week
One week to start. It extends only when the requirement genuinely needs it, agreed with you before the week runs out, and never as a surprise on an invoice.
- Separate from your licence. Nothing about your monthly licence changes whether you run a discovery or not. See how the licence is priced.
- Separate from implementation. Discovery buys the answer. The build is quoted at the end of it, and you decide then.
- What it depends on. The number of systems, what your vendor’s API exposes, and how much of your field mapping already exists.
Indicative, subject to order form. Implementation, migration and custom development are quoted separately after discovery.
How an integration gets ready
Six steps, each with a named owner on both sides. Nothing is announced as available until it has passed step five on your data.
Step 1: Discover
A working session on your workflow: which system, which events, which fields, who touches them. We leave with a written scope, not a slide. This is the paid discovery week; everything after it is quoted at the end of it.
- Event list
- e.g. quote sent, booking confirmed, contract approved
- Field map
- your fields against platform reference data
- Named owners
- one on your side, one on ours
Step 2: Evaluate the API
We read the vendor’s documentation and confirm what it can and cannot do before anything is promised. Gaps are written down, with the workaround or the honest no.
- Capability matrix
- read, write, webhook, rate limits
- Gap list
- what the vendor cannot expose today
- Go / no-go
- agreed before scope is signed
Step 3: Access
Sandbox credentials, scopes and data-protection sign-off arranged with your vendor and your IT. Least privilege by default.
- Sandbox credentials
- scoped to the events in step 1
- DPA sign-off
- your legal and ours
- Audit entry
- who granted what, when
Step 4: Build out
Mapped, built on the platform’s webhooks and reference data, and reviewed with you at each milestone. No custom code in your systems.
- Webhook subscriptions
- configured from Settings
- Field transforms
- currencies, dates, IDs normalised
- Milestone reviews
- you see it working before step 5
Step 5: Test on your data
Run against your real records in a sandbox. You sign off on the results, not on a demo. Failures are listed with cause and fix.
- Test log
- every record, pass or fail, with reason
- Your sign-off
- ops lead and IT, by name
- Rollback plan
- written before go-live
Step 6: Deploy and monitor
Switched on in your environment with monitoring and a delivery log, then maintained with the platform. Retries and failure alerts are on from day one.
- Delivery log
- every event, every retry
- Alerting
- to your channel of choice
- Maintained
- updated with the platform, not as a one-off
Where the connected data comes from
- Contract intelligenceThe contract data and stop-sales a connection would carry onward start as contracts read, scored and approved.
- Partner APIYour trade partners search, quote and book against your inventory at sell prices, through secure partner access.
- PlatformOutbound webhooks and the shared reference data every scoped connection is built on.
Start with the discovery week
You leave with a written scope your IT can review, a build cost and a timeline. If it cannot be done, you get that in writing instead.