Use case · Travel & hospitality
AI that pre-fills booking support tickets and reviews every pull request
An LLM ticket assistant that extracts booking references and enriches helpdesk tickets with reservation data, plus an AI code reviewer that posts to Slack.
Client details are kept confidential. This use case describes the problem and what we built.
The brief
The client operates a B2B hotel-distribution platform with a busy support desk handling booking queries from travel buyers and hotels.
MultiGenesys built two practical AI tools around the team’s daily work: an assistant that turns free-text support tickets into structured, reservation-enriched records, and an AI code reviewer that gives engineers fast feedback on every pull request.
The challenge
What needed solving
Agents re-keying booking details
Support tickets about hotel bookings arrive as free text. Agents had to find the confirmation codes, look up each reservation in the admin system and copy hotel, room and date details into the ticket by hand.
Inconsistent ticket categories
Request type and category were set manually, so routing and reporting depended on how each agent read the message.
Review load on senior engineers
Every pull request needed a careful first pass. Senior engineers spent time on routine review comments instead of design and risk.
The solution
What we built
Event-driven ticket pipeline
New helpdesk tickets are queued on Amazon SQS. A Spring Boot consumer picks them up with a managed thread pool, so bursts of tickets do not slow the helpdesk.
LLM extraction
An OpenAI GPT model reads the ticket subject and body and returns structured output: booking and confirmation codes, request type and category.
Reservation enrichment
The service looks up each code in the booking platform and writes hotel, room, stay dates, refundability, cancellation cut-off and guest details back into the ticket's custom fields, then moves it into the open queue.
AI pull-request reviewer
An AWS Lambda function receives repository webhooks, fetches the diff, asks an LLM for review feedback and posts it to Slack. Developers rate the feedback in Slack, and ratings are stored in DynamoDB and S3.
Safe rollout controls
Feature toggles, CloudWatch metrics and token counting keep the assistant observable and let the team switch behavior on or off without a redeploy.
The outcome
What changed
Tickets arrive ready to work
Agents open tickets that already carry the reservation details they need, instead of starting with a lookup.
Consistent classification
Request type and category are set the same way every time, which makes routing and reporting more reliable.
Faster first-pass reviews
Every pull request gets automated feedback in the team's Slack channel, with developer ratings to tune the reviewer over time.
Technology used
- Java
- Spring Boot
- OpenAI GPT
- DeepSeek
- AWS Lambda
- Amazon SQS
- Amazon DynamoDB
- Amazon S3
- Amazon CloudWatch
- Slack API
- Helpdesk API
Related use cases
Running a B2B hotel-distribution business on one admin, supplier and pricing back end
Admin and supplier services for hotel rates, availability, rate plans, buyer margins, wallets and virtual cards, with queue-based pricing updates on AWS.
Read the use caseDeveloper onboarding where every training assignment gets an AI code review
A training and onboarding platform that links trainee pull requests to topics, sends them for AI review, scores them and keeps mentors in control.
Read the use caseMapping hospital service catalogues to clinical codes, with reviewers in the loop
A mapping engine, hospital onboarding portal and LLM contract-rules extraction that turn messy hospital price lists into auditable, coded data for an insurer.
Read the use caseHave a similar problem to solve?
Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.