Industry 14 February 2026 6 min read Mokan B2B editorial team

It is one of those decisions that looks neutral on a spreadsheet and turns out to be load-bearing in production. The choice between a global aggregator and a locally-rooted DMC for your Istanbul programme will, in a quiet way, decide whether your customer service team has a good month.

Global aggregators are useful. They are easy to integrate, broad in coverage and consistent across markets. For low-volume, low-complexity destinations they are often the right tool. Istanbul is rarely either of those things.

This city has a way of producing unscripted moments a flight diverted to Ankara, a hotel that suddenly cannot honour its block, a guide who calls in sick on a Sunday in Ramadan, a wedding procession blocking the only road to Topkapı. The question is not whether these things happen. They happen. The question is who answers the phone when they do.

What "local DMC" actually means

The term has been diluted by aggregator marketing. Many platforms describe themselves as having "local partners in 200 destinations" which is technically true and operationally hollow. A real local DMC has three concrete features that most aggregators cannot replicate:

  1. Physical presence in the city, full-time. Not a sales office, not a virtual address. A working ops team whose seats are warm during business hours and whose phone has someone behind it the rest of the time.
  2. Direct contractual relationships with delivery partners. The drivers, guides, hotels, restaurants and venues are contracted by the DMC not subcontracted three layers down through an aggregator's API.
  3. Legal accountability under local law. A licence (in Turkey, this is the TÜRSAB document number ours is 10997) that is forfeit if standards lapse. Aggregators move risk around; local DMCs hold it.

The terminal-exit-B problem

Picture the scenario. Your client's flight lands at Istanbul Airport at 23:40. They are tired, they speak no Turkish, they exit at a gate that has been temporarily reassigned because the original gate is under maintenance. Their pre-booked transfer driver, dispatched by an aggregator algorithm, is waiting at the original gate. The driver is following instructions. The client is following signage. They do not meet.

What happens next determines whether your client emails you a thank-you note or a complaint.

Under a local DMC model: the airport-based dispatcher sees the missed connection in real time on the partner's flight feed, calls the driver, redirects the greeter who is already in the terminal, sends a WhatsApp message to the client with the new meeting point and a photo of the greeter holding a sign with the client's name. Total elapsed time: 8-12 minutes.

Under an aggregator model: the client opens an app, sees a generic "Where is my driver?" support button, files a ticket, waits, calls a global call centre, gets through to someone in another time zone, is told the local supplier will be informed. Total elapsed time: 45-90 minutes. By then, the client is in a taxi having vowed never to book through your agency again.

Real-world cost One missed-greeting incident, refunded, costs roughly the equivalent of three months of transfer-line gross margin at typical European-agency rates. Avoiding one of these incidents per season is, in pure financial terms, worth a premium of several percent on per-transfer pricing.

Five questions to ask any "Istanbul partner"

Whether you are evaluating an aggregator's local capability or a self-described DMC, these five questions will reveal almost everything you need to know:

  1. Where is your operations team physically located? A real answer names a street, an office, ideally an airport terminal. A bad answer talks about "regional coverage" without committing to a place.
  2. What is your TÜRSAB licence number? Anyone selling inbound travel services in Turkey must have one. If they cannot quote it from memory, walk away.
  3. Who answers calls between midnight and 06:00 local time? Listen for a specific role (named ops dispatcher) rather than a vague "24/7 support".
  4. Can I visit your office and ride along with a transfer? Real DMCs are proud of their operation and will say yes. Aggregators usually deflect.
  5. What is your standard escalation flow for a missed pickup? A confident, specific answer beats a polished but generic one.

When aggregators win

We are not in the business of pretending aggregators have no place. They genuinely solve real problems:

  • For micro-volume programmes where contracting a DMC creates overhead that exceeds the savings.
  • For one-off destinations within a multi-city itinerary where the agency has no plans to scale.
  • For commodity transfers where the agency has decided, intentionally, to compete on price rather than service.

What is risky is using an aggregator for a strategic destination somewhere your agency is selling enough volume that operational mishaps will accumulate into reputational damage. Istanbul, for most European trade partners, is in that strategic category.

The agencies who choose local DMCs are not romantics. They are calculators who have done the maths on incident costs over an annual programme and concluded that the operations premium is the cheaper option.

The Mokan B2B model, briefly

Our office is inside Istanbul Airport. The dispatch desk runs 24/7. The drivers are on our payroll or contracted on annual terms; the guides hold Turkish Ministry of Culture and Tourism licences; the partner-facing AMs reply within one business day. We publish our commission tiers. We sign DPAs. We host quarterly FAM trips.

None of that is marketing. It is the operational baseline you need from any serious Istanbul DMC. If you are talking to one that cannot match it, you are talking to the wrong supplier.

Request our rate sheet