Overview
A journey is the path one person takes from first hearing about you to their first completed shift.
There is no single "journey" screen in Vome. A journey is what you get when a form, an automation, a sequence and an opportunity are wired together. This article shows the whole chain end to end, so the individual modules make sense as parts of one thing.
This article is for administrators who have read about the modules separately and want to see how they connect.
1. What is a journey made of?
Four things you build separately, then connect.
- A form. The door someone comes in through.
- An automation. The rule that routes them without you touching the application.
- A sequence. The onboarding they work through.
- An opportunity with shifts. What they end up approved for, and what they can then book.
None of these is the journey on its own. The journey is the wiring.
2. What does the chain look like end to end?
Six steps, and an admin does not have to open the application for any of them.
- Someone finds your form and submits it.
- A form automation reads their answers and assigns them to an onboarding sequence, straight to an opportunity, or both.
- They work through the sequence. Steps they can finish alone complete themselves. Steps you need to look at wait on your My Tasks.
- A sequence automation approves them for the right opportunity when they finish.
- They can now see that opportunity's shifts and reserve one.
- They attend, and attendance is recorded against the shift.
That last point matters more than it looks. The record that someone turned up is the same record you use later to prove who is trained and to report your hours.
3. What should I build first?
Backwards, from the end of the journey to the start.
- The opportunity and its shifts, because your automations need something to point at.
- The sequence, because the form automation needs a sequence to assign.
- The form last, because it is the only piece that refers to both of the others.
Building forwards means saving half-finished automations and coming back to them, which is where mistakes get left behind.
4. Where do people actually fall out of a journey?
Three places, in roughly the order they happen.
- A review step nobody reviews. Any step set to wait for you is a stop. If nobody is watching My Tasks, the person waits indefinitely and never hears why.
- An automation that was never set. Applications then sit in the Forms module waiting for someone to notice them, which is exactly the work the automation exists to remove.
- An opportunity with no upcoming shifts. The person finishes onboarding, gets approved, opens the calendar and finds it empty.
All three look identical to the person on the other end: nothing happened.
5. How do I check a journey actually works?
Walk it yourself, the way a real applicant would.
Open your own form link in a private browser window and submit it as a test person. Then follow what happens: did the automation fire, did the sequence arrive, did the steps behave the way you expected, and did approval reach the right opportunity? Testing from the admin side by assigning yourself skips the exact part most likely to be misconfigured, which is the automation.
6. Can one person be in more than one journey?
Yes. A person can be in more than one sequence and approved for more than one opportunity at the same time.
That is normal for organizations running several programs. Keep each journey's automations pointed at its own sequence and opportunity, and the two do not interfere.
Summary
- A journey is a form, an automation, a sequence and an opportunity wired together, not a module of its own.
- The chain runs submit, route, onboard, approve, reserve, attend.
- Build backwards: opportunity and shifts, then sequence, then form.
- People fall out at unreviewed steps, missing automations, and opportunities with no shifts.
- Test by submitting your own form as a real applicant would, not by assigning yourself.
- One person can be in several journeys at once.
Where to go next