IHL Reservations

Overview

IHL Reservations is a centralized reservation management system built around travel and booking workflows. It combines reservation information, document deadlines and automated reminders in one application, helping the team follow up on time-sensitive work.

The business problem

Travel reservations were being coordinated across emails, spreadsheets and messaging apps. Customer information and booking deadlines were spread between channels, making it difficult for the team to maintain a consistent view of each reservation.

The system needed to bring flight, hotel, tour and logistics reservations together with ticketing time limits, departure dates and customer travel documents. Passport and visa expiry dates also needed reliable tracking, rather than repeated manual checks.

My role and implementation

I designed a Laravel application that creates and dispatches reminders from reservation and document information. The scheduling logic follows the business rules behind each deadline, so staff can work from a shared system rather than coordinate every follow-up manually.

The implementation separates notification channels and reservation types to support future changes. Queue records and notification logs make background processing easier to review, while private file access includes download tracking.

Reservation and document workflows

• Centralized records for flight, hotel, tour and logistics reservations.
• Ticketing time-limit (TTL) reminders based on deadline duration.
• Departure-date reminders and passport and visa expiry monitoring.
• Private client files with tracked downloads.
• Role-based administrative access.

How reminder automation works

Reservation and document data feed into scheduled processing that runs every 15 minutes. Database queues handle reminder delivery through Telegram and email, with notification logs providing a record of processing.

The flow is reservation data → scheduler → queue → Telegram or email notification. Business-rule-driven scheduling, separate notification channels and auditable records are central to the design.

Technology stack

Laravel 11, PHP and MySQL form the application foundation. Laravel database queues and the scheduler support background processing, with the Telegram Bot API and SMTP used for notifications. The deployment environment is DigitalOcean.

Project status and next steps

The portfolio document records an active production environment, with implementation and feature delivery ongoing. The architecture is prepared for future Amadeus integration; that integration is a future extension.

Screens