How it works From a problem in plain words to a resolved call.
Your support team builds it, tests it and runs it. Describe how you solve a problem, connect the knowledge and systems it needs, test it like a real call, and put it in front of customers when it’s ready.
Describe it in plain words
Say how your team solves the problem, or drop in the SOP. Bidirection drafts every step and branch and shows where each one came from.
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.
Connect your systems
Steps that need a system use a tool your team reviewed, and ask for the caller’s yes before anything changes.
Switching on for calls, journey by journey.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.
Ground it in your knowledge
Answers and decisions come from your own policies and help centre. Staff-only pages stay with your team.
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.
Test it like a real call
Every path runs against sandbox systems, so you see exactly what it will do before you approve it.
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.
Resolve it on the call
Customers explain in their own words. Bidirection follows your workflow to the end, or hands off with the whole story.
Switching on for calls, journey by journey.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.
Improve with every call
Questions nothing answered become draft answers, contact reasons show what to build next, and daily checks catch changes in the systems you connected.
Three cards: a question asked on two calls that nothing answers, with a button to draft an answer; this week’s top contact reasons; and a daily check that found a change in the Stripe refund tool to review.
Illustrative, on Fernbill, a made-up invoicing app.
Getting it in front of customers.
The first link it reads, and the one line of code that puts it on your site.
Start from one link
Paste your website’s address and it gets to know your product the way a new hire would.
Reads your site
It reads your pages, then checks them again every week for changes.
Flags pages that disagree
Two prices for one plan, or two answers to one question, are flagged before customers hear either.
Suggests your agent
You get a ready-to-edit agent built from what your site says you do.
Go live when it’s ready
One script on your site, or a link you can share anywhere.
One script tag
Add it once; it answers only on domains you’ve verified.
Or a help link
A hosted page with a QR code for emails, receipts and printed guides.
Publish when ready
Nothing answers on your site until you publish, and you can unpublish at any time.
<script async src="…/embed.js" …></script>CopiedWhat you need to start.
Your website
The address of the site your customers use. That’s enough to start.
How your team works
SOPs, help articles, policies or solved tickets make it resolve more. Optional.
One script tag
Or a hosted help link, if you’d rather not change your site.
Setup questions
No. Your support team sets it up in plain words: start from your website’s address, then describe or import the journeys you want. Going live is one script tag, or a hosted help link with a QR code if you’d rather not change your site.
Yes. Run test conversations from your workspace; they never count toward your numbers. Nothing answers on your site until you make it live.
Yes. Bidirection can give your existing chatbot a voice, or turn to it when your own content doesn’t cover a question.
From the website pages and documents you add, and the journeys your team approves. Callers only hear knowledge you mark public. When your content doesn’t cover a question, it asks a clarifying question or says it doesn’t know.
Nothing. The Free plan includes 100 call minutes a month. Paid plans start at $20 a month.