Journeys and workflows Complex issues, resolved your way.
Turn how your team solves problems into journeys Bidirection follows on calls. Describe them in plain words, build them from your SOPs or learn them from solved tickets, then connect your systems and test every path before a customer hears it.
Always confirm the account email and the last four digits of the card first.1
Look the customer up in Stripe and compare this month’s charges.2
Duplicates under $100 are refunded right away, once the customer agrees.3
Anything larger goes to the billing team with the details.4
- 1Verify the caller“Always confirm the account email and the last four digits of the card first.”
- 2Find the charges in Stripe“Look the customer up in Stripe and compare this month’s charges.”
- 3Refund a duplicate under $100“Duplicates under $100 are refunded right away, once the customer agrees.”
- 4Otherwise, hand off to Billing“Anything larger goes to the billing team with the details.”
Illustrative, on a fictional product.
Build it from how your team works
Describe the problem in plain words or drop in your SOPs, and it drafts every step.
Describe it
Write how your team solves the issue in a sentence, and it drafts the steps and branches for you to check.
From your SOPs
Drop in a procedure document and get numbered steps in plain English, ready for review.
Every step cited
Each step links back to the line it came from, and any step without one is flagged for you to check.
- 1Open Invoicesp. 1
- 2Choose Export and pick a date rangep. 1!Conflicts with your written policy “Exports”: 12 months here, 24 months there. Decide which is right.
- 3Pick the usual formatp. 2!Check against your documents: “the usual format” isn’t in the SOP.
- 4Download the filep. 2
Illustrative, on a fictional product.
Start with the issues that matter most
Learns why customers contact you, and how your team resolves each reason.
Contact reasons
Past tickets are grouped into the reasons customers reach out, with a count for each.
Learn from your team
It reads solved tickets from Zendesk, Intercom or any helpdesk export and proposes journeys, biggest first.
Operations map
See every procedure on one page, with the steps they share and where they conflict.
- 1Open Team
- 2Choose Invite
- 3Set the role
- 4Send the invite
Illustrative, on a fictional product.
Decide what it does at every step
Workflows follow your policy, use your systems through tools you approve, and hand off where you say.
Steps that use your systems
A step can look up or change a record through a tool you approved, like finding a charge in Stripe.
The caller’s yes, and your limits
A change always needs the caller’s clear yes, and you decide who may use each tool and how often a call may use it.
Hand-offs where you say
Say when it hands off, in a plain sentence; the ticket says exactly where the customer got to.
- 1Verify the callerVerify
- 2Find this month’s charges
List charges · reads
- 3A duplicate under $100?DecideYes: step 4No: step 6
- 4Refund the duplicate
Refund a charge · changesNeeds the caller’s yesOnce a call
- 5Say when it arrives, then closeClose
- 6Otherwise, hand off to BillingHand off
Illustrative, on a fictional product.
Switching on for calls, journey by journey.Test every path before it goes live
Run it like a real call against sandbox systems, so nothing real changes.
Test runs
Run a journey like a real call, against sandbox systems, and see every step it took.
Readiness checks
It lists the steps to check, and holds approval until any conflict with your written policies is decided.
Approve each version
Approve a version when it’s ready; earlier versions stay on record.
CustomerHow do I add our accountant to the workspace?
NovaOpen Team in the left menu, then choose Invite.
CustomerOkay. Which role should I pick?
NovaChoose Accountant, then send the invite.
CustomerSent. Thanks.
- Open Team
- Choose Invite
- Set the role
- Send the invite
Illustrative, on a fictional product.
Resolve it on the call
Follows your steps as the customer’s page changes, until it’s resolved or with the right person.
Step by step
It takes one step at a time and follows along as the customer’s page changes.
Troubleshooting
It checks whether each fix worked and moves to the next one by what the caller says.
Same outcome every time
Every caller with the same issue gets the same approved steps and the same policy.
- Open Team
- Choose Invite
- Set the role to Accountant
- Send the invite
Send it, and you’re done.
Team
InviteIllustrative, on a fictional product.
Resolving issues for businesses like yours.
Typical L1 and L2 issues, and how each one ends.
- L1“How do I import my clients from a spreadsheet?”Resolved on the callClients › Import, columns checked together
- L1“Does the Starter plan include reminders?”Answered on the callFrom your pricing page
- L1“How do I add our accountant?”Resolved on the callTeam › Invite, role set to Accountant
- L2“Our bank feed stopped syncing.”Fixed on the callBanks ask for a fresh sign-in every 90 days. Reconnected together under Banking.
- L2“Can we get a refund on the annual plan?”Decided by your policyYour refund policy: full refund within 14 days. Sent to Billing with the details read back.
- L2“We were charged twice this month.”Done in your systemsStripe: the duplicate charge found and refunded, after the customer’s yesSwitching on for calls, journey by journey.
- L2“Please close our old workspace.”Handed off with the whole storyReason: closing a workspace needs the owner’s sign-off. Step reached: workspace and owner confirmed.
- L1“Do these boots run small?”Answered on the callFrom your size guide: order one size up
- L1“How do I swap these for a bigger size?”Resolved on the callOrders › Return or exchange › Size 9
- L1“My coupon won’t apply.”Answered on the callFrom your offer terms: full-price items only
- L2“I bought this 45 days ago. Can I still return it?”Decided by your policyYour returns policy: 60 days for members. Return started together in Orders.
- L2“Where’s my order?”Done in your systemsShopify: order found, shipped Oct 30, arriving FridaySwitching on for calls, journey by journey.
- L2“Can you cancel my order? I picked the wrong size.”Done in your systemsShopify: order cancelled before it shipped, after the shopper’s yesSwitching on for calls, journey by journey.
- L2“The vase arrived broken.”Handed off with the whole storyReason: a damaged item needs a refund decision. Step reached: order and item found on the page.
- L1“I just signed up. Where do I start?”Resolved on the callSetup checklist opened, first location added together
- L1“Can my staff swap shifts without asking me?”Resolved on the callSettings › Shift swaps, turned on together
- L1“Is there an app for my staff’s phones?”Answered on the callFrom your help centre: iPhone and Android
- L2“My staff can’t see their shifts.”Fixed on the callThe week was still a draft. Published together from Schedule.
- L2“Can I get a few more days on my trial?”Decided by your policyYour trial policy: one 14-day extension. Sent to Billing with the details read back.
- L2“We pay for 15 seats but only use 12.”Done in your systemsStripe: three unused seats credited to the account, after the customer’s yesSwitching on for calls, journey by journey.
- L2“Payroll export fails every time.”Handed off with the whole storyReason: a likely bug, for your engineers. Step reached: the export retried together and the error noted.
- L1“How do I download last year’s statements?”Resolved on the callStatements › 2025 › Download
- L1“What’s the fee for an outgoing wire?”Answered on the callFrom your published fee schedule
- L1“When will my deposit be available?”Answered on the callFrom your funds availability policy
- L2“My autopay didn’t go through this month.”Fixed on the callAutopay pointed at a closed account. Moved to Checking ••6021 together under Payments.
- L2“My card was declined at the store.”Done in your systemsCard system: locked after three wrong PINs, unlocked once the member was verifiedSwitching on for calls, journey by journey.
- L2“There’s a charge I don’t recognize.”Handed off with the whole storyReason: possible fraud, sent straight to your team. Step reached: charge date noted.
- L2“I want to dispute a charge.”Handed off with the whole storyReason: disputes need a decision. Step reached: dispute form found.
Typical issues. How each one ends depends on your content and the workflows you approve.
Questions
A how-to helps the customer do it themselves, one step at a time, on the page they’re on. A workflow resolves the issue for them, using your systems through tools your team approved, like finding a charge in Stripe and refunding the duplicate.
Switching on for calls, journey by journey.No. Describe the problem in a sentence, drop in an SOP, or let it learn from your solved tickets. It drafts the steps and the branches, shows where each one came from, and your team checks and approves them.
Every version of every journey, and every tool a workflow uses. Nothing reaches a caller until someone on your team approves it, and earlier versions stay on record.
Answers from your knowledge, how-tos with troubleshooting, decisions by what the caller tells it, and hand-offs with the whole story. Workflows that look up or change records in your systems are built and tested in Bidirection.
Switching on for calls, journey by journey.