Skip to main content

​
Pricing and usage

No. The Free plan needs no card and includes 500 replies or 50 voice minutes a month, with real customers as well as in testing. You only need a card to keep answering past that, or to move to a paid plan.
Two things: how much usage is included each month, and how much help you get. Every feature is on every plan, including Free: chat, voice and email, custom API actions, roles, the activity log, analytics and the spend cap. Free also has a limit of 3 agents per workspace; paid plans have no limit.See Plans and limits.
$0.02 per answered chat message or email, and $0.20 per started voice minute. Replies and minutes draw on the same monthly allowance, so one voice minute uses as much as ten replies. Past the allowance, usage is billed at the same rates, up to your spend cap.
No. The allowance resets on the first of each month, on monthly and yearly billing alike.
The agent stops answering billable conversations until the month rolls over, unless you add a card. With a card on file, it keeps going at list rates, up to the spend cap you set.
Yes. Every workspace has a hard monthly cap on what you pay beyond your plan. It is $50 by default, and you can change it. When the cap is reached, the agent stops answering billable conversations until you raise it. See Spend cap.
No. There are no seats on any plan. Ten people working the inbox cost the same as one.
Yes. That answer is a reply like any other, and it counts against your allowance. It is also a signal: an agent that says it a lot has something missing from its knowledge. See The agent says it does not know.

​
The chat widget

Yes. The key identifies the widget. It lets someone chat with that one agent and does not give access to anything else. Three things stop abuse: allowed domains, rate limits on the chat endpoints, and your spend cap. See Security model.
widget.js is about 12 KB gzipped and loads asynchronously. It does not build the chat iframe until a visitor hovers over, focuses, touches or clicks the launcher. On a page where nobody opens the chat, that one small script is all it costs.
Yes. Whether the panel is open is kept for the browser tab, so clicking through to another page does not close a conversation in progress. A visitor who comes back within 24 hours finds the same conversation. After that, they start fresh. They can also choose View recent chats in the panel’s menu to reopen an earlier conversation, or Start a new chat.
Yes, with no JavaScript. Add data-wiredesk-open to any element, or give it a value to type a question in for the visitor: data-wiredesk-open="I need help with billing". From code, call wiredesk("open"). See JavaScript API.
The browser is refusing to show the conversation frame. Either your site’s Content-Security-Policy does not allow frames from https://wiredesk.ai, or the page’s domain is not on the widget’s allowed list. The console names which one. See The chat widget is not showing up.
The allowed-domains list almost certainly has one host and not the other. A bare domain covers its subdomains, but it does not cover a different domain.

​
Integrations

Yes. Connect Zendesk, Freshdesk, HubSpot, Intercom, Help Scout, Gorgias or Odoo under the agent’s Actions › Connections, then add a helpdesk ticket action. When a customer needs a person, the agent opens a ticket there with its summary and the full transcript. It can also answer inside Zendesk itself: connect Zendesk Messaging and it answers first in your Zendesk Web Widget, then passes the chat to your team in Agent Workspace. Stripe, Shopify and Calendly connect too, for billing questions, orders and booking. Salesforce, Zoho Desk and Slack are coming. See Integrations.
Yes, both, and an MCP server, on every plan. Make an API key under Developers → API keys to read and change conversations, contacts, leads and knowledge with the REST API. Add a webhook endpoint under Developers → Webhooks to get new messages, handoff requests, leads and finished conversations on your server as they happen. See Webhooks and MCP server.
Three ways. Export them as CSV, which needs nothing built. Add a webhook for the lead.captured event, so each lead arrives on your server the moment it is captured. Or read them with the REST API on your own schedule.
Yes. An API call action lets the agent call an HTTPS endpoint of yours, such as an order lookup or a stock check, and answer from the response. See API calls.

​
Phone and handoff

No. You keep it and forward it to the agent’s number. Your published number stays with your current carrier.
No. Calls are routed by the number dialled, so each number belongs to one agent. If you want different answers on different lines, give each line its own number.
Yes. Click Preview, at the top of every agent page, and choose the Call tab to talk to the agent in your browser. It does not need a phone number, and it works whether or not the phone channel is on.
The request times out, and the agent tells the customer that nobody was free rather than leaving them waiting. The conversation stays in your history as an unanswered request. See Handoff.
Yes. Your team replies as themselves, and a person’s replies are marked as theirs in the chat.

​
Knowledge and answers

Yes, in chat and email. It replies in the language the customer writes in and switches when they do. Names, prices, addresses and links stay as they are. Your knowledge can stay in English: the agent looks things up in English and answers in the customer’s language. To always use one language, say so in the agent’s instructions, for example “Always reply in English.” Phone calls don’t have this rule yet. The chat widget’s own buttons and messages are in English.
It is told to answer from what it finds in your knowledge and to say when it does not know. If you see a confident answer with no source, it almost always comes from a fact typed into the agent’s instructions. See Fix a wrong answer.
PDF, Word, Excel, CSV, HTML, Numbers, OpenDocument, plain text or Markdown, under Knowledge → Upload a file. See Files.
Usually one of three reasons: the source is still processing, the page could not be reached without a login, or the sentence is buried in a page that is mostly header and footer. A short note that states the fact plainly fixes all three.

​
Team and security

There are three roles:
  • Owner: everything, including billing and deleting the workspace.
  • Admin: agents, knowledge, numbers and the inbox. Not billing.
  • Agent: the inbox and conversations. Cannot change how the agent works.
Only the owner can invite, remove or change the role of people on the team. See Team and roles.
Not yet. SOC 2 is on the roadmap. We do sign a data processing agreement (DPA) with customers who need one; ask through the contact form. In the meantime, we will complete your security questionnaire and walk your team through the architecture. Start at wiredesk.ai/security, and see Security model for how the widget is secured.