From enquiry to lead
Travel enquiries need enough context for a useful first response. The public form requests destination and travel details; the private CRM presents leads in an operational dashboard.
A tailored CRM that brings travel enquiries, lead status and follow-up into one team workflow.
Tranz / Engineering in practiceA2A Holidays publishes a broad catalogue of domestic and international tour packages, with an enquiry form that captures destination, travel date, group size and a message. Its CRM provides the team with a separate place to manage the resulting leads.
Travel enquiries need enough context for a useful first response. The public form requests destination and travel details; the private CRM presents leads in an operational dashboard.
The CRM interface visibly groups leads as New, Yet to Talk, Follow up, Hot, Cold, Won and Lost. This gives the sales team a shared language for the next action and pipeline review.
The supplied project brief describes a move away from per-user CRM pricing. The public website and CRM show the workflow, while the pricing comparison remains a brief-supplied outcome without published cost figures.
The live CRM was delivered in two months using Java, Spring Boot, PostgreSQL, React and Next.js. The team included three backend developers, two front-end developers, a UI/UX designer, a team lead and a technical architect.
This public overview focuses on workflow and does not include customer records or account data.
Continue with the connected project.
Explore project ↗