Solutions SaaS & software

Resolve SaaS support on the call. From setup questions to billing problems.

Customers explain the problem out loud, and Bidirection resolves it on the page they’re on: setup, sign-in trouble, sync errors and billing questions, by your workflows and your policies. Your team keeps the cases that need judgment.

Illustrative call on Fernbill, a made-up invoicing app.

The issues that fill your queue.

Quick questions and real problems, L1 and L2. Here’s how each one ends.

  1. L1“How do I import my clients from a spreadsheet?”Resolved on the callClients › Import, columns checked together
  2. L1“Does the Starter plan include reminders?”Answered on the callFrom your pricing page
  3. L1“How do I add our accountant?”Resolved on the callTeam › Invite, role set to Accountant
  4. L2“Our bank feed stopped syncing.”Fixed on the callBanks ask for a fresh sign-in every 90 days. Reconnected together under Banking.
  5. 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.
  6. 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.
  7. 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.

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

The answer is on page 87 of your docs. Your customer is on page 1 of your product.

Help centres grow past a hundred articles, and customers still don’t read them. Bidirection reads every page, and when a customer asks, it brings the fix to the screen they’re on.

Illustrative, on Fernbill’s made-up help centre.

What your business gains.

  • Issues resolved in the first session.

    Setup, sign-in and sync problems are resolved on the call with your own workflows, so new customers reach the moment your product clicks without filing a ticket.

  • Features customers find.

    Customers learn what your product can do while their issue is being resolved. The feature they ask about is one question away, not one search away.

  • Your engineers on the hard problems.

    L1 and L2 issues end on the call. What reaches your team arrives with the reason, the step reached and a note, so nobody starts from zero.

  • Docs that fill their own gaps.

    Each question it couldn’t answer becomes a draft answer for your expert to approve, so the next customer hears it.

Fits the way your support team works.

Set it up the way you’d onboard a new support engineer.

  1. 01

    Start from your help centre

    Paste one link. It reads your docs like a new hire, flags pages that disagree, and suggests your agent.

  2. 02

    Turn your playbooks into workflows

    Describe how your team solves an issue, or upload the procedure. Every step is cited to its source, and nothing goes live until you approve it.

  3. 03

    Hand off with the whole story

    When it can’t finish, your team gets a ticket with the reason, the step reached and a note.

It sees the page, not the secrets.

It reads the headings, labels and buttons on your page, never pixels, other tabs or other apps.

Read more on the Trust page
Sensitive fields stay in the browser
Passwords, card numbers and codes are masked on the customer’s device and never sent.
Public knowledge only
Callers only hear content you’ve marked public; staff-only sources never reach them.
Pages it skips
List pages it should never read, like account settings or billing.
Verified domains
Your agent only answers on domains you’ve verified as yours.

35% fewer CX tickets

L1 and L2 issues end on the call, before they become tickets.

Resolve customer issues on the call.