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.

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.

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.

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.

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.

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.

Illustrative, 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.
See Bidirection for SaaS & software

Typical issues. How each one ends depends on your content and the workflows you approve.

Questions

Resolve customer issues on the call.