Outbound webhooks
Conversation events posted to an endpoint you control. Not built yet — if this is what stands between you and a decision, tell us and it moves up.
We are not trying to become your system of record. Your orders live in your order system, your mail lives on your mail server, and your site is your site. These are the seams where we meet them.
It is the most common support question there is, and in most teams it costs an agent two tabs, a copy-pasted email address and forty seconds of silence in the conversation. Point us at the order API you already run, map its fields onto ours once, and your agent sees the customer's orders in a panel beside the chat.
Every order API in the world names its fields differently — order_no,
orderId, reference. Rather than making you write a
transform, we show you a real response from your endpoint and you pick which
of its fields is the order ID, which is the status, which is the customer's
email. Anything left over is kept in an extras bucket, so information is
never silently thrown away because nobody thought to map it.
Short list, on purpose. Each of these is something a real team asked for twice.
Bring the mailbox you already own. We sync its folders and send replies through your own server, from your own domain — no forwarding address, no rewritten From line.
Shared inboxThe companion app wakes an agent when a conversation needs them, so nobody has to keep a browser tab open to stay on shift.
Mobile appOne global, three methods — open it, close it, read its resolved config. Wire your own “Need help?” button to it. That is the whole surface, and we would rather it stayed small than grew into something you cannot rely on.
JavaScript APIThe same script tag and the same token serve every whitelisted domain and subdomain in your workspace. Adding a site is a dashboard action, not a second install.
Multi-domain routingConversation events posted to an endpoint you control. Not built yet — if this is what stands between you and a decision, tell us and it moves up.
Read conversations and push messages from your own systems. There is a versioned JSON API behind the mobile app today; opening it publicly means committing to it, and we would rather do that once.
Tell us what you are connecting to. We have built an integration off a single well-argued email before.
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.