Analytics that wait for your consent
We added analytics to our marketing site, and built the consent gate before we added the tags.
- Nothing loads until a visitor opts in.
- None of it runs inside the chat widget on your site.
A running record of what we have shipped, in plain language and in the order it happened. Everything on this page is live in the product today, not a promise.
We added analytics to our marketing site, and built the consent gate before we added the tags.
The agent decides on its own when to offer a human, and you set the hours you are actually around.
A full rebuild of the conversation surface: floating controls, a composer that grows, and an expand button that works.
The screen visitors see before they start chatting is now a stack of blocks you arrange yourself.
Paste a URL and we scan the site, show you exactly what we found, and configure the agent from it.
Every surface in the widget now follows its theme, including formatted answers, menus and status colors.
Voice moved onto a pipeline running the same brain as text, so calls use your knowledge, tools and history.
Your agent answers on Telegram, and those conversations land in the same inbox as everything else.
One panel for adding anything, plain text as a real source, and pages that refresh themselves.
Weekly by default, nothing sent when there is nothing to report, and one-click unsubscribe on everything.
One-click Google sign-in on both auth screens, and the marketing site opened to the public.
The dashboard rebuilt on a warmer, quieter design system, with new navigation for working on a single agent.
Store connections moved to one workspace hub, and the agent gained real store actions.
Plan changes, usage meters, invoices and payment recovery all moved into the dashboard.
AI Actions let the agent call your own APIs and connected apps in the middle of a conversation.
The builder's navigation cut from fourteen pages to ten, split into what you set up and what you run daily.
New accounts confirm their address, and every email we send now shares a single branded shell.
Install the widget on WordPress without touching a theme file, with WooCommerce support built in.
A rebuilt retrieval pipeline that finds the right passage more often, and says so when it cannot.
Route handoffs and leads into Slack channels, and connect the rest of your stack through Zapier.
A documented REST API for your data, and signed webhooks the moment something happens.
One visual language across the dashboard, and eleven templates to start a new agent from.
Visitors rate answers, you correct them from the inbox, and the agent replies in the visitor's language.
Optional feedback when a message lands: a haptic tap, or one of ten sound themes.
Self-serve signup, invitations with roles, and support for belonging to several workspaces.
The widget learned to speak, with a voice you choose and an optional spoken greeting.
Take a conversation over from the AI, hand it back when you are done, and track the leads that come out of it.
A metrics page, in-chat tools you switch on individually, and the first booking card.
Agent personality and rules in one clear form, with a test panel sitting beside it.
More ways to get content in, and a widget that opens as a swipeable sheet on phones.
Preview a source before it is indexed, and manage the individual passages afterwards.
Configuration split into clear steps, and the knowledge base got a real management screen.
Ingestion, embeddings and retrieval came together into something that could answer a real question.
The first commit: accounts, a dashboard, agent management and billing.
No dates. These are the things actually in progress right now, and they ship when they are right rather than when a roadmap said they would.
Take a handoff and reply from your phone, with a push notification when someone is waiting.
Telegram is live today. The Meta channels are built and waiting on app review.
The agent checks real availability, books the meeting, and handles reschedules and cancellations.
Install from the App Store in one click, rather than following a setup guide.
Uptime and incident history, so you never have to ask us whether something is down.
Taking the widget through WCAG 2.1 AA properly, rather than claiming it and hoping.
No credit card · Live in a day · Cancel any time