Tools and integrations Your systems, ready for every workflow.

Resolution lives in your systems. Connect the billing, commerce, CRM and helpdesk tools you already use, or your own API, database or MCP server, and your team decides exactly what each tool may do.

Illustrative, on a fictional product.

Switching on for calls, journey by journey.

Connect the systems you already use

Pick a ready connector or bring your own system, and it finds the tools each one offers.

  • Ready connectors

    Stripe, Shopify, HubSpot, Salesforce, Freshdesk and Statuspage connect with a sign-in or an API key.

  • Your own systems

    Add your API from its OpenAPI file, your database with a read-only login, or any MCP server.

  • Tools for every workflow

    Each tool becomes a step a workflow can use, like finding a charge or cancelling an order.

Illustrative, on a fictional product.

Decide what every tool may do

Your team reviews each tool, and every change carries the guards you set.

  • Reviewed one by one

    Every tool waits for your review; reads are low risk, and anything that changes a record is flagged.

  • Limits and the caller’s yes

    Decide who may use each tool and how often a call may use it, and require the caller’s clear yes before a change runs.

  • Daily checks

    A daily check spots when a connected system changes, and pauses the steps that use it until someone looks.

Illustrative, on a fictional product.

Switching on for calls, journey by journey.

Try every tool before a customer hears it

Run a tool on its own in a sandbox, then test the workflows that use it.

  • Try a tool

    Run a tool with sample values and see exactly what comes back, in a sandbox where nothing real changes.

  • Test runs

    Workflows that use the tool run like real calls, path by path, before your team approves them.

  • Approve each version

    Approve a workflow when its test runs pass; earlier versions stay on record.

Illustrative, on a fictional product.

What workflows do with each system.

A few of the jobs teams give their tools.

  • Stripe

    Find a customer’s charges, refund a duplicate and check an invoice.

  • Shopify

    Find an order and its status, or cancel it before it ships.

  • HubSpot and Salesforce

    Find the caller’s contact and account, and open or check a ticket or case.

  • Freshdesk

    Add a private note to the customer’s ticket with what was tried.

  • Statuspage

    Check for open incidents first, so callers hear about an outage before they troubleshoot.

  • Your own systems

    Anything your API, database or MCP server offers, reviewed tool by tool: a licence check, a booking, an account status.

Switching on for calls, journey by journey.

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.

Questions

Resolve customer issues on the call.