Stores

Connect Salla to WhatsApp (2026): an AI bot, order confirmation and cart reminders

12 min read Updated 17 September 2026 ArabyBot team Salla · WhatsApp Cloud API
أهلًا نورة 👋 وصلنا طلبك رقم 2231: عباية كلوش سوداء مقاس 56 — 320 ريال، والتوصيل للرياض مجاني. نأكّد ونشحن؟
أكّد الطلب ✅عدّل العنوانألغِ
Sent automatically from the "new order" event in Salla
أكّد الطلب ✅ بس متى يوصل؟ أبغاه قبل الخميس
تم تأكيده 🌹 الشحن للرياض يومين عمل، فيوصلك الثلاثاء أو الأربعاء قبل الخميس بإذن الله. وراح أرسل لك رقم التتبع أول ما يطلع من المستودع.
ممتاز. وعندكم نفس العباية لون كحلي؟
إيه، الكحلي متوفر مقاس 54 و56، باقي منه 3 قطع. أرسل لك صورته؟ Read from the Salla catalogue at the moment of asking — colour, size, stock

The short answer

From the Salla app store: install the ArabyBot app and approve it once from your store dashboard, and your products, stock and orders reach us from Salla itself the moment they happen. The bot then confirms orders, sends shipping status, chases the abandoned cart and answers "in stock?" and "where is my order?" from your live store rather than a copy — in Saudi dialect.

What runs automatically after the connection — in one table

The Salla connection is not one button but five things that start working after it, each with a different sender and a different cost at Meta. A merchant should read this table before anything else, because the difference between a message you start and one the customer starts is the difference between halalas and zero.

What runs after connecting Salla to WhatsApp, and its cost
ItemWhat happensWho starts itCost to a Saudi number
Order confirmationA message with "confirm / edit / cancel" buttons the moment the order is created; its status is written back to SallaYou (utility template)about 4 halalas
Shipping status"Shipped" with the tracking number, then "delivered" and a review requestYou (utility template)about 4 halalas each
Abandoned cartThree messages on your timing, stopping the moment they buyYou (marketing template)Marketing rate — not yet billed to us for Saudi Arabia, so not published
Customer questions"In stock?", "how much?" and "where is my order?" from the live catalogue, stock and ordersThe customerZero
Ordering inside the chatThe agent collects product, option and address, opens the order in Salla and sends the payment linkThe customerZero

Meta's cost on our accounts ÷ its message countsample 120 daysmeasured 5 September 2026

The steps to connect Salla to WhatsApp

The whole connection runs from two dashboards: ArabyBot's and Salla's. The usual time is under an hour, and the longest part is neither ours nor Salla's but Meta's: approving the first template.

  1. Create the account and connect a WhatsApp number

    Sign up with no card and no sales call, then connect the number through the official WhatsApp Cloud API from inside the dashboard. A Saudi +966 number is accepted like any other. If your number currently runs on the WhatsApp Business app, move it with coexistence mode and keep your chats and contacts — or use a new number. You need a Meta business account; verification with the commercial register opens the higher sending tiers later and does not stop you starting.

  2. Install the ArabyBot app from the Salla app store

    From the Salla dashboard: Apps → App store → ArabyBot → Install. You will see the permissions the app asks for: reading products, stock, orders and customers, and writing order status. No permission to edit prices or products, deliberately.

  3. Approve once from your store dashboard

    The approval links the store to your ArabyBot account and opens the event channel: every new order, every status change and every abandoned cart reaches us from Salla itself the moment it happens. Check the store name at the top of the dashboard before approving if you own more than one store.

  4. Choose what to automate and get the templates approved

    Turn on order confirmation (for all orders or cash on delivery only), shipping status, and the abandoned cart with its timing. Each has a ready Arabic template that is sent to Meta for approval; utility ones are usually approved the same day. Do not turn confirmation on before its template is approved — that is mistake number one in the list below.

  5. Create the AI agent and answer its questions

    How products are ordered, how they ship and delivery times per city, the return policy, and when to hand to a person. The agent builds its operating rules from your answers and reads products from Salla directly, so you upload no catalogue. Set the dialect to Gulf or auto.

  6. Test with five messages, then go live

    From your phone as your customer writes: «وش سعر الشحن لجدة؟» — «متوفر مقاس 54 كحلي؟» — a voice note about returns — «وين طلبي؟» with a real order number — then create a test order in Salla and see whether the confirmation arrived with its buttons and whether the order status changed when pressed. Watch the first two days from the app.

What runs automatically — in detail

Order confirmation before dispatch

The moment an order is created in Salla the customer receives a message with the order summary and three buttons: confirm, edit address, cancel. Pressing confirm writes the status into Salla; pressing cancel stops the order before you pay a courier. Most Salla stores are prepaid, so a paid order needs a receipt more than a confirmation; the real value is in cash-on-delivery orders, where the unconfirmed order is the one that returns. That is why confirmation can be limited to one payment method. The difference between confirming on WhatsApp and by phone call is in the store-connection guide.

Shipping status and the review request

When the order status in Salla changes to "shipped" the customer gets a message with the tracking number, and when it becomes "delivered" a message asking about their experience. These messages turn «وين طلبي؟» — the most common question any store receives — from a conversation the customer starts anxiously into a message that reached them before they asked. They are utility templates at the halala rate, not marketing.

The abandoned-cart reminder

The cart reaches us from Salla's own event, so the follow-up starts from an accurate signal rather than tracking we build. Three messages on your timing — after an hour, a day and three days, say — carry the abandoned products and the checkout link, and all stop the moment they buy. It is a marketing template at Meta, the dearest category, so make it three rather than ten: the fourth follow-up costs you money and quality rating together.

AI answers from the live catalogue

The agent keeps no copy of your catalogue; it asks Salla at the moment of the customer's question: searches by name, opens the product page, reads price, options, photos and stock, and reads an order's status by its number. So when a customer asks «متوفر اللون الكحلي مقاس 54؟» it reads the stock of that exact combination and sends its photo, not the first one. What it cannot find it does not invent: it says it is unavailable and offers an alternative or hands over. One limit to know: a product with several option axes shows its card at the base price, with stock read per combination. The full explanation is in the agent reads your store.

Six mistakes that break the connection — and we see them every week

  1. Turning confirmation on before the template is approvedOrders arrive from Salla and the message is not sent because Meta has not approved the template yet, so the merchant concludes the connection is broken. Wait for "approved" on the template before switching on — utility ones are usually approved the same day.
  2. The number is still active on the WhatsApp appThe WhatsApp Cloud API refuses a number that is simultaneously running on the app. Either move it with coexistence mode from inside the dashboard, delete it from the app and then register it, or use a new number. Uninstalling the app from the phone alone is not enough; deleting the account from inside WhatsApp's settings is what is needed.
  3. Approving from the wrong store, or from a staff account without permissionA merchant with two stores approves while logged into the other one, and receives orders from the store they did not want. Or a staff member approves from an account without app permissions and the approval is silently refused. Approve from the owner account, and check the store name at the top of the dashboard.
  4. A cart reminder to someone who did not consent to be contactedA customer who entered their number without clear consent wording reports the message, and a handful of reports lower the number's quality rating and its sending limit. Add consent wording at checkout, and put a way to stop inside the message. What the data-protection law means here is in the PDPL guide.
  5. Expecting the bot to edit products or pricesThe connection reads the catalogue and writes order status only. A merchant who asks the bot to "change the abaya's price" or "add a product" will not find that, deliberately: editing happens in the Salla dashboard alone, and the bot reads the change that instant.
  6. An unverified business account, then a wide broadcastAn unverified account at Meta runs with a limited daily allowance for conversations you start. A merchant running confirmation, shipping and cart together on a sale day hits it before noon and the messages wait until tomorrow. Verify the business with the commercial register early; the higher tiers open gradually with sending quality. Your replies to people who wrote to you are unlimited.

The cost in riyals — a worked example

A Salla store receiving 500 orders a month with confirmation and shipping status on: 500 confirmations + 500 "shipped" + 500 "delivered" = 1,500 utility messages × 4 halalas ≈ 60 riyals from Meta a month. Customer questions about sizes, delivery and returns — however many — are started by customers and cost zero. With the ArabyBot subscription (120 riyals for the WhatsApp plan) the total is about 180 riyals a month for everything on this page, except the abandoned cart whose Saudi rate we do not publish because we have not been billed for it yet. Full rates and a calculator are on WhatsApp API pricing in Saudi Arabia.

From 1 October 2026

Meta starts billing service messages — your free-form replies to whoever wrote to you — beyond 1,000 free per number per month. A Salla store answering fewer than a thousand customers a month from one number sees no change. Details and figures.

Frequently asked questions

1

Does connecting Salla to WhatsApp need code or a developer?

No. You install the ArabyBot app from the Salla app store and approve it once from your store dashboard — no key to copy and no line to add to your theme. Order and cart events reach us from Salla itself the moment they happen, so we are not polling your store every minute.

2

Does the bot edit my prices or products in Salla?

No. The connection reads the catalogue, stock and orders and writes order status only (confirmed, cancelled). It changes no price, description or stock. What you see in the Salla dashboard is what the customer sees in the chat at that moment.

3

What does a WhatsApp order-confirmation message cost to a Saudi customer?

An order confirmation is a utility template you start, costing $0.0107 to a Saudi number — about 4 halalas, i.e. 40 riyals per thousand orders — measured on Meta's actual cost. The customer's "confirm" and anything after it is free. Meta's fees are billed to your own account with no markup from us, and the subscription is separate: the WhatsApp plan from 120 riyals a month.

4

Is an abandoned-cart reminder on WhatsApp allowed in Saudi Arabia?

Yes, on two conditions: the customer gave their number and consent to be contacted — which happens when the number is entered at checkout with clear consent wording — and the message carries a way to stop. A cart message is a marketing template at Meta, and what the Personal Data Protection Law means for it is in the PDPL and WhatsApp guide.

5

Does confirmation work for cash on delivery and prepaid orders alike?

Yes, and you choose which orders get confirmed. Most Salla stores are prepaid, and a paid order needs a receipt and shipping status more than a pre-dispatch confirmation; a cash-on-delivery order is where confirming before the waybill is printed stops the return. Confirmation can be limited to one payment method only.

6

Does the bot answer in Saudi dialect and to voice notes?

Yes. The dialect is a setting on the agent — Gulf, Egyptian, MSA or "auto" in the customer's own dialect — and a voice note is transcribed and answered as if it were text. Products are read from your Salla store at the moment of the question, so it does not sell what ran out.

7

I have more than one Salla store — how do I connect them?

Each store is connected separately with an approval from its own dashboard, to its own WhatsApp number or to the same number with one agent per store. The common mistake is approving from an account open on the wrong store, so check the store name at the top of the Salla dashboard before you press approve.

8

Does the same connection work on Instagram and Messenger?

Yes. The store is connected once, and the same agent answers on WhatsApp, Instagram, Messenger and Facebook comments from one inbox. Only the presentation differs: a card with a photo and a button on WhatsApp, a photo and a link on Instagram.

And you run all of it from your phoneEverything on this page is also run from the ArabyBot mobile app — replies, orders, campaigns and AI reports. Not a web dashboard only.

Connect your Salla store now — with one approval

Install the app from the Salla app store, create a test order, and watch the confirmation arrive with its buttons before you pay anything. The Salla integration · Saudi stores.