Malaka

Contact Malaka

Tell us what the trip needs.

Booking question, skipper request, payment issue or something that simply needs a human answer — start with the context and we'll route it correctly.

Before you write

The more trip context you include, the faster your message reaches the right person.

  • Booking reference, if the trip is confirmed
  • Sailing area and dates you have in mind
  • Skipper request reference, if you posted one

Response times depend on topic and support availability.

Send a message

Give us the context.

Choose a topic and the form asks only for what that topic needs. Nothing here is sent anywhere — this is a frontend prototype.

Topic

Choose a topic so the message reaches the right team.

Your details

Enter your name.

Enter a valid email so we can reply.

Only useful for time-sensitive trip questions.

About the confirmed trip

Add the booking reference so we can find the trip.

About the skipper request

About the payment

About your skipper account

Report a concern

Choose the type of concern you want to report.

Reports are reviewed by the Trust & Safety team. We don't publish investigation deadlines.

Your message

Add a short subject.

Tell us what happened or what you need help with.

Attachment Optional · prototype only

Do not upload passport copies, card details or sensitive personal documents through this general contact form.

HelpfulScreenshot · booking confirmation · a relevant non-sensitive trip document · a photo of the issue.
NeverFull card data · CVV · passwords · private credentials · passport scans.

Prototype only — nothing is sent, stored on a server or turned into a support ticket.

Draft saved

Message sent

We've got the context.

Your message has been prepared for the selected support topic.

Topic
—
Reference
—
Email
—

Prototype submission complete. No support ticket was created and no message left this page. Response times depend on topic and support availability.

Back to Help Center Return to Malaka

Trip context

Two things that speed everything up.

A booking reference or a skipper request reference tells support exactly which trip, skipper and Departure you mean.

Prototype data

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
Prototype data

Waiting on skipper offers?

Include the skipper request reference so your message stays connected to the right trip.

Area
Croatia
Dates
6–13 June
Yacht
Bavaria Cruiser 46
Status: Open for offers

For skippers

Are you a skipper using Malaka?

Skipper questions go through the same form — choose Professional Skipper and tell us which part of the workspace you mean.

Become a skipper
  • Profile verification
  • Credential review
  • Experience publishing
  • Departure setup
  • Skipper requests
  • Calendar
  • Boats
  • Crew
  • Documents
  • Earnings
  • Reviews
  • Payouts

After you write

What happens after you send a message.

01

Message received

The request is categorized by the topic you selected, so it starts in the right queue rather than a general inbox.

02

Context reviewed

Booking or request details are checked if provided — Departure, skipper, payment record or crew status, depending on the topic.

03

Response

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.

For a real-world emergency, do not use this form.

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

Where messages go.

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.

General support

support@malaka.example

Bookings, Departures, payments, crew and documents.

Skipper support

skippers@malaka.example

Verification, publishing, calendar, earnings and the skipper workspace.

Business enquiries

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

Working with Malaka.

If you run a charter fleet, a marina, a skipper network or a travel brand, the business inbox is the right starting point.

Charter partnerships Destination partnerships Skipper networks Marina partnerships Travel partnerships Press Commercial integrations

Business enquiry

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.

Customer support instead

Routing

Where are you in the journey?

Support looks different depending on how far along the trip is. Find your stage and the right route is usually one click away.

Privacy

Share the context, not more personal data than necessary.

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:

  • Full passport details
  • ID scans
  • Card information
  • Passwords
  • Bank credentials
  • Sensitive health data

One last thing

If the question is about a trip, give us the trip context.

Dates, booking reference, skipper request or yacht details help route the message correctly.