Fewer tickets.Customers who stay, faster onboarding, features found, and support on tap.

Bidirection is a voice AI agent for your website. Customers talk to it instead of typing into a chat, and it resolves their issue on the call, from quick questions to complex L1 and L2 problems, by the journeys your team approves. What needs a person reaches your team with the whole story.

Bidirection’s call window, on an illustrative call with Fernbill, a made-up invoicing app.

35%fewer CX tickets
24/7support on tap
1 lineof code to go live on your site

Built and run by your support team.

Describe a problem in plain words. Bidirection turns it into a workflow, connects it to your knowledge and systems, and tests it like a real call before any customer hears it.

A support lead types how duplicate charges are handled. Bidirection drafts a six-step workflow: verify the caller, find the charges in Stripe, decide whether it is a duplicate under $100, refund it after the caller says yes, close, or otherwise hand off to Billing.

The Stripe connection with two reviewed tools: List charges, which reads data, and Refund a charge, which changes data, asks for the caller’s yes and runs once per call. Both are approved.

Switching on for calls, journey by journey.

Two public sources the workflow answers from: the refund policy, section 2, and a help centre article on duplicate charges. A staff-only billing handbook is never read to callers.

A test run of four paths on sandbox systems: a duplicate under $100 is refunded, one over $100 is handed to Billing, a single charge is explained, and when the caller says no nothing changes. Four of four pass, and the team approves version 1.

A test call: the caller says they were charged twice, gives the account email, hears that the second $49 charge will be refunded, says yes, and the refund is done. The workflow’s steps tick off beside the call.

Switching on for calls, journey by journey.

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

From simple questions to complex problems.

Most support is L1 and L2 work your team repeats every day. Bidirection resolves it on the call, by your rules, and leaves your team the work that needs judgment.

80%
of service leaders say 20% or more of their team’s tickets are repetitive, yet easy to resolve.DigitalGenius and Canam Research, survey of North American service leaders, 2018

Illustrative week of support for Fernbill, a made-up invoicing app.

Works with the systems you already use.

Bidirection reads your knowledge, learns from your helpdesk and connects to the tools that resolve the issue. Nothing to migrate, nothing to replace.

  • Connects Stripe, Shopify, HubSpot, Salesforce or your own API as tools you approve one by one
  • Reads your help centre, wiki and drive, and keeps them in sync
  • Learns from solved tickets in Zendesk or Intercom, or an export from any helpdesk
  • Keeps your chatbot: Bidirection can speak its answers

Example journeys: Refund a duplicate charge draws on Zendesk (solved tickets), Confluence (refund policy), Stripe (refund a charge); Where’s my order? draws on Intercom (closed conversations), Your website (shipping times), Shopify (find an order); Is the app down? draws on Any helpdesk (exported tickets), Notion (incident playbook), Statuspage (list open incidents); My device stopped working draws on Zendesk (solved tickets), SharePoint (warranty terms), Salesforce (open a case).

Act through

Switching on for calls, journey by journey.
  • Freshdesk: Tickets and private notes.
  • Your API: From its OpenAPI file. Reads are low risk; changes are flagged for review.
  • Your database: Postgres or MySQL, with a read-only login.
  • MCP server: Any MCP server. Its tools wait for your review.

Each system becomes tools your team reviews: what it reads, what it changes, its limits, and when the caller must say yes.

Know from

  • Your website: Every page, re-read weekly. Signed-in web apps too.
  • Documents: PDF, Word, PowerPoint, Markdown, HTML, CSV, JSON and text files.

Answers come from these, kept in sync. Pages for staff only never reach a caller.

Learn from

  • Any helpdesk: A JSON export of solved tickets, from any helpdesk.

Solved tickets show what customers ask and how your team resolves it.

Your chatbot

  • Your chatbot: Its answers, spoken on the call.

Keep the chatbot you have. Bidirection can speak its answers on calls.

Every part of resolution, in one platform.

Each part does one job, and your team stays in control of all of them.

Simplified Bidirection screens, on Fernbill, a made-up invoicing app.

See how it works, step by step

What resolution does for your business.

Issues end on the first call, your team works the cases that need judgment, and every customer gets the same answer at 2 a.m. as at noon.

L1 and L2 issues are answered, resolved or fixed on the call, so they never become tickets.

Problems are worked through to the end on the first call, check by check, so customers don’t come back and ask again.

What needs a person reaches your team with the whole story: what was decided, the step reached and the details read back.

Every call follows the journey and policy your team approved, so a customer at 11 p.m. gets the same decision as one at 9 a.m.

Customers get issues resolved at any hour, right on your website: no office hours, no phone number to find, no email to wait on.

Customers who get unstuck keep using your product, instead of quietly giving up halfway through setup.

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

A chatbot answers. Bidirection resolves.

A chat box makes customers type the problem out, read what comes back and do the steps on their own, and they still file tickets. On a call, Bidirection hears the whole problem, sees the page they’re on and works it through with them, by your rules, until it’s fixed or with the right person.

Illustrative: a typical chat widget and Bidirection on Fernbill, a made-up invoicing app.

Why voice, not typing.

The next generation of support is AI your customers can talk to. Nobody should have to type a problem into a chat box to get help.

  • 3×faster to say than to type on a phone keyboard, with 20% fewer errors.

    Saying it is faster.

    Customers explain the whole problem in one go, in their own words, instead of squeezing it into a chat box.

    Source: Stanford University, University of Washington and Baidu, 2016

  • Their eyes stay on the fix.

    They keep working on your page while Bidirection talks them through each step. No chat window to read and switch back from.

  • It asks, like a person would.

    When something is unclear, it asks straight away, the way your best support engineer would, instead of guessing from a typed fragment.

  • AI the whole way, still a conversation.

    Nobody is sent to a chat to type it all again. What needs a person reaches your team with the whole story.

  • 14%of service issues are fully resolved in self-service.
  • 36%of issues customers call “very simple” are fully resolved in self-service.
  • 43%of the time, customers couldn’t find content relevant to their issue.

Source: Gartner, survey of 5,728 customers (December 2023), published August 2024

See the full comparison

Control and trust, built in.

Your rules are checked on every call, nothing goes live until your team approves it, and passwords, card numbers and codes never leave the browser.

  • Callers only hear knowledge you mark public.
  • It refuses attempts to talk it out of your rules.
  • Each rule shows whether it’s checked on every call.
See how we handle trust

Questions

Resolve customer issues on the call.