Skip to content
comark

Case study · Travel & tourism

One search API for five suppliers, and the CRM the agents sell from

Nazarene Tours, a travel agency in Nazareth, buys its fares and rooms from outside suppliers. We put those suppliers behind one search API, then built the CRM the agents sell from: live search inside each deal, offers the customer can answer, and the website's customers and orders synced every hour.

Client
Nazarene Tours
Industry
Travel & tourism
Languages
Hebrew · Arabic
Stack
Next.js · PHP · Amadeus · Travelport · Gimmonix

Five suppliers, three ways in, and no pipeline.

Nazarene Tours has sold flights, packages and hotels since 1974, to Hebrew- and Arabic-speaking customers. It holds no inventory: every fare and room comes from an outside supplier, and every sale started as a website lead, an email or a phone call.

Suppliers that don't agree

Travelport and Amadeus for scheduled flights, ALP's charter operators and Arkia for charter and domestic flights, Gimmonix for hotels. Each has its own format and speed, and Travelport's price points aren't checked for seats.

Sales without a pipeline

Agents worked from website leads, email and phone. Nothing recorded which offer a customer had received, whether they had opened it, or when to follow up.

No view of the market

Management couldn't put the agency's sales next to airport traffic, market prices and the effect of the website's own pricing rules.

The CRM in the middle, the search API underneath.

Agents work in the CRM. It calls the supplier search API live, mirrors the website's data on a schedule, and connects the channels the agency already uses.

  • Supplier search API · Travelport · Amadeus · ALP · Arkia · Gimmonix

  • Website data API · customers · orders · passengers · leads

  • Market data · Ben Gurion reports · price monitors

  • Meta and Twilio · WhatsApp · Messenger · Instagram · calls

  • NTours CRM · Next.js and PostgreSQL, with Inngest running the scheduled jobs.

  • Agents · pipeline · offers · inbox · calls

  • Customers · offer email · offer page

  • Managers · pricing and market intelligence

  • AI assistant · customer, sales, support and pricing data

The search API and the website data API run on servers Comark manages · full website sync nightly at 03:00

Four decisions behind the search and the sales flow.

Flights: one call, one list

One request runs every flight supplier. The API merges the answers, sorts them by price and groups duplicates, and each itinerary keeps every supplier's quote and the best one. Travelport price points, which aren't seat-checked, stay labelled as such.

Hotels: a job the CRM polls

A hotel search starts a job that returns what the fast suppliers already have. The CRM then asks by revision for hotels added or re-priced, while filters, sorting and paging run on the server.

Offers the customer can answer

Every offer version goes out as a branded email and a public offer page. The customer accepts or asks for changes; either answer moves the deal, schedules a follow-up and notifies the agent. Opens, page views and WhatsApp clicks are logged.

An assistant on the agency's own data

A tool-using assistant reads the CRM's customer, sales, support, pricing and marketing data. It drafts; the agent reviews what goes to a customer.

More of the CRM, built for how the agency sells.

Customer 360 from the website

Orders, passengers, frequent companions and loyalty tiers from an idempotent sync. Cancellation and existing-booking leads open support tickets. ID and passport numbers are masked; managers and admins can reveal them.

Pricing intelligence

Supplier quotes and the website's price next to market prices, flight by flight, with the website's own pricing rules applied. Price monitors run every 10 minutes.

Airport statistics

The Israel Airports Authority's monthly Ben Gurion PDF reports, read page by page with a model against a strict schema and checked against the printed totals.

Support desk

Tickets with SLAs, a board by status, a timeline per ticket and an AI support assistant.

Inbox and calls

WhatsApp, Messenger and Instagram in one inbox, and browser calls through Twilio with recordings and notes on the CRM record.

Demand calendar

Jewish, Muslim and Christian holidays, school vacations and long weekends, stored as demand signals next to the sales data.

What runs on our servers, and what we keep building.

The CRM is an active build. The APIs it depends on run on infrastructure we manage.

Supplier search API

Flights and hotels for the CRM's live search, on servers Comark manages.

Website data API

The endpoints the hourly and nightly syncs read customers, orders and leads from.

CRM and scheduled jobs

Website sync, price monitors, follow-up notifications and reports, maintained by Comark.

Your project next

Tell us what yours must do. We'll come back with an architecture.

Start a project for a scoped proposal, or talk to an engineer first.