Already booked?
If your question belongs to a confirmed trip, include the booking reference so the support team can understand the exact Departure, skipper and trip context.
- Booking
- Croatia Islands Escape
- Departure
- 6–13 June
- Reference
- MLK-240614
Contact Malaka
Booking question, skipper request, payment issue or something that simply needs a human answer — start with the context and we'll route it correctly.
Or read first: FAQ Trust & Safety How It Works
The more trip context you include, the faster your message reaches the right person.
Response times depend on topic and support availability.
Start here
Pick the closest match. It selects the right topic in the form below and tells you what to include.
Send a message
Choose a topic and the form asks only for what that topic needs. Nothing here is sent anywhere — this is a frontend prototype.
Message sent
Your message has been prepared for the selected support topic.
Prototype submission complete. No support ticket was created and no message left this page. Response times depend on topic and support availability.
Trip context
A booking reference or a skipper request reference tells support exactly which trip, skipper and Departure you mean.
If your question belongs to a confirmed trip, include the booking reference so the support team can understand the exact Departure, skipper and trip context.
Include the skipper request reference so your message stays connected to the right trip.
For skippers
Skipper questions go through the same form — choose Professional Skipper and tell us which part of the workspace you mean.
Faster than writing
Most booking, payment and skipper questions are covered in the guides — worth thirty seconds before you write.
Common booking, payment and trip questions.
Read FAQUnderstand Experience, Departure and Booking.
Open guideUnderstand skipper requests and offers.
Open guideVerification, privacy and route-change information.
Read moreMore detailed support topics, by area.
Browse topicsAfter you write
The request is categorized by the topic you selected, so it starts in the right queue rather than a general inbox.
Booking or request details are checked if provided — Departure, skipper, payment record or crew status, depending on the topic.
Support replies through the appropriate channel, usually the email address you gave, or inside the trip messaging for a confirmed booking.
Response times depend on topic and support availability.
If there is immediate danger or a maritime emergency, follow the skipper's onboard instructions and contact the appropriate local emergency or maritime services.
Malaka support is not an emergency-response service.
Contact details
The form is the fastest route because it carries the topic and trip context with it. These addresses exist for anything that doesn't fit.
support@malaka.example
Bookings, Departures, payments, crew and documents.
skippers@malaka.example
Verification, publishing, calendar, earnings and the skipper workspace.
hello@malaka.example
Partnerships, press and commercial integrations.
Replace with production contact details before launch. These are semantic placeholders on the .example reserved domain. No phone number, support hours or office address is published here, because none has been provided.
Business
If you run a charter fleet, a marina, a skipper network or a travel brand, the business inbox is the right starting point.
Tell us what you operate, where, and what you'd like to build together. Customer support questions are answered faster through the main form above.
Routing
Support looks different depending on how far along the trip is. Find your stage and the right route is usually one click away.
In a real emergency, see the note above — not this form.
Privacy
A general contact form is not a secure document channel. Where a trip needs formal documents, the booking flow has its own protected step — use that instead.
Please don't send through this form:
Quick answers
One last thing
Dates, booking reference, skipper request or yacht details help route the message correctly.