Get started

Products and how they fit

Texa Desk, Texa AI, the Texa API, the widgets, the mobile app and the Texa Relay, and which one you build on.

The parts

Product	What it is	What you build with it
Texa Desk	The helpdesk your team works in, on the web at `https://desk.texadesk.com` and in the iPhone and Android app. Inboxes for WhatsApp, email, phone, SMS, live chat, Facebook, Instagram, Telegram and more; contacts, teams, labels, tickets, the help centre, campaigns and reports	The Texa Desk API, its webhooks, agent bots, dashboard apps, your own channel
Texa AI	The agent that answers customers on every channel, follows the procedures your team approved, runs actions in your systems and hands over to people. Set up in Texa Desk under Texa AI	Everything below reaches it
The Texa API	Texa AI as a service for your own software, at `https://api.texadesk.com/v1`	Conversations, events, actions, voice
The website widget and app components	Texa AI as a chat in your website (`widget.js`) and app (`@texadesk/react-native`, Flutter soon), for visitors and signed-in customers	Your website and app
Live chat	Texa Desk's own chat bubble for your website, answered by your team and Texa AI	Live chat, the WordPress plugin
Connectors	Texa AI's way into your systems: ready-made (Paystack, Flutterwave, Shopify…), your API, your server, MCP	Actions, connectors
The Texa Relay	A small program that runs inside a bank's network and answers Texa AI's lookups without data or credentials leaving it	The Texa Relay
The customer portal	Your help centre's "My requests": customers follow and answer their tickets, on the web or in your app	Customer portal
SDKs	Python, JavaScript and TypeScript, React Native, Go, Swift and PHP	SDKs

How a message flows

Text

 customer ─▶ WhatsApp / email / phone / live chat ─▶ Texa Desk inbox
                                                        │
                                       Texa AI answers ─┤─▶ actions in your systems
                                                        │   (connectors, your server, the Relay)
                                   needs a person? ─────┴─▶ your team, in Texa Desk

 your app ─▶ Texa API (or the widget) ─▶ Texa AI ─▶ events back to your app and webhooks
                                            └── handover ─▶ "App conversations" inbox in Texa Desk

Customers who reach you on a channel (WhatsApp, email, a call) land in a Texa Desk inbox. Texa AI answers there if it's on for that inbox. You extend this with the Texa Desk API and webhooks.
Customers who use your own app or website reach Texa AI through the Texa API or the widget. Your app shows the replies. When a person is needed, the conversation appears in Texa Desk.
Either way, actions go to your systems the same way, and every conversation is in one place for your team.

Which one do I use?

"I want Texa AI to answer inside my app." The widget or app component if you want our chat; the Texa API if you're drawing your own.
"I want to read every conversation into my data warehouse." Texa Desk webhooks and the Application API.
"I want Texa AI to check a customer's transfer." An action, through a connector or your own server.
"Our data can't leave our network." The Texa Relay, and a dedicated instance if the whole system must be in your country.
"We already use Zendesk." Texa AI inside your helpdesk.