Case studiesTravel claims

iPurey TravelAssist: conversational travel-claim intake

iPurey’s TravelAssist moved travel-disruption claim intake into a guided conversation. Abhishek Gawade’s work connected the chat experience to itinerary information, eligibility rules and the existing claim-status backend.

Business
iPurey
Sector
Travel claims
Scope
Conversational intake and claim status
Contributor
Abhishek Gawade
Editorial illustration: a silver suitcase with an orange luggage tag
AI-generated editorial illustration of the project’s domain.

A travel claim needed to be usable during a disruption.

A traveler dealing with a delay or cancellation has limited attention for a long intake process. iPurey needed to collect the information used by its claim workflow in a format suited to a phone and a conversation.

The interface also had to remain connected to the business behind it. Itinerary capture, eligibility rules, claim status and support questions needed a route into existing services.

Connect the conversation to the real claim workflow.

TravelAssist combined quick replies and custom conversation flows with natural-language understanding and generative AI. The assistant collected itinerary information and connected it to the backend’s eligibility and claim-status services.

The chat flow covered flights, rail and connections. A traveler could supply information, check claim status and ask for support through the same interface instead of treating each step as a separate web task.

What the workflow includes

  • Quick-reply buttons and custom flows that guide rather than interrogate
  • NLU plus generative AI, so it parses a question and replies in plain language
  • Itinerary capture across flights, rail and connections, mapped to eligibility rules
  • Integrated with existing backend services for live claim status

Product walkthrough

Conversational intake and claim status. The delivery section explains the workflow demonstrated here.

Guided intake and status checks in one conversation.

The project connected a conversational entry point to iPurey’s existing service workflow. The value of the implementation was in carrying the user’s information into the backend and returning the relevant status, with the conversation providing the interface.

What this means for the technology owner.

A customer-facing assistant needs an owner for both the dialogue and the systems it calls. Eligibility rules, backend responses and conversation changes must remain aligned. The operating scope should explain when to hand a question to a person and what the user sees when a connected service is unavailable.

How we operate AI workflows →

Conversational AINLULLMsNodeWebhooksBackend integration

Project contribution: Abhishek Gawade. The scope described above identifies the work behind this case.

iPurvey.com — project link

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.