Importing your tour catalog into intusell: automatic prices and availability with KolayTurum & XML

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 the field use of connecting your tour catalog to intusell with the kolayturum integration and keeping 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 becomes 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:

This is where intusell's positioning as "not a chatbot, but a senior salesperson" becomes concrete: a senior 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?

• Umrah, Hajj, cultural, holiday, domestic and international tour agencies that manage their catalog through KolayTurum.
• Agencies that export their catalog via XML/Excel.
• 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 reasonably quick and is done from the panel.

Connecting KolayTurum

In the panel, under the Tours section, you turn on the KolayTurum connection. Three pieces of information are requested; you get these from your KolayTurum agency panel:

firmaid

webkul

websifre

These three values are stored encrypted (credential vault); they are not shown again as plain text in the panel. The moment the connection is established, the first sync starts and intusell pulls:

• Tour packages (TumTurlarXml)
• Hotel list (TumOtellerXml)
• Price matrix (departure × hotel class × room type)

So with a one-time setup, your entire existing catalog comes into intusell. From here on, 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 cron that runs every night at ~02:00 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 also trigger a manual sync without waiting, but in daily operations you won't need it. On the availability side, the seat ledger is atomic: capacity is protected by a database constraint, so overbooking is mathematically impossible.

Price matrix: departure × hotel class × 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 point (e.g. Istanbul, Ankara, Izmir)
• Hotel class (3 / 4 / 5 stars or special categories)
• Room type (single, double, triple, family)

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 class, room type and child price from the matrix and builds the quote from there. The FX 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 has a status: draft, published or archived. Packages coming in from sync may be published on the KolayTurum side. Here two controls work together:

• Auto-publish toggle: If on, eligible packages coming in from sync are published directly. If off, they come in as draft first, and you review and publish them.
• Status preservation: If you set a package to archived by hand, the next sync does not make it published again. The decision you made is preserved.

This pair leaves the control with you, somewhere between "publish everything automatically every night" and "let me approve everything by hand." Most agencies start with auto-publish off and turn it on as trust builds.

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 a combination that is not in the matrix is requested — for example an unsynced departure point 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. Offers to connect the conversation to a live team member (handover).

So it does not utter sentences like "roughly this much" that would put you in a tight spot later. This behavior works together with the AI's human-handover (lock) modes; a missing price is a typical hybrid handover scenario. You can find how these handovers are managed in the inbox in daily operations in how you use intusell.

Writing the reservation confirmation back to KolayTurum

The flow is not one-way. When a customer reservation is confirmed, intusell attempts to write the result back to KolayTurum (best-effort). The reservation lifecycle follows these lines:

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

Cancellation, refund, no_show and waitlist branches are also part of this cycle. For each passenger, name, date of birth and passport details are kept encrypted; KVKK explicit consent and contract acceptance are stored with SHA-256 hash proof. On the payment side, bank transfer/IBAN is the default method (requires no integration), iyzico POS is optional, and the seller is always the agency — intusell stays out of the loop.

XML and other sources

If you don't use KolayTurum, you lose nothing. You can feed the same price matrix structure from other sources too:

• XML / Excel / CSV: You upload your file containing departure, hotel class, room type and price columns.
• Manual entry: You create the package by hand from the panel and enter the matrix row by row.
• Knowledge Base (RAG): You upload tour terms, visa information, cancellation/refund policy and FAQ texts as PDF or free text into the Knowledge Base section. The AI searches these automatically on every reply.

Important distinction: the price always comes from the structured matrix; the policy and description texts come from the Knowledge Base. You don't mix the two, so the AI reads both the price and the text from the correct source. You can review the side of connecting the catalog to channels on 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 can be enabled in any plan; the pricing model is based on messages and voice minutes, and does 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 channel. You can also add the catalog manually or upload it via XML/Excel/CSV. If you use KolayTurum, you just enter firmaid + webkul/websifre and turn on sync.

How often are prices updated?

If KolayTurum is connected, a nightly cron (~02:00) automatically syncs the catalog, hotel list and price matrix. In the morning you see current prices in the panel; no manual action is needed.

How do child and infant prices work?

The price matrix keeps the child age threshold (child_age_max), child price, infant price and single supplement separate. The AI picks the correct row based on the passenger age and builds the quote from there.

Can the AI give a wrong price?

No. 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 does not give a price and offers to connect the customer to a live team member.

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. You manage both sources together in the same panel.

Are my KolayTurum login credentials safe?

Yes. firmaid, webkul and websifre are stored encrypted (credential vault). They are not shown as plain text in the panel. The entire system is end-to-end encrypted and KVKK/GDPR compliant.

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 hello@intusell.com; with your existing KolayTurum or XML source, we'll set up the first sync in 20 minutes.