A case for a travel agency, where we integrated amoCRM with U-ON and put together a clear client route: application, tour selection, reservation, documents, payment, departure and contact again after the trip.
Applications arrive quickly, but then the manager is forced to switch between amoCRM, U-ON, chats and tables.
Reservations, documents and payments often live separately from each other, so some stages are lost or duplicated.
It is difficult for a manager to see who quickly processes requests, where tourists hang out and at what stage money is lost.
What did you do
Integration and logic
We integrated with U-ON so that the manager launches the necessary actions directly from amoCRM, rather than rebuilding the process manually.
We put together a single logic: application, selection, reservation, payment, documents, departure and return of the client for the next tour.
We added button scripts in the deal card so that each step is completed faster and equally for the entire team.
What was decided in the work
Tasks
A button for sending a client to U-ON, a button for requesting documents, a button for fixing payment and a re-touch button.
Automatic tasks and reminders for reservations, payments and next actions of the manager.
Clear control of the entire tourist route without a gap between systems.
Case skeleton
Case of a travel agency with U-ON and an automated client route
On this page you can further show the integration scheme with U-ON, the stages of the transaction, buttons in amoCRM, the logic of reservations, payments, documents and scenarios for repeat sales after the trip.
U-ON
Integration of the tourist accounting part with amoCRM without breaking the context for the client and the application.
Buttons
Quick actions within a transaction: send to U-ON, reservation, documents, payment, task and signal to the manager.
Automation
Full cycle from the first application to departure and return of the client for the next tour.