An FAQ is where you check whether the rest of the site was honest, so it is the worst page to oversell on. Where we have not built something, it says so — with a link to tell us if that is the thing standing between you and a decision.
One script tag before </body>, on any page or in your site template. The widget appears as soon as the domain it is running on has been approved.
So that a copy of your snippet cannot start answering as your brand on a site you have never heard of. You submit a domain, it is reviewed, and then the widget answers there — same snippet, same token.
Once, to paste the snippet. Everything after that — colour, copy, position, business hours, the pre-chat form, routing — is a dashboard setting and needs no redeploy of your site.
Yes. The free trial needs no card details. The pricing page shows the trial length and what the free tier includes.
Yes, and that is rather the point. Every domain and subdomain in your workspace shares one token and one bill — see Routing & teams.
Plans are built around published limits — agents, domains, conversations, concurrent chats — rather than a per-seat licence. The exact limits for each tier are on the pricing page.
No. Domains count against your plan’s limits; they are not a separate line item, and there is no per-brand workspace to buy.
Yes, from the billing section of your dashboard. You can switch tiers or cancel; there is no notice period to serve.
The same plan, billed once a year at a discount. The pricing page shows both figures side by side — toggle the switch above the plans.
Volume pricing, custom limits and the compliance conversation. It is a “talk to us” tier because the answer genuinely depends on your situation, not because we are hiding the price of the normal ones.
No. Someone who opens the widget is queued for a human. Canned responses, quick-reply chips and routing make your agents faster; they are not a substitute for one.
It is a gated feature: your plan has to include it, and then your company admin switches it on for the widget. Both have to be true before a call button appears. See Voice calling.
Yes — any IMAP/SMTP mailbox you already own. Replies leave through your own server from your own address. See Shared inbox.
It depends on your plan; the free tier keeps a few days and paid plans keep it indefinitely. Your billing page shows the figure that applies to your workspace.
Not publicly, yet. There is a versioned JSON API behind the mobile app, and opening it publicly means committing to it — which we would rather do once, properly. Outbound webhooks are on the roadmap. If either is what stands between you and a decision, tell us and it moves up.
Yes, with three methods on one global: ATWChat.open(), ATWChat.close() and ATWChat.config(). That is the whole surface — see the docs.
Yes, in private beta — it is not on the stores yet. See Mobile app and ask us for access.
Before a visitor clicks the launcher there is no session, no heartbeat, no polling loop and no WebSocket — just a bubble painted from config that arrived inlined with the snippet. The connection opens on the first click.
It is designed not to. In particular the widget registers no beforeunload handler, which is the thing that quietly disables the back/forward cache for an entire page in Chrome and Firefox and turns every back-navigation into a full reload.
The widget falls back to polling so the conversation still works. The fallback engages only when it is needed, so the common path never pays for it.
Usually. Media prefers UDP where it is available and falls back to TCP, and there is a TURN relay over TLS for networks that block UDP outright.
Every query is scoped to your workspace at the ORM layer, with row-level checks on top. Details are on the security page.
TLS 1.2+ in transit on every endpoint, AES-256 at rest for the database and backups. Passwords are hashed with Argon2.
Yes. Invites, assignments, suspensions and billing changes are recorded in an immutable activity log, scoped to your workspace.
Recording can be enabled, and recordings are held at the platform level — agents and company admins have no access to them. A recording your whole support team can replay is a liability, not a feature.
A DPA is available on request, and the same data-rights flow covers CCPA. SOC 2 Type II is in progress — the security page has the current status rather than a badge we have not earned.
Their address lands on a suppression list your agents cannot override, and it is enforced server-side rather than as a UI convention.
The chat bubble in the corner of this page is our own widget, running on the same product you are reading about. Or use the contact form.
Talk to us. Moving from another tool is mostly a matter of getting your domains, agents and canned responses across, and we would rather help than have you do it badly and blame the product.
Very much. We have already rewritten pages of this site because they described features that did not exist. If you find another, tell us.
A small, self-funded product team headquartered in Bengaluru, India, with engineers across three time zones. More on the about page.
The chat bubble in the corner of this page is our own widget, running the product you have been reading about. Use it — that is rather the point.
Pick the categories you're comfortable with. Essential is always on — everything else is yours to decide. See our cookie policy.
Session, security and CSRF cookies. Needed to keep you signed in and the site secure — there's no version of the site that works without them.
Remembers small things — billing cycle preference, last viewed plan. Disabling makes the site slightly less smart, never broken.
Anonymous, aggregated visit data — which pages get read, which features get clicked. We use this only to decide what to build next.
Attribution for ad campaigns and remarketing pixels. Off by default — enable only if you don't mind retargeting.