The Helen Standard, Operationalized.
One Operational Home
How Helen Oksanen of Helen's Journeys uses Safari Portal to run a fully personalized client process without losing a single detail along the way.
contacts, trips, proposals, itineraries, tasks, and Travel Dashboards, all in one place
Zero Detail Lost
individual traveler data and trip-specific information kept cleanly separate across every client journey
Automation on Her Terms
routine tasks triggered automatically; every client touchpoint stays entirely Helen's
-
-

Tier II Plan
-

Task Sets
-

Travel Dashboards
-
The Challenge
Helen Oksanen built Helen's Journeys around a simple idea: the process can be standardized. The journey never should be.
That's a hard balance to hold. Every client conversation, every proposal, every pre-travel checklist needs to feel handcrafted — but behind the scenes, someone still has to move information, trigger reminders, and keep ten client journeys from ever bleeding into each other. Before Safari Portal, that meant juggling separate documents, task lists, and memory. Helen needed one unified operational home for the client journey that would let her stop managing admin and start focusing on what actually grows the business: the conversation, the design, the relationship.
The Setup
Helen runs her client journey in ten stages, from the first website inquiry through the trip itself and the follow-up conversation that opens the door to the next one. Safari Portal sits at the center of nearly every stage.
Contact vs. file. Permanent traveler information lives with the contact. Everything specific to one trip — destination, dates, budget, discovery notes, proposal, internal notes, feedback, final itinerary — lives with the file. One client can have several past, current, and future journeys, and nothing gets mixed together.
That split pays off in two directions at once: at the contact level, Helen can see a client's full travel and inquiry history and build marketing segments straight from it — past guests, warm leads, repeat travelers, whatever the campaign calls for. At the file level, she has full visibility into every inquiry, so her forecast is always based on actual pipeline progress instead of guesswork.
Proposal to Travel Dashboard. Helen builds the day-by-day itinerary and combines accommodation, transport, activities, and practical information using saved templates to save production time without making the recommendations feel cookie-cutter. The client then receives it as a personal, visual proposal inside their own Travel Dashboard, presented in a considered order: concept first, reasoning second, price last.
Automated reminders, personal messages. Sending a proposal automatically triggers a follow-up task three days later, with suggested template content ready to go. But Helen decides what actually gets sent, and it's always customized, never the template as-is.
Safari Portal can also fully automate message sequences through scheduled messaging, but Helen has chosen not to run her follow-ups that way. She's hands-on by nature, and a task that gives her full control of what actually gets sent is what fits her business.
That's the line running through her process and through Safari Portal itself: the system hands you the tools and the options, but it never tells you how to run your business. The system handles the routine admin; Helen decides the rest.
One record, two systems. Safari Portal is Helen's operational CRM — contacts, trips, proposals, itineraries, internal notes, feedback, tasks, the Travel Dashboard. HubSpot handles marketing. The two are connected but distinct: basic contact and permission data can flow to HubSpot, while detailed traveler and journey information stays in Safari Portal, exactly where it belongs.
In Her Words
"The process is standardized; the individual journey is not. Every stage has a clear purpose and next action. Information is collected once and used in the correct context. The client receives the right information at the right time."
The Results
For Helen, the value shows up in what she no longer has to think about:
One operational home for each client journey, instead of scattered documents and lists
A clear structure separating what's permanent about a client from what's specific to a single trip
A proposal that evolves naturally into the final itinerary and Travel Dashboard, with no re-entry in between
Internal notes and client-facing content living in the same system, cleanly separated
Tasks and reminders automatically tied to the correct client, journey, status, and date
Full journey history on hand, before, during, and after travel
Routine work gets automated. First contact, discovery, the proposal conversation, and every follow-up stay hers entirely.
The Bottom line
Helen's Journeys is proof that automation and personal service aren't opposites – they just need the right dividing line. Safari Portal handles the structure: moving information, triggering tasks, keeping every journey distinct. Helen handles everything that makes a trip feel like it was designed for one specific traveler, because it was.
Helen Oksanen is the founder of Helen's Journeys. ✦
See what Safari Portal can do for your business.
Built for travel professionals who want to work smarter, not harder.