Platform/How Tripdocks is built
Engineered for the whole trip.
One platform on AWS carries every enquiry, quote, booking and payment for the agencies that run on it, with each agency’s data kept to that agency.
One record per tripEnquiry, quote, booking, trip and invoice all live on the same record, so nothing is re-typed between teams.
Each agency on its ownEvery request is tied to the agency that signed in, and only ever reaches that agency’s data.
Every channel, one pipelineWhatsApp, ad forms and website enquiries pass the same checks before they reach your Queue.
Live for the whole teamA new lead, a paid installment or an incident shows up on every screen as it happens.
EWEmma Walsh · Swiss AlpsOne record
EnquiryWhatsApp · matched to the lead
DoneQuoteLuxury option chosen in the Client Portal
DoneReservation6 bookings with their suppliers
DoneTripDay 2 of 8, nothing open
LiveInvoice2 of 3 installments paid
Open[01] Architecture/ Six layers · one platform
Six layers, one platform.
Every channel, module and background job runs through the same API under the same agency rules, so a WhatsApp enquiry and an accounting entry get the same guarantees.
L1ChannelsWhere enquiries and clients come in
WhatsApp BusinessMeta lead adsWebhooksEmailClient Portal
L2One APIThe web app and every integration use it
Secure sign-inAgency scopingRole permissionsSame rules for every screen
L3Product modulesOne record per trip
LeadsDistributionQuotesReservationsOperationsClient PortalAccountingB2BDashboard
AceSame permissions and records
Agent pipelineTool layerApproval gateIn design
L4Jobs and live updatesWork that never holds up a screen
Scheduled jobsLive updatesDocument rendering
L5DataEvery record tied to its agency
Relational databaseFile storageAudit trails
L6CloudHosting, data, files and delivery
AWS
- Every module behind one API
- Agency rules applied to every request
- Slow work runs in the background, never in front of you
- Changes reach every screen live
[02] How a lead moves/ One enquiry, end to end
From a form on a website to money in the ledger.
Seven hand-offs, one system. Each step adds to the same record under the same agency rules, so nothing is re-typed between sales, operations and accounts.
01
ArrivesA website form posts to the agency’s own webhook, or Meta sends a lead from an ad form.
02
CheckedThe submission is validated, mapped to the agency’s fields and checked for duplicates.
03
QueuedThe lead joins the agency’s Queue with its source and campaign. Every delivery is logged.
04
AssignedDistribution rules pick the agent, skipping anyone paused, off shift or at capacity.
06
QuotedThe quote is priced from the agency’s rates and rendered to a branded PDF.
07
Booked and billedConfirming creates the reservation and its supplier bills. Invoices and installments follow.
[03] Data, tenancy and security/ Scope · permissions · records
Each agency’s data, kept to that agency.
Every request is tied to the agency that signed in, and the platform only ever returns that agency’s records.
- Secure sign-in, refreshed in the background
- Every request scoped to the signed-in agency
- Role permissions by module, section and action
- Incoming webhooks verified before anything is saved
MKMaya opens LeadsSigned in to Island Hop TravelOnly Island Hop’s records
Island Hop TravelIn scope
leadsEmma Walsh#48402Sofia Marin#48391
invoicesIH-0042-INV-0001$7,500
Another agencyNot visible
leads••••••#•••••••••••#•••••
invoices••••••••$•••
Attachments go straight to file storage over short-lived private links.
Storage per agency is capped and enforced.
Money records are never deleted. Mistakes are corrected with a reversing entry.
[04] Integrations/ Channels in · your AI connected
Every channel in, your own AI connected.
Inbound channels share one pipeline with the same checks. And with the MCP server, the assistant you already use can work inside Tripdocks with your permissions.
- WhatsApp Business on your own numbers
- Meta lead ads, synced as they’re submitted
- Webhooks for any form you already use
- An MCP server for your own AI, in early access
WhatsApp BusinessYour own numbers through Meta’s Cloud API, AiSensy or Gupshup.
Meta lead adsFacebook and Instagram forms, verified and synced as they’re submitted.WebhooksAny website form, landing page or partner site, mapped to your fields.
EmailBooking requests to hotels and feedback requests to clients, sent from the platform.
Early accessMCP server for your own AIConnect an assistant that supports MCP, such as Claude or ChatGPT. It can search leads, create quotes and add tasks, only with the access you grant, and every call is recorded.
[05] Ace, under the hood/ Built on what’s already live
An agent that follows the same rules as your team.
Ace is being built on the same permissions, records and agency rules as everything else. Each stage below is tagged with where it stands today.
INAn eventA new enquiry, a quiet lead, a payment due.Built
01ContextReads agency data through the permission-checked tool layer.Early access
02PlanDecides what the job needs: a summary, a quote, a nudge.In design
03DraftWrites it in the agency’s template and voice.In design
04ChecksDates, prices and rules checked against the record.In design
YOUApproveA person on the team approves or edits. Nothing goes out before.In design
BuiltSame permissionsAce reaches data only through tools that check the person’s own permissions and the access they granted.
BuiltOn the recordEvery action is recorded, so you can see what Ace looked at and what it did.
ResearchMeasured before it shipsDrafts are scored against quotes and messages the agency already approved.
In designBring your own AIDesigned to work with hosted models, or with your own assistant connected to Tripdocks.
[06] Reliability/ Measured from real traffic
Measured, not promised.
We measure availability from production request logs and platform health events. A public status page with live checks is coming next.
99.80%Requests without a server errorSince May 2026
99.90%Time-based uptimeLast 62 days
Public status pageComing next
Request availability by month2026
99.86
May
99.90
Jun
99.51
Jul
99.87
Aug
99.94
Sep
99.78
Oct
[07] Roadmap and R&D/ Shipped · building · next · research
Where the platform is going, sorted by where it stands.
No invented dates. Shipped means in production for every agency on the plan that includes it.
ShippedRule-based lead distributionClient PortalOperations cockpit and incidentsB2B partner ledgerQuote templates with rate refreshMeta lead ads and WhatsApp chat
BuildingMCP server, in early accessMobile app for iOS and AndroidWhatsApp message templates
NextAce summaries, quote drafts and follow-upsPartner portalTrip messaging and tasks in operationsPublic status page
ResearchScoring agent drafts against approved workMetered calling inside the CRM
For partners and programs
Want the technical detail? Ask for the tech kit.
The full architecture, how a request moves through the system, our availability data and the Ace R&D plan, for partners, programs and technical buyers.