TL;DR

Pilot one consented Salla or Zid workflow, verify identity and event data, add human fallback, and measure recovery and error rates against a control.

Conversational commerce is the default in KSA

Many Saudi shoppers use WhatsApp to ask about size, cash on delivery, and delivery timing. This playbook shows how to connect SkyLight Chat, WhatsApp Business, and Salla or Zid while measuring outcomes from your own baseline instead of relying on generic conversion claims.

Target architecture to verify: store → SkyLight → WhatsApp Business

  • Confirm which Salla or Zid order and cart events the selected integration actually provides.
  • Define and test identity verification before returning order or personal data.
  • Map each update to the correct WhatsApp template or customer-service message category.
  • Route missing, conflicting, sensitive, or unsupported cases to an authorized person.
  • Document whether tags or suppression states synchronize and how failed updates are reconciled.

Flow 1 — Abandoned cart recovery on WhatsApp

Start with a consented reminder after checkout abandonment, including the product and a direct cart link. Test timing and frequency on a small segment, use the correct Meta template category, avoid false scarcity, provide an opt-out, and compare recovered orders against a control group.

Flow 2 — 'Where is my order?' automation

Ask for an order ID or verified phone number, query Salla or Zid, then return the carrier and tracking URL in the customer's language. Example: 'طلبك #[ID] مع SMSA. التتبع: [Link]'. Measure deflection and incorrect-answer rates, and escalate missing or conflicting data to a person.

Flow 3 — COD confirmation & fake-order reduction

Before dispatch, an approved workflow can ask the customer to reply 1 to confirm COD or 2 to cancel. Decide with operations what an unanswered message means; do not pause or cancel fulfillment without an explicit, tested business rule. Compare return-to-origin cost and false-cancellation rate with a control.

Flow 4 — Restock & offer automation

When a verified inventory event arrives, notify only eligible waitlisted shoppers under the applicable permission and template rules. Configure quiet hours, frequency limits, STOP synchronization, stale-event handling, and suppression before enabling offer messages.

Measurement dashboard

  • Cart recovery rate and revenue attributed to WhatsApp
  • First-response time on ecommerce intents
  • Template block rate / quality rating
  • COD confirmation rate
  • % of WISMO tickets handled without a human

Example staged pilot checklist

  • Day 1–2: Connect WhatsApp Business number + approve utility templates
  • Day 3: Wire Salla/Zid order + cart webhooks
  • Day 4: Upload product FAQs / shipping policy to the knowledge base
  • Day 5: Activate cart + WISMO flows on a 10% traffic sample
  • Day 6–7: Review transcripts and errors, improve language handling, then decide whether a broader rollout is safe