Travel rarely breaks at the gate. It breaks when somebody needs a refund, a rebook, or a straight answer and gets a queue instead.
That is the part tiket.com is trying to fix. Microsoft says the Indonesian travel platform's CRATER assistant now handles more than 75,000 customer interactions a month, while halo tiket automates 87% of inquiries. tiket.com says the new setup reduces handling time and gives the support team more room for the messy cases that still need a person.

Gaery Undarsa, co-founder and chief marketing officer at tiket.com, put the point in plain English: "In travel, every minute matters." That is not a slogan. It is the operating rule for refunds, reschedules, missed connections, and the kind of trip problem nobody planned for.
The company was already saying that halo tiket should be fast and bounded. In its own launch note, tiket.com said customers could get instant solutions and have each issue resolved within one hour. The current Microsoft write-up adds the part that matters more now: CRATER is built on Microsoft Foundry, uses AutoGen for multi-agent orchestration, and applies guardrails across production interactions. That is the difference between a chatbot and a support system.
That also fits the way tiket.com presents the service on its own site. The company still puts chat, email, and call center details right in front of customers, which is a good sign. The AI is not replacing the support surface. It is getting inserted into it. That is the right order for a travel business. Nobody wants a new way to be ignored. They want a shorter path to the same answer.
The hard part is the handoff
This is where the story gets interesting. The value is not in letting a model chat about travel. The value is in connecting the chat to bookings, payments, refunds, and the rules that decide what can happen next. When that part works, the answer is actionable. When it does not, the customer gets a prettier dead end.
That is also why the people piece matters. tiket.com said halo tiket was built through cross-functional work across customer service, customer experience, product, technology, design, and data science. Microsoft framed the collaboration the same way, saying the goal is to "create meaningful impact on the customer experience." Support stops being the place where work piles up and starts being part of how the product earns trust.
Sam C BarthAI sticks when the CRM underneath it is cleanI help teams get HubSpot, data, and handoffs in shape so new tools have something solid to run on.Visit samcbarth.comIrvan Bastian Arief, tiket.com's vice president of data and AI, said the company is using Microsoft Azure to introduce a way for customers to personalize travel services with "greater speed, convenience, and seamless connectivity throughout every step of their journey." That line matters because it puts the AI effort inside the travel flow instead of outside it. The customer should feel the fix, not the model.
Refunds are a clean test because the second step is where context either survives or gets lost, the same place most support automations break. In a travel business, that context is the booking record, the refund status, the support history, and the rule that keeps the whole thing from turning into a back-and-forth loop.
The number mix matters too. 75,000 monthly interactions and 87% automation sound like efficiency wins, but they only work if the remaining cases get handled better, not worse. A refund that needs human review can still burn goodwill if the AI layer makes the customer repeat the story before a person ever sees it. In travel, the real test is not how many requests the model absorbs. It is whether the handoff to a human feels shorter, cleaner, and less annoying than the old queue.
The good part is that this is not a shiny demo problem. It is a bad-day problem. Flights change. Payments fail. Plans get rewritten. If AI can take pressure off the queue when the trip goes sideways, it is doing useful work. If it cannot, nobody is going to remember the model name. They will remember the wait.
If tiket.com keeps that loop tight, the customer never has to care what CRATER or halo tiket is called. They just notice that the refund lands, the booking updates, and the trip keeps moving. In travel, that is the whole business.




