A bot that does not know your stock lies to your customer. Which is why integration is not an added feature — it is the condition for the reply being true.
Most sites show an undifferentiated wall of logos, and the buyer discovers on first use that half of it is not built. We write plainly what is ready today and what is built on request — and the second is not a flaw, because every installation of ours is built by hand anyway.
Reads: products, prices, stock, order status.
Writes: a new order, updated customer details, tagging the conversation with the order number.
Useful for: “how much is this?” and “where is my order?” — the two most common questions in any store.
Reads: The product catalogue and what is in stock, and shipping status.
Writes: Updating the order, and conversation notes on the customer record.
Useful for: Stopping it promising a product that has run out of stock.
For anyone running prices and stock in a spreadsheet. The system reads the sheet and writes new leads and issued quotes back into it.
Useful for: A connection in one day instead of waiting for a full system.
Every event reaches you in real time: message.received · lead.qualified · quote.issued · handoff.requested.
Useful for: connect any internal system of yours without waiting for us. Technical details.
No wall of logos. Every platform here is classified by its real status, and there are three statuses, not two: 5 ready today,35 has a documented public API and is built on request, and9 has no public API, so connecting it goes through the provider itself. That last one is what other sites hide, and it is what you discover after paying.
The governing rule: any system with a documented API, we can connect to. The list above is what we have built or verified the documentation of — not the limit of what we can do. Your business uses a system not listed? Send us its documentation link and we will reply with a duration and a cost.
About names and marks: every name and mark here belongs to its owner, and is mentioned solely to identify the integration. And a drawn mark appears only on a platform whose integration is actually built; everything else is a letter set in the site’s own typeface. Neither the mention nor the mark implies partnership, endorsement or sponsorship by any of these parties.
| Case | Naateq’s behaviour |
|---|---|
| The external system does not respond | It does not guess the price or availability. It says it will check and escalates to you. |
| The product is not in the catalogue | It asks the customer to clarify instead of inventing a close match. |
| A conflict between the stored price and the live price | It always takes the live one, and logs the conflict in the dashboard. |
| A prolonged outage | An alert in the dashboard, and an automatic switch to “reply without price commitment” mode. |
This behaviour is governed by code — it does not depend on the model behaving sensibly.
All names and marks shown here belong to their owners, and are shown to state technical compatibility only — implying no partnership, sponsorship or endorsement by any of them. And the status of each integration is written on its tile: “Ready now” for what is built and tested, and“Built on request” for what is not built yet.
If it has an API, chances are we can connect it. Tell us about it in the discovery session.