Without an integration he answers everything that is on your site and in your documents. With an integration he also answers the questions you currently have to dive into a system for: where that order is, whether that size is still in stock, when you have time. Below, per system, what he fetches, what he never sees, and whether it is standard or custom.
Order status, track & trace, stock per variant and delivery times — live from your shop, with read-only access. The only integration for which nothing needs to be built.
To the Shopify page →Qualified leads land in HubSpot as a contact, with the full conversation as a note underneath. Your sales team knows what was discussed before they call.
Recognises which company is visiting your site, even without a completed form. The agent has the conversation, LeadInfo tells you who was on the other end.
More about LeadInfo →This is where most of the return is: "where is my order" is the most asked question in almost every webshop, and the only one a good FAQ cannot catch.
Fetches Order status, track & trace, stock per variant, product information and prices.
The only integration that is ready-made: no custom build, no separate quote. Runs through the Admin API with read-only access. You create a custom app in your own admin and give us the token — no app from the App Store, no developer, no change to your theme.
More about this →Fetches Order status, stock and product information via the WooCommerce REST API.
Technically doable, but every WooCommerce shop is put together differently. We look case by case at what can be pulled out and quote that separately.
Fetches Orders, items and stock.
Case by case, depending on which Lightspeed version you run and which API comes with it.
Fetches Orders, catalogue and stock.
A heavier integration than the rest, so always a conversation with your technical administrator first before we name a price.
Fetches Whatever your API returns: status, shipping information, returns route.
We do this more often than you would think. If your system has a REST endpoint that returns an order by order number plus email address, we hook the agent up to it. Runs like this today at a customer with their own order system.
A conversation that goes well ends with a name and an email address. Those do not belong in a chat log but in the system your sales team already works in.
Fetches New contacts and deals, plus the conversation as a note on the right contact.
The integration we get asked for most. A lead the agent qualifies lands in HubSpot as a contact, with the full conversation underneath — so your sales team sees what was discussed before they call.
Fetches People, organisations and deals in the right pipeline.
Same principle as HubSpot. We agree up front at which stage a lead comes in, so your forecast is not polluted with conversations that are not about anything yet.
Fetches Every qualified lead as JSON to an endpoint you point us to.
If you are on a CRM we do not know, or on something home-built, we send the lead as a webhook. That is how our own CRM works too — exactly the same route.
Fetches The company name behind anonymous website traffic.
LeadInfo recognises which company is visiting your site, even when nobody fills in a form. Next to the AI employee that is a strong combination: he has the conversation, LeadInfo tells you who was on the other end. Separate licence from LeadInfo itself; we set up the integration and the follow-up.
More about this →Fetches A tidy summary of the conversation plus the contact details.
The simplest form, and included in every plan. No CRM needed: you simply get an email as soon as someone wants something from you.
The same AI employee, the same knowledge, in the places where your customers already talk to you.
Fetches One line of script in your theme or via your tag manager.
Loads only after your page is ready, so your speed scores do not notice a thing. Colours, name and avatar are yours.
Fetches Messages on your Facebook page.
Connected to your Facebook page via the official Meta route. Runs today at Dutch Triathlon Series, among others.
Fetches Direct messages on your business Instagram account.
For webshops often the busiest channel after the website: people see something in your feed and ask straight away.
Fetches —
It is planned, but until it is there we do not promise it. Existing customers get this channel first.
For those who have appointments rather than orders: a conversation that goes well ends in your calendar instead of in a callback request.
Fetches Your availability and a booking link at the right moment in the conversation.
What we use ourselves. The agent recognises when someone wants an appointment and sends the link — he does not push it into every conversation.
Fetches The same, but with your Calendly link.
Works exactly like Cal.com. Runs like this today at a customer with a guided-tour calendar.
Fetches Free slots, and the appointment in it.
Usually easiest via Cal.com or Calendly, which are already hooked up to it. Direct is possible too; we quote that separately.
Fetches Availability and appointments.
Case by case, depending on how your tenant is set up and what your administrator is allowed to approve.
An integration fetches data. Knowledge is something else: that is everything he needs to know to answer a question without making anything up.
Fetches Every page, indexed automatically.
The foundation of every AI employee, and of the free trial version. When your site changes, we index again.
Fetches PDF, Word, price lists, returns and shipping policy, internal FAQ.
Everything that is not on your site but is correct. This is usually the difference between an agent that sounds nice and an agent you dare to switch on.
Fetches An export or a periodic sync.
If your team works in Notion or another knowledge base, we can use that as the source instead of loose documents.
The most important quality of a good AI employee is that he knows when to stop. This is what happens then.
Fetches The conversation, with all its context, in the dashboard.
Your colleague takes over the conversation live and types on themselves. If it goes quiet afterwards, the agent picks it up again — so the customer is never left waiting in a void.
Fetches An email as soon as a lead comes in or someone asks for a human.
To a personal address or a shared inbox. Works with every email provider.
Fetches A message in the channel your team is in anyway.
Handy if customer questions already pass through a channel today. Via webhook, so quick to arrange.
If your system is not listed, this is usually the route. Anything with an API or a webhook can be connected — the only question is what it costs.
Fetches Leads and conversation data as a trigger for your own scenarios.
The fastest way to hook the agent up to something we have no integration for. You build the scenario, we provide the webhook.
Fetches The same, for those already working in Zapier.
Same principle as Make. Which of the two does not matter to us — pick what your team already knows.
Fetches JSON in, JSON out, on an endpoint you point us to.
The raw variant, without a middle layer. That is how the order integration with a custom order system works too. We write the tool description so the agent uses it at the right moment, and no more often than that.
Fetches Every conversation, readable at portal.visstick.ai.
Not an integration, but the reason you dare to switch on the others: you see exactly what he said, what he looked up and where customers get stuck.
Every integration above is read-only by default. That is not a technical limitation but a choice: an AI that gets an answer wrong costs you a correction, an AI that gets a cancellation or a refund wrong costs you a customer.
If you do want a write action — booking an appointment, writing away a lead — we agree exactly which ones up front, and build a confirmation step around them. And what he is not sure of, he does not say: then he brings in your team, with the whole context of the conversation underneath.
The Shopify integration is part of the Growth plan (€295 per month) and does not need to be built; setting it up is part of that plan’s setup, for which we agree a fixed price up front. Everything marked "on request" we quote separately, also with a fixed price up front — never billed by the hour. The amount depends on how well your system is documented; a modern REST API is a day’s work, a system without documentation is a week. What each plan includes is at /en/prijzen/vergelijken.
Just ask. If it has an API or can send a webhook, it is almost always possible. If it cannot, we say so straight away instead of turning it into a project.
Read-only by default. That is a deliberate choice: an AI that gets an answer wrong is annoying, an AI that gets a cancellation or a refund wrong is a problem. If you do want a write action — booking an appointment, for example — we agree exactly which ones up front, and build a confirmation step around them.
The agent fetches what he needs per question and keeps no copy of your catalogue or your customer base. Conversations live in your own environment in the dashboard. We work in line with the GDPR and sign a data processing agreement; it is available for download at the bottom of every page.
Then he says so honestly — "I can’t look up your order right now" — and offers to put you through to your team. He does not invent a status. You see it back in the dashboard.
Twenty minutes, online. Tell me where your data lives and what your customers ask, and I will tell you honestly whether there is an integration in it — and if so, roughly what it costs.
Book 20 minutes with DennisOnline · no obligations · no sales pitch
Shopify 
HubSpot 
LeadInfo 
