A Lucidchart customer journey map is usually drawn as a diagram with swimlanes: one horizontal lane for the buyer, and one for each team that touches them, such as marketing, sales and delivery. The lanes are what make it useful. This article answers how to turn those lanes into ownership inside the levelpartner.ai platform, so every handover the diagram shows becomes an assignment, a task or a notification that actually reaches the right person.
Why the lanes matter more than the stages
Most journey maps describe what the buyer does. A swimlane diagram also shows who on your side is responsible at each point. That second layer is where most firms lose deals, because the gaps sit between lanes: marketing believes sales has the lead, sales believes marketing is still nurturing it, and the buyer hears from nobody.
When you translate the diagram into the platform, each line that crosses from one lane to another becomes a handover rule. A handover rule has three parts: the event that triggers it, the person or team who now owns the contact, and the deadline for their first action.
Before you start
- A diagram with lanes for the buyer and for each internal team.
- Every arrow that crosses lanes marked, so handovers are easy to count.
- Users set up in the platform for each person named in a lane.
- A pipeline in Opportunities with stages that match the buyer lane.
- Access to Automation, Opportunities and Settings for user roles.
Read the diagram for handovers
Go through the diagram arrow by arrow. Ignore arrows that stay inside one lane, because those are a team's own work. Circle every arrow that crosses into another lane. A typical service business has between four and eight of these.
For each circled arrow, write a one-line rule. "When a contact books a discovery call, the sales lane owns them, and the assigned salesperson confirms within one working hour." If you cannot write the rule, the diagram is hiding a decision your team has not made yet. Make it before you build anything.
How to set it up
- Number every arrow on the diagram that crosses from one lane to another.
- Write the trigger event, new owner and response deadline for each numbered arrow.
- In Settings > My Staff, confirm each lane's people have users.
- Go to Automation > Workflows and click + Create Workflow.
- Click + Add New Trigger and pick the arrow's event.
- Add an Assign To User action for the new owner.
- Add an Add Task action with the agreed due date.
- Add an Internal Notification action for the new owner.
- Repeat for every numbered handover on the diagram.
- Add the Tasks widget from General to your dashboard.
- Write the arrow number in each workflow name so the diagram and the platform match.
What it replaces in a 10 to 250 person firm
In a 50-person consultancy, handovers usually run on email and goodwill. The marketing coordinator forwards a promising enquiry, a partner means to reply, and the enquiry ages in an inbox. The diagram already showed that arrow. Turning it into an assignment with a task and a deadline replaces the forwarded email with a rule nobody has to remember.
It also replaces the "who owns this client" question in meetings. Every contact and every opportunity shows an owner, and the Tasks widget shows which handover tasks are still open.
Say the diagram has lanes for buyer, marketing, valuations, sales and lettings, with five arrows crossing between them. Once the rules are built, imagine the Tasks widget showing 14 first actions past due in the first month, 11 of them on the valuation-to-sales handover. A pattern like that would suggest giving that one handover to a named sales coordinator instead of the whole sales team.
How much time it takes
Reading the diagram for handovers and writing the rules takes about two hours with the people who own each lane in the room. Building each handover workflow takes 20 to 40 minutes. Running it costs a weekly five-minute look at overdue tasks by user, plus a quarterly check that the diagram still matches how the teams actually work.
The mistake most people make
Assigning a handover to a team instead of a person. "Sales picks it up" sounds clear on a diagram, but in practice everyone in sales assumes someone else has it. Every handover rule needs a single named owner or a round-robin rule that picks one, plus a deadline. A lane is a team. An owner is a person.
When not to use it
If one person handles a client from enquiry to delivery, the lanes collapse into one and there are no handovers to automate. A simple pipeline is enough. Swimlanes are also unhelpful while roles are still changing month to month. Settle who does what first, or you will rebuild the assignments every time someone moves desk.
For the branching side of the same diagram, where a buyer books or does not book, the customer journey flowchart guide shows how forks become workflow branches.
Troubleshooting
Tasks are created but nobody completes them. The notification goes to an inbox the owner does not watch. Send it to the channel they actually use, such as the mobile app or SMS, and check their notification settings.
Two people get the same contact. Two workflows fire on overlapping events. Check that each handover has one trigger only, and add a condition that skips contacts who already have an owner.
No task ever shows as past due. Tasks have no due date, so nothing can be overdue. Add the deadline to every task action.
The diagram has arrows the platform cannot see. Some handovers happen in a phone call or a hallway. Ask the person receiving them to log a note or move a stage, so the event becomes visible.
Frequently asked questions
Should the buyer lane match the pipeline exactly?
The stages after the first sales conversation should. Earlier steps in the buyer lane, such as reading an article, are better kept as tags. The customer journey steps guide explains where to draw that line.
How many lanes should the diagram have?
One for the buyer and one per team that owns a handover, usually three to five in total. More lanes than that tend to describe the org chart rather than the journey.
Can the handover rules use AI agents?
Yes, for the first response. An AI agent can reply to an enquiry and book a call before the human owner picks it up. The human handover still needs an owner and a deadline.
How do I report on handover speed?
Track time from the triggering event to the first completed task or first reply, grouped by owner. The customer journey process article covers how to set targets for each step, and customer journey roadmap covers sequencing the fixes.