KolayTurum integration: tour catalog, prices, availability

At a tour agency, updating prices is a silent time thief. The departure date changes, the hotel class shifts, the child price is revised; one person writes these into the Instagram bio, another into Excel, another into a WhatsApp template. A price kept in three separate places sooner or later contradicts itself, and the wrong figure goes out to the customer. This article explains, from field experience, how to connect your tour catalog to inTusell with the KolayTurum integration and keep prices and availability current automatically. This is the catalog-and-pricing piece of our sector-specific "how to train your AI" series; for the tourism pillar of the series, see how to train your inTusell AI.

Quick answer

Why you connect the catalog

There is only one reason to connect the catalog to inTusell: so that the price has a single source of truth. In manual mode, every channel keeps its own memory. In connected mode the price matrix is the one source, and the AI reads the same row in customer DMs and on WhatsApp alike.

Think of the concrete difference like this:

inTusell is an AI sales assistant and CRM that answers messages on WhatsApp, Instagram and web chat, books appointments and opens orders, and follows each customer through the sales pipeline; it is not a simple chatbot. An experienced salesperson does not invent the price; they look at the price list. The list inTusell looks at is the price matrix.

Who is it for?

• Agencies that manage an umrah, hajj or cultural tour catalog through KolayTurum (the sync pulls these three tour types).
• Agencies without KolayTurum whose tour packages are published on their website (site import).
• Operations teams that want to quote prices consistently across multiple channels (Instagram, WhatsApp, web).
• Those who want to keep entering packages manually and still prevent the AI from giving wrong prices.

No technical knowledge is required; setup is done from the panel.

Connecting KolayTurum

In the panel, you open the KolayTurum card on the Channel Connections › Agency Integrations page. Three pieces of information are requested; you get these from your KolayTurum agency panel:

firmaid

webkul

websifre

The username and password (webkul, websifre) are stored in an encrypted credential vault; they are not shown again as plain text in the panel. You can try the details with "Test connection". When you turn the connection on and save, the first sync starts right away and inTusell pulls:

• Tour packages (umrah, hajj and cultural; TumTurlarXml)
• Hotel list (TumOtellerXml)
• Price matrix (departure × hotel × room type)
• Departure capacity and seats already sold in KolayTurum

So a one-time setup brings your entire existing catalog into inTusell. From here, you’ll find step by step how to shape the AI to answer correctly in how to train your inTusell AI.

Nightly sync

Once the connection is established, you don’t trigger the sync yourself. A sync that runs every night (around 05:00 Turkey time) pulls the current data from KolayTurum:

• Newly added packages come in.
• Changes in the price matrix are updated.
• Hotel class or room type edits are reflected.

When you log into the panel in the morning, prices are already current. For an urgent change you can pull right away with "Sync now". On the availability side, seats are allocated in a single locked transaction, and seats sold in KolayTurum are deducted from capacity too. If a departure is full, the AI does not open a booking and hands the conversation to your team.

Price matrix: departure × hotel × room

In tourism, a price is not a single number; it’s a matrix. inTusell keeps this matrix as it is. Each row is the intersection of these dimensions:

• Departure (date and departure city, e.g. Istanbul, Ankara, Izmir)
• Hotel (the hotels linked to the package, e.g. 4- or 5-star options)
• Room type (single, double, triple, quad)

On top of these, passenger-dependent variables are added:

When a customer says "there are 3 of us, one is 5 years old, 5 stars from Izmir," the AI reads the correct departure, hotel, room type and child price from the matrix and builds the quote from there. If more than one option is left, it asks the customer. The exchange rate is frozen at the moment of quoting; that way, even if the rate moves later, the figure you gave the customer stays fixed.

Auto-publish + status preservation

Every package is either a draft (draft) or published (published); you can also archive a package by hand. Here three controls work together:

• Auto-publish switch: If on, packages coming in from sync with a future departure are published directly. If off, they come in as drafts, and you review and publish them.
• Status preservation: A package you archived by hand is never republished by the sync. The decision you made is preserved.
• Catalog cleanup: A package that drops out of the KolayTurum list, or has no future departure left, is unpublished and goes back to draft; it is never deleted. If the list comes back half empty, this step is skipped so the catalog doesn’t empty out.

This setup leaves control with you, somewhere between "publish everything automatically every night" and "let me approve everything by hand." Starting with auto-publish off and turning it on after reviewing the first syncs is a safe start.

The AI does not invent prices

This is the most critical trust point of connecting the catalog. The AI quotes only from the price matrix. If someone asks for a combination that is not in the matrix (an unsynced departure point, say, or an undefined room type) the AI does not guess a figure. Instead, it:

1. Notices that the price is not in the matrix.
2. Does not tell the customer a made-up number.
3. Hands the conversation to your team; the handoff lands on the Decisions page with the full history.

So it does not say things like "roughly this much" that would put you in a tight spot later. This behavior is the same in every operating mode (Intern, Senior, Full approval); a missing price is a typical reason for a handoff. To see how these handovers are managed in the inbox day to day, read how you use inTusell.

Writing the booking confirmation back to KolayTurum

The flow is not one-way. If you turned on write-back on the KolayTurum card, once a KolayTurum-sourced booking is fully paid inTusell writes it to KolayTurum as a pre-registration (WebOnkayit). If the write fails, it is retried in the nightly sync; the same booking is never written twice. The booking lifecycle follows these lines:

quote → option_hold → awaiting_payment ↔ partially_paid → fully_paid → confirmed → departed → completed

Cancellation and refund branches are also part of this cycle. Personal passenger fields are kept encrypted and open only to an authorized, logged action. The customer gets a privacy notice (KVKK) with the agency’s own link; contract acceptance is recorded with a SHA-256 hash. On the payment side, bank transfer/IBAN is the default method (requires no integration); if iyzico is connected, the AI also sends a card payment link. A bank-transfer booking lands in the Receivables ledger with a reference code, and your team approves the receipt. The seller is always the agency: inTusell stays out of the loop.

Without KolayTurum: other sources

If you don’t use KolayTurum, you build the same price matrix structure in other ways:

• Import from your website: You give the address of your tour pages; inTusell extracts package candidates, and you pick them in a preview and add them as drafts. Departure, hotel and price rows that can be read from the page are suggested too; you complete what’s missing and publish. Quotes still come from the matrix.
• Manual entry: You create the package by hand from the panel and enter the matrix row by row; you can copy one departure’s prices to other departures in bulk.
• Knowledge Base: You add tour terms, visa information, the cancellation/refund policy and FAQ as files (PDF, Word, Excel, CSV, TXT) or a website scan under My business › Knowledge › Knowledge Base. The AI looks at these when it replies. An Excel or CSV price list is read here as a document; it does not load prices into the tour engine.

Important distinction: exact prices, seats and payment always work from the matrix in the catalog; the policy and description texts come from the Knowledge Base. The two never mix, so the AI reads both the price and the text from the correct source. For the side of connecting the catalog to channels, see the solutions and integrations pages.

What it isn’t

• It is not an accounting or reservation ERP. inTusell runs the sales conversation and quotes the price from the correct source; it does not replace KolayTurum, it talks to it.
• It is not a price prediction engine. It does not do dynamic pricing and does not invent discounts. It only reads the matrix you defined.
• It is not a tourism-specific product. The tour module (beta) can be enabled in any plan; plans differ only by messages, voice minutes and storage, and do not vary by sector. For package details, see the pricing page.
• It is not a one-time import tool. The sync is continuous; the catalog is not copied once, it is kept current night after night.

Frequently asked questions

Is KolayTurum required to use inTusell?

No. KolayTurum is a convenience. You can add your packages by hand in the panel or import them from the tour pages on your website. If you use KolayTurum, you just enter firmaid, webkul and websifre and turn the connection on.

How often are prices updated?

If KolayTurum is connected, packages, the hotel list, seats and the price matrix sync automatically every night (around 05:00 Turkey time). In the morning you see current prices in the panel; for an urgent change you can pull right away with "Sync now".

How do child and infant prices work?

Each price matrix row keeps the child age threshold (child_age_max), child price, infant price and single supplement separate. The AI takes the right price from the row based on the passenger’s age; if a child or infant price is not defined, it gives no quote and hands the conversation to your team.

Can the AI give a wrong price?

The AI only reads the price from the price matrix; it does not invent prices. If a departure/hotel/room combination that is not in the matrix is requested, it gives no price and hands the conversation to your team; the handoff lands on the Decisions page.

Can I add a tour manually?

Yes. Independently of KolayTurum, you can create your own package from the panel and enter the price matrix by hand, or import the tour pages on your website as drafts. You manage the sources together in the same panel.

Are my KolayTurum login credentials safe?

Yes. webkul and websifre are stored in an encrypted credential vault, are never shown as plain text in the panel and are not written to logs; firmaid sits on your account as your company number. Each agency’s data is kept separate.

Next step

After you connect your catalog, you go in two directions. To shape the AI with your tour terms and sales style, read how to train your inTusell AI. To see how incoming quotes are managed in daily operations, move on to how you use inTusell. You can reach all articles via the blog.

If you’d like us to connect your catalog together, request a demo or write to hi@intusell.com; let’s set up the first sync together with your existing KolayTurum account.