Connecting to the store is a condition for correct replies. What the system reads from your store, what it can't, and how to test it before it faces a customer.
· 14 min read
“How much is this? Do you have it in L? Where's my shipment?” These are the most common questions an online store gets on WhatsApp. Answering them needs your store's data at the moment of the question, and saved text isn't enough.
That's why connecting to the store is a requirement for a correct reply. A system that doesn't read your stock may promise your customer a product that's sold out.
The technical connection takes Hours, and most of the time goes into gathering your business knowledge: products, prices and common questions. With Naateq, the agent is live within 24 hours of receiving it, and the Salla or Zid connection is built on request.
«Is size 42 in stock?»
Product · price · stock · order status
In stock · SAR 235 · arrives in two days
The whole difference is in the second step: a system that doesn't read your stock replies “we'll get back to you,” and that reply does nothing for the customer.
Saying “connected to Salla” isn't enough. Ask which fields the system reads, and when: at the moment of the reply, or from a copy saved hours earlier? Each field answers a type of question:
| What is read | The question it resolves | If it is not read |
|---|---|---|
| The product, its options and current price | “How much is this?” | An expired price, or the price of a different option |
| Stock per option | “Do you have size L?” | A promise of a size that's sold out |
| Order and shipment status | “Where's my order? When will it arrive?” | Every follow-up question gets handed to you |
| Return policy | “Can I return it?” | It invents a policy that binds you |
The last column is what happens without a connection: the system gives a wrong answer, and the customer thinks they got an answer.
Where systems go wrong most is the second row: many of them read “is the product available” but don't read what is available of each option. So it says “available” for a shirt whose requested size is sold out, and the reply looks completely correct.
Most integrations in the market only read. That covers ninety percent of what you need, and it's also the safest option.
Whereas writing, like editing an order, issuing an invoice or applying a discount, it needs a higher permission, along with a fixed rule that stops the system from doing it without your approval. A system with write permission and no rule may give a discount just because a customer kept pushing.
The contract, and any discount outside the limits you set, only reach the customer after you approve it. The system prepares it and sends it up to you, and you approve or reject it. A quote, on the other hand, goes out directly with numbers from your price list.
Connecting to the Salla or Zid API is technical work that's done in hours. The long part is agreeing on what the system says and what it does not.
That includes: collecting the frequent questions from your customers' past conversations, return and shipping policies worded so they can't be read two ways, discount limits, when it hands over to you, and what it says when it doesn't know.
An offer that skips this part gives you a system that gives generic answers. With Naateq, we ask you for this information first, and the agent goes live within 24 hours of receiving it, and any later changes to it are free.
Once the system is running, the question becomes “How many conversations ended without me touching them?”. That number tells you whether the investment is paying off.
The second number: where did the customer come from? One link for every platform gives you a report with no source. A tagged link for each channel tells you, in numbers, whether Snapchat is worth your time.
And before integrating at all, settle which category you need in The difference between a WhatsApp bot and an AI agent, and read about the safety of your number in can a WhatsApp number be banned for using automated replies.
Some systems pull products once an hour to reduce load, so the old price keeps showing after you launch a new offer. Ask: how old is the oldest number the system might state?
“Black abaya” and “Classic black abaya,” so the system picks the first and answers with its price. The fix is in the naming: give each product a name that clearly sets it apart from the others.
Drafts, hidden and deleted products: if the connection reads them as they are, the system shows your customer things you decided not to show. Ask for it to read published products only.
A system that can edit orders when you don't need that adds risk with no benefit. Grant the smallest permission that gets the job done, and raise it when you need to.
Don't hand the system to your customers until it passes these messages. You can send them all from your phone to the system's number in ten minutes, and each one checks a common connection mistake.
| Send | The correct reply |
|---|---|
| A question about a product that just sold out | “Not available” |
| A question about one specific size | The status of that size only |
| A question about a product you discounted minutes ago | The new price |
| Asking for a discount insistently, three times | The same limit every time |
| A valid order number | Its state and delivery date |
| A wrong order number | “I couldn't find an order with that number” |
| Another customer's order number | A refusal with no data at all |
| The name of a product you do not sell | “We don't sell it,” with no made-up suggestion |
| A request for a formal quote | A document with a number and a date |
A system that gives order details to someone who doesn't own the order is leaking your customers' data. Keeping each customer's data separate from everyone else's has to be built into the system itself, not left as an option in its settings. If it fails this test, don't launch it, however well it does on the rest.
Once it passes them all, read about what could threaten your number itself in can a WhatsApp number be banned for using automated replies.
Products and their prices, available stock, and order and shipping status. With these it replies with the right number instead of “we'll get back to you after checking.” A system that doesn't read your stock may promise your customer a product that's sold out.
Reading and writing are two different permissions, and many systems only read, so read the offer carefully. Writing (editing an order, issuing an invoice) needs a higher permission and a rule that stops the system from doing it without your approval.
The technical connection takes hours. The longer part is preparing your business knowledge: your products, your customers' common questions, and what the system should and shouldn't say. With Naateq, the agent is live within 24 hours of receiving your business data, and the Salla or Zid connection is built on request.
Choosing a system
A WhatsApp bot replies with pre-written text, while an agent decides and acts. The difference shows in the price: a bot reply costs $0.01 to $0.10, and an agent conversation $0.30 to $2.00.
Running and connecting
Connecting through your current number is faster, but it's unofficial and exposes the number to a ban. The difference between the two routes, the behavior that raises the chance of a ban, and what you lose if it happens.