Skip to content
AI · Chatbot Automation

Azizsaif Perfumes — WhatsApp Automation Bot

Feasibility & Scope of Work for the AI assistant “Ahmed” — a WhatsApp chatbot built to turn enquiries into website sales. Prepared by the AZ Media team · June 2026.

01 · Executive Summary

One WhatsApp number, built to sell

The bot — named Ahmed — is the primary WhatsApp point of contact for Azizsaif Perfumes across retail, wholesale and international audiences. Its core objective is to increase direct sales on azizsaifperfumes.com by converting enquiries into website purchases, while delivering efficient multilingual support and minimising live-agent dependency.

This document confirms which capabilities from the brief are feasible, partially feasible, or not feasible within the agreed technical architecture, and defines the scope of work AZ Media will deliver.

18 ✓
Capabilities feasible
2 ~
Partial (image OCR fallbacks)
1 ✗
Not feasible (GMB API)
02 · Feasibility by Capability

The verdict, line by line

Capability / FeatureStatusNotes
Multilingual customer support✓ FeasibleEnglish, Arabic, French and other detected languages
Welcome message & name capture✓ FeasibleBot intro as Ahmed; name stored for session
Website sales prioritisation✓ FeasibleAll product responses link to azizsaifperfumes.com
Product info lookup (price, notes, description)✓ FeasibleSourced from official website product pages
Order number extraction from screenshot~ PartialOCR attempted; text fallback if image unreadable
Order lookup & tracking via Shopify✓ FeasibleLive Shopify data; tracking link returned
Delivery time guidance (country matrix)✓ FeasibleCountry-wise matrix; total timeline on follow-up only
Live Shopify inventory lookup✓ FeasibleReal-time stock status including preorder flag
Preorder messaging✓ FeasibleFixed approved message triggered when applicable
Store info via Google My Business✗ Not feasibleGMB API integration not supported
Store info via static master file✓ FeasibleClient to supply store data; bot routes by emirate/city
Wholesale qualification & catalogue✓ FeasibleIntent detected; catalogue shared; MOQ explained
Distributor file routing✓ FeasibleExact or closest-country match from approved file
Unsupported-country distributor routing✓ FeasibleClosest-country fallback clearly communicated
Competitor product ID from image (OCR)~ PartialAttempted; fallback to brand + name text prompt
Competitor product ID from text message✓ FeasibleFull matching if a competitor reference list is supplied
Similar Azizsaif product recommendation✓ FeasibleMatched to similar tone/profile + website link
Order modification / cancellation / refund✓ FeasibleDetected; routed to live agent Quraysh only
Influencer & collaboration routing✓ FeasibleEmail: collab@azizsaifperfumes.com
HR / job application routing✓ FeasibleEmail: hr@azizsaifperfumes.com
Post-purchase retargeting (monthly)✓ Feasible1-month trigger; repeats monthly; stops on STOP
Escalation to live agent with tagging✓ FeasibleTag: Quraysh; email notification; context passed
Mandatory disclaimers (verbatim)✓ FeasibleAll five disclaimers enforced in relevant intents
03 · Brand & Bot Context

Meet “Ahmed”

Identity & voice

Bot name: Ahmed. Voice: professional, helpful, human — never robotic or overly formal.

Welcome message: “Welcome to Azizsaif Perfumes. My name is Ahmed. I’m here to help you with product information, order updates, store details, wholesale inquiries, and distributor information. May I please have your name to assist you better?”

Primary objective

Prioritise and increase direct sales on azizsaifperfumes.com. Every product interaction — price, notes, best-sellers, competitor matching, retargeting — guides the customer to checkout on the website. Distributor routing is reserved for countries Azizsaif Perfumes does not ship to, or when explicitly requested.

Audience segments

  • UAE retail & returning customers
  • Oman retail customers
  • International / GCC e-commerce customers
  • Wholesale buyers
  • Distributor & regional partner enquiries
  • Influencer & brand collaboration enquiries
  • HR & job application enquiries
04 · Capability Breakdown

How each flow works

Multilingual support ✓

Detects the customer’s language and replies in kind across English, Arabic, French and others. No manual toggle; preference is held for the session.

Product information lookup ✓

Returns name, listed price, short description, fragrance notes and the exact product-page URL from the official site. Clarifies when several products match; always ends with a call to action to azizsaifperfumes.com.

Order lookup & tracking ✓

Shopify is the single source of truth. Order number captured by text or OCR from a screenshot; if unreadable, the bot asks for it. Never fabricates order or shipment data.

Delivery time guidance ✓

Uses the approved matrix. For existing orders the shipping country is pulled from Shopify; handling and delivery times are stated separately, with the combined total only on a delay follow-up.

Live inventory & preorder ✓

Checks real-time Shopify stock before confirming. In stock → confirm online + link; preorder → fixed approved message. Never confirms in-store stock from this number.

Store information ✓ (file) / ✗ (GMB)

Google My Business API is not supported, so store info is served from a static master file. The bot asks the emirate/city and returns the nearest branch; for in-store stock the customer calls the branch directly.

Wholesale qualification ✓

Detects intent (“wholesale, bulk, carton, reseller, trade order”), collects name, company, country and quantity, shares the catalogue and states MOQ = 12 pcs per SKU. Best-sellers come from Shopify data, with a minimum 24 units/SKU always reserved for online sales. Pricing negotiations escalate to a human.

Distributor routing ✓

Shares details only from the approved distributor file. For non-serviceable destinations, an exact match is returned if available; otherwise the closest country is shared, clearly flagged. Never invents a distributor contact.

Competitor matching ~ partial

Image OCR is attempted but depends on photo quality; if unreadable, the bot asks for the brand + perfume name in text. Text matching is reliable with a reference list. Suggestions are framed as “similar in scent profile”, with the website link.

Modification / cancellation / refund ✓

All such requests are detected and routed immediately to live agent Quraysh. The bot never approves or processes them; the order number is collected first.

Influencer, collaboration & HR ✓

Collaboration → collab@azizsaifperfumes.com · HR / jobs → hr@azizsaifperfumes.com. The bot routes, it does not evaluate.

Retargeting & escalation ✓

One month after a confirmed purchase, a monthly recommendation cycle begins; STOP opts out permanently. The bot retries up to 3 times before escalating with full context and tagging Quraysh.

05 · Approved Delivery Matrix

What the bot quotes for delivery

DestinationHandlingDelivery (after dispatch)Total guidance
UAE1 business day1–2 business daysUp to 3 days; most within 2
Oman1–2 business days2–4 business days3–6 business days
Saudi Arabia1–2 business days4–5 business days5–7 business days
Bahrain1–2 business days6–7 business days7–8 business days
Kuwait1–2 business days8–10 business days9–12 business days
All other countries1–2 business daysUp to 14 daysShared only on a delay follow-up

By default the bot states handling and delivery separately; the total timeline is shared only when the customer asks about delays.

06 · Guardrails

Out-of-scope & hard limits

Out-of-scope itemReason / alternative
Google My Business API integrationNot supported. Alternative: static store master file.
Guaranteeing exact delivery datesApproved matrix ranges only, unless present in the order record.
Confirming physical in-store stockE-commerce only; customer directed to call the branch.
Approving refunds, cancellations, modificationsRouted to live agent Quraysh; the bot has no approval authority.
Inventing product details, prices or stockAll data from the official website and Shopify; unconfirmed data is never shared.
Committing to wholesale pricing / discountsOnly approved MOQ and catalogue data; negotiation is human.
Legal, medical, financial or unrelated adviceOutside scope; the bot redirects appropriately.
Image-based competitor OCR as guaranteed outputBest-effort; text fallback always applied when unreadable.

Mandatory disclaimers (verbatim)

Negative list — phrases the bot will never use

07 · Data & Client Actions

Knowledge sources & what’s needed before go-live

SourceUsed forStatus
azizsaifperfumes.comProduct names, prices, descriptions, notes, URLsReady — live
ShopifyInventory, orders, tracking, shipping country, purchase dates, retargetingReady — API integration required
Static store master fileBranch names, addresses, phones, timings (UAE & Oman)Pending — client to supply
Distributor fileCountry/region routing & unsupported destinationsPending — client to supply
Wholesale catalogue fileShared with qualified wholesale buyersPending — client to supply
Google My BusinessStore location / phone / timingsNot feasible — GMB API unsupported

Client action items

08 · Summary & Next Steps

Feasible as scoped

The large majority of requested capabilities are feasible within the proposed architecture. The only capability not feasible as originally specified is the Google My Business API integration, replaced by an agreed static store master file. Two capabilities — order-screenshot OCR and competitor image identification — are partially feasible with robust text-based fallbacks.

Next: client sign-off → supply the pending files (store, distributor, wholesale, non-serviceable list) → AZ Media initiates Shopify integration and configures the conversation flows → UAT → go-live on sign-off.