Does it work with yours?
Taiwa runs inside your existing call console. Nothing migrates, nothing is replaced. Here are the seven it runs in — and the desktop app for the calls that aren't in a browser.
Supported platforms
Aircall
Runs in the Aircall workspace. Both legs translated.
Amazon Connect
Runs in the Amazon Connect agent workspace. Both legs translated.
Freshdesk / Freshworks
Runs in the Freshworks agent console, on Freshcaller. Both legs translated.
HubSpot
Runs in the HubSpot call console, across Sales Hub and Service Hub. Both legs translated.
Intercom
Runs in the Intercom Inbox, on Intercom's calling. Both legs translated.
Twilio
Runs in a Twilio-powered call console using the Voice SDK. Both legs translated.
Zendesk
Runs in the call console inside Zendesk, on both Zendesk Talk/Voice and Zendesk for Contact Centre. Both call legs translated.
It also reads the ticket's language field when you turn that on, so the customer's language comes from the ticket rather than being guessed at from the first thing they say. That's the one place Taiwa does something on Zendesk it can't do anywhere else, and it's there because the language was already sitting in the ticket.
Seven platforms, all fully supported — both call legs translated on every one.
Not a browser console?
Microsoft Teams, Zoom and softphones are applications rather than web pages. The Windows desktop app translates calls in those — both legs, the same languages, the same account.
A Mac app is coming. Until then, the browser extension runs in Chrome on a Mac.
The desktop app →Why not every platform?
Most call consoles work in a similar way, with minor differences in how they expose the call's audio to the browser. We test each one properly before we list it as supported — we won't claim a platform we haven't made a real call on. If yours isn't one of the seven, tell us — or look at the desktop app, which doesn't depend on the console at all.
Running one of these?
Work out what it's costing you today. It'll tell you if this isn't worth it.