Almost every agency we meet runs on a general-purpose CRM, a spreadsheet, or both at once. Both work — right up to the point where the trip itself needs somewhere to live.
Built for software deals: a contact, an amount, a close date. A trip is none of those things. It has dates, a party size, twelve nights of arrangements and four suppliers, and none of that fits a field. So it ends up in the notes — and the notes are where information goes to be forgotten.
You can tell by how much lives in free text.
Genuinely good at what it does, which is why it never quite goes away. It just cannot chase anybody. It will not tell you a balance is due on Friday, will not notice a traveller went quiet for nine days, and will not survive the person who built it going on holiday.
You can tell by who is the only one allowed to edit it.
Not a feature count — the specific places the work falls out of the tool and back onto a person.
| General CRM | Spreadsheet | OpenVoy | |
|---|---|---|---|
| Contacts, notes and a pipeline | yes | Manually | yes |
| Knows what a trip is | no | no | yes |
| Day-by-day itinerary on the request | no | no | yes |
| Library of stays, activities, transfers | no | Another tab | yes |
| Urgency that follows the departure date | Fixed timer | no | yes |
| Traveller-facing trip page | no | no | yes |
| Deposit and balance deadlines tracked | no | Manually | yes |
| Post-booking checklists | no | Manually | yes |
| Request forms that open a deal | Add-on | no | yes |
| Reply routing back to the right trip | Add-on | no | yes |
| Reporting by market and season | Build it | Build it | yes |
| Survives someone leaving the company | yes | no | yes |
Written from what agencies tell us in demos. If your setup already does all of this, you probably don't need us — and we'll say so.
Genuinely — open it next to OpenVoy and we'll go row by row through what moves and what doesn't.