chat icon
chat icon
✕

Get A Quote

AI-Powered WhatsApp Customer Support Platform for eCommerce

Customer support for an online store can become repetitive very quickly.

Customers ask where their order is, whether an item is available, how returns work, when a shipment will arrive, or what to do when something goes wrong. The questions are often simple, but answering the same ones throughout the day takes time away from conversations that genuinely need an experienced support person.

We developed an AI-powered WhatsApp customer support platform for eCommerce businesses to handle that repetitive workload while keeping support teams in control.

The platform answers customers using business-approved FAQs, support guidelines, product information, and live commerce data when current information is required. It can understand text, images, and voice notes, organize conversations, create support tickets, summarize resolved cases, and hand a conversation to an agent whenever human attention is needed.

Clock Icon

7 Months

Country Icon

Europe

AI-Powered WhatsApp Customer Support Platform for eCommerce

What Is an AI-Powered WhatsApp Customer Support Platform?

An AI WhatsApp customer support platform helps eCommerce businesses answer customer questions through WhatsApp using approved business knowledge and connected store data.

It can handle routine questions from FAQs, retrieve live order or shipment details when needed, understand images and voice notes, and hand the conversation to a human agent if the AI cannot answer reliably.

What We Implemented Using AI

We built an AI-powered customer support assistant for Shopify merchants that answers customer messages on WhatsApp. It replies to common questions about orders, shipping, returns, products, and stock, using information the merchant has approved and live data from the store.

Instead of support staff typing the same answers again and again, the AI handles the repetitive questions, and the team steps in only when a human is really needed. Support staff can see every AI reply and take over any conversation at any time.

Key AI Capabilities

  • Automatic WhatsApp Replies: Answers customer questions in their own language, using the merchant's FAQs, guidelines, and store data.
  • Live Order and Product Lookups: Fetches order status, tracking, customer details, products, collections, and top-selling items from Shopify only when a question needs them.
  • Image and Voice Note Understanding: Reads text from images and transcribes voice notes, then answers the actual question.
  • Combining Multiple Messages: Merges several short customer messages into one clear question, so the customer gets one useful reply instead of many.
  • Safe Fallback and Handover: When the AI is not sure, it sends the merchant's fallback message in the customer's language and lets a human take over.
  • Automatic Labels: Tags conversations, such as refund request or order status, based on the merchant's own rules.
  • Ticket Summaries: When a ticket is closed, the AI writes a short summary and gives a satisfaction score from 1 to 10.
  • Conversation Insights: Reviews recent conversations and reports AI vs. human replies, customer satisfaction, most asked questions, and top topics.
  • Campaign Writing: Drafts three WhatsApp campaign messages in the chosen tone and language, and refines them in one click (shorter, longer, more emojis).
  • Training From Real Chats: Support staff can correct any AI answer in the chat, and the AI uses it for future customers.

Project Brief

The client wanted to reduce the amount of repetitive WhatsApp support handled manually without losing visibility or control over customer conversations.

The system needed to work around the business's existing support process rather than forcing teams into a completely separate AI workflow.

From one connected environment, the support team needed to:

  • Create and maintain an AI knowledge base
  • Add approved FAQs
  • Define response guidelines
  • Set communication tone and response rules
  • Organize conversations automatically
  • Synchronize relevant product information
  • Let AI handle routine WhatsApp questions
  • Retrieve current order information only when required
  • Check shipment and delivery information
  • Answer suitable stock and product questions
  • Understand customer images
  • Process voice notes
  • Monitor AI-generated responses
  • Pause AI for individual conversations
  • Take over a conversation immediately
  • Improve AI knowledge from real support chats
  • Convert conversations into support tickets
  • Track ticket status and responsibility
  • Generate summaries when cases are resolved
  • Review common support topics and conversation trends

The main requirement was straightforward: automate the predictable parts of support without making customer service unpredictable.

Technologies

  • React

    React

  • Node.js

    Node.js

  • Express

    Express

  • Bun

    Bun

  • WebSockets

    WebSockets

  • Python

    Python

  • FastAPI

    FastAPI

  • LangChain

    LangChain

  • Google Vertex AI

    Google Vertex AI

  • Gemini

    Gemini

  • WhatsApp Business API

    WhatsApp Business API

  • eCommerce API Integration

    eCommerce API Integration

  • AWS Lambda

    AWS Lambda

  • AWS API Gateway

    AWS API Gateway

  • AWS Cognito

    AWS Cognito

  • Amazon SQS

    Amazon SQS

  • Amazon S3

    Amazon S3

  • EventBridge Scheduler

    EventBridge Scheduler

  • MongoDB

    MongoDB

Technology and Methods

  • AI Platform: Google Vertex AI
  • LLM: Google Gemini (Gemini 2.5 Flash by default, configurable per merchant)
  • AI Framework: LangChain, Python, FastAPI
  • Knowledge Retrieval: RAG with merchant knowledge base; FAISS vector search with Vertex AI embeddings (text-embedding-005)
  • Live Data Access: Tool calling to the Shopify Admin API
  • Multimodal: Gemini for image text extraction and voice note transcription, FFmpeg for audio conversion
  • Output Control: Pydantic structured output, JSON repair
  • Monitoring: LangSmith tracing, per-call token and cost tracking, Sentry
  • Shopify App: React, Shopify Polaris, Shopify App Bridge, Node.js, Express
  • Live Chat Frontend: React, TypeScript, Material UI, Chatscope Chat UI, i18next
  • Chat Backend: Node.js, TypeScript, Express, Bun, WebSockets
  • Messaging: WhatsApp Business API
  • Database: MongoDB
  • File Storage: Amazon S3
  • Authentication: Amazon Cognito, JWT
  • Background Processing: AWS Lambda, Amazon SQS, API Gateway (WebSocket), EventBridge Scheduler

Client's Need

The client needed a customer-support system that went beyond sending automated replies.

Business-Specific AI Answers

The AI had to follow the store's own communication style, response rules, escalation guidelines, preferred language, and topics it should avoid.

Controlled Knowledge

Policies around returns, shipping, payment, warranty, product usage, and customer service needed to come from information approved by the business.

Product Information

The support assistant needed access to relevant catalog information so it could answer suitable product and availability questions.

Live Order Data

Questions about order status, delivery, or shipment tracking required current information rather than a pre-written answer.

Text, Image & Voice Support

Customers do not communicate in one format. They may send a typed message, screenshot, product image, or voice note.

Reliable Fallback

When there was not enough approved information to answer safely, the AI needed to stop and follow the configured fallback process.

Human Control

Agents needed to see what AI was saying and take over whenever a conversation became sensitive, complex, or simply better handled by a person.

Simple AI Improvement

Support staff needed a practical way to improve future responses without asking developers to modify prompts every time.

Ticket Management

Customer conversations needed to become trackable cases rather than remain disconnected WhatsApp threads.

Management Visibility

Managers needed a quicker view of support activity, common questions, resolved conversations, and how AI and agents were being used.
AI WhatsApp customer support operations dashboard
AI WhatsApp customer support operations dashboard
AI WhatsApp customer support operations dashboard

Build AI-Powered WhatsApp Support Around Your eCommerce Operation

The most useful customer-support automation is not the one that tries to replace every conversation with AI.

It is the one that understands which questions are repetitive, which answers require current business data, and which conversations should go directly to a person.

That is the approach behind this platform.

AI handles suitable questions using approved knowledge and connected commerce information. Support employees remain visible throughout the process and can take control whenever the situation calls for human judgment.

For businesses planning similar functionality, Kanhasoft can help with AI-powered application development, AI Knowledge Base solutions, custom business software, WhatsApp Business integrations, real-time support systems, and eCommerce application integrations.

Discuss your AI customer-support requirements with Kanhasoft.

Pre-Vetted Developers

Challenges

The Same Questions Kept Returning

Order status, delivery, stock, return, and product questions consumed a meaningful part of the support team's daily work.

A General AI Model Did Not Know Store Policies

Without controlled knowledge, an AI assistant could provide an answer that sounded convincing but did not match the business's actual rules.

Not Every Question Needed Live Data

Calling external commerce APIs for basic policy questions would add unnecessary processing and dependency.

Current Information Could Not Come From Static FAQs

Order and shipment status changes. These questions needed data from the operational system at the time the customer asked.

WhatsApp Conversations Were Not Text-Only

Screenshots, images, and voice messages were part of normal customer behavior.

AI Could Not Be Allowed to Compete With Agents

Once a support employee entered a conversation, the automation needed a clear way to step aside.

Conversation History Could Become Difficult to Manage

Long WhatsApp threads are useful for communication but are not always ideal for tracking support workload and case status.

AI Improvement Had to Be Practical

A support team should not need a developer every time it discovers a better answer to a common question.

Managers Needed Context, Not More Chat Logs

Reading hundreds of messages is not the same as understanding what customers are asking.

The harder problem was therefore not sending an automated WhatsApp reply.

The real challenge was deciding what the AI should know, when it should retrieve live information, when it should stop, and when a person should take over.

Solutions

Business-Managed AI Knowledge Base

The support team can maintain FAQs, communication guidelines, conversation rules, labels, and relevant store information used by AI.

Knowledge-First Responses

Routine questions are answered using approved business information rather than unrestricted model knowledge.

Selective Real-Time Data Retrieval

The AI requests live commerce information only for questions that actually depend on current data.

Order & Shipment Lookup

Current order or tracking information can be fetched when customers ask about an existing purchase.

Product & Availability Context

Synced commerce data gives the assistant useful product context for appropriate customer questions.

Image & Voice Understanding

Customer images can be processed for relevant information, while voice messages can be transcribed before entering the AI workflow.

Controlled Fallback

If the available information is not enough, the system can return the configured fallback rather than invent an answer.

Automatic Conversation Classification

Conversations can be tagged according to support categories such as Order Status, Refund Request, Shipping Question, Product Query, or Payment Issue.

Shared AI & Human Support

Agents see the same conversation history and can pause automation or take over immediately.

AI Training From Real Conversations

Useful agent responses or corrected AI answers can become part of future knowledge.

Automatic Ticket Creation

WhatsApp conversations can become structured support tickets with status, responsibility, timestamps, and conversation history.

AI Ticket Summaries

Closed tickets can be summarized so managers do not have to reread every customer message.

Support Insights

Recent conversations can be analyzed to highlight repeated questions, common topics, satisfaction patterns, and the balance between AI and human support.

AI-Powered WhatsApp Support, Knowledge Management

The platform combines AI support, approved business knowledge, live eCommerce data, human agents, and ticket management in one workflow.

Business-Controlled Knowledge

The support team manages FAQs, tone, language, escalation rules, and topics the AI should avoid.

Knowledge-First Replies

General questions are answered from approved business information, while live eCommerce data is used only when current order, shipment, or stock details are needed.

Multimodal Support

The system can process text, images, screenshots, and voice notes within the same support flow.

Automatic Labels

Conversations can be categorized by topics such as order status, shipping, refunds, payments, product questions, and availability.

Controlled Fallback

If the AI cannot answer reliably, it uses the configured fallback response and allows a human agent to take over.

Human Takeover

Agents can monitor AI replies, pause automation, respond manually, assign chats, and continue from the same conversation history.

AI Learning

Useful agent responses and corrected AI replies can be reused to improve future answers.

Natural Reply Timing

A configurable delay helps combine multiple short customer messages into one relevant reply.

Support Tickets

Conversations can become tickets with status, ownership, timestamps, and linked chat history.

AI Summaries & Insights

Resolved tickets can be summarized, while recent conversations can be analyzed for common questions, support topics, AI-versus-human replies, and customer patterns.

How We Built the AI Solution

Google Vertex AI and Gemini Integration

We used Google Gemini (Gemini 2.5 Flash by default) through Google Vertex AI to understand customer messages and write replies. The model can be chosen per merchant, so different stores can use different Gemini models without code changes.

For example, when a customer asks "Do you offer free shipping?", Gemini reads the merchant's shipping FAQ and guidelines and replies in the store's tone and in the customer's language.

Knowledge Base Answers Using RAG

We used Retrieval-Augmented Generation (RAG) so the AI answers from the merchant's own content instead of guessing.

Merchants manage their knowledge base from the Shopify app: FAQs, guidelines (tone, length, language, topics to avoid, escalation rules), auto labels, and synced store data such as products and top-selling items. When a message comes in, this knowledge is retrieved and given to Gemini together with the conversation history. For large knowledge bases, we also support vector search using FAISS and Vertex AI text embeddings, plus a text pre-filter that keeps only the relevant products before they reach the AI.

Tool Calling for Live Shopify Data

For questions that need live information, we connected Gemini with a fixed set of backend tools, such as customer and order details, products, collections, and top-selling products.

It works in two steps. First, the AI decides whether the question needs live data. If yes, the backend fetches it from Shopify, and the AI then writes the answer using those real records. Questions that don't need live data are answered directly from the knowledge base, which keeps replies fast and reduces API calls. Tool parameters are checked against an allowed list before any call is made.

Multimodal Understanding and Message Handling

Gemini's multimodal support converts images and voice notes into text. Audio is first converted to a supported format with FFmpeg, and the extracted text then goes through the same reply process as normal messages.

A configurable reply delay waits for the customer to finish typing. The AI then merges the separate messages into one clean question before answering.

Structured and Controlled AI Output

Every AI response follows a fixed structure (built with Pydantic and LangChain output parsers). It includes the answer, whether the AI actually knows the answer, whether the conversation has ended, and the translated fallback message. This lets the system decide reliably when to send the fallback, stop the AI, or hand over to a human. A JSON repair step fixes small formatting mistakes in model output.

Human Control and Secure Access

Support staff use a real-time live chat application to monitor AI replies, pause the AI on any conversation, assign chats, and take over instantly. New messages appear live through WebSockets.

Users log in through Amazon Cognito. The AI service accepts only signed JWT requests, and each request is limited to one merchant's data, which keeps every store's information separate. Token usage and cost are tracked for every AI call, and LangSmith is used to trace and debug AI responses.

Key Features

AI-powered WhatsApp customer support

Customer-support guidelines

Escalation rules

WhatsApp Business API integration

Shipment and tracking lookup

Image text extraction

Human escalation

Multiple-message grouping

Instant agent takeover

AI improvement from real chats

Ticket timestamps

AI ticket summaries

Frequently asked question analysis

eCommerce system integration

Tone preferences

Topics-to-avoid configuration

Real-time AI responses

Product-information lookup

Voice-note transcription

Automatic conversation labels

Real-time agent chat

Pause AI per conversation

Automatic support tickets

Ticket filtering

Support conversation insights

Support handling overview

Business-managed AI knowledge base

Response-length rules

Product-data synchronization

Selective live-data retrieval

Stock and availability support

Multimodal customer support

Custom support categories

WebSocket updates

Conversation assignment

Ticket status tracking

Ticket metrics

AI-versus-human interaction analysis

FAQ management

Language configuration

AI enable / disable controls

Order-status lookup

Image understanding

Multilingual fallback handling

Configurable AI reply timing

AI response monitoring

Direct agent replies

Ticket assignment

Ticket export

Customer-topic analysis

Architecture & Scalability

The platform is organized around three main technical components.

eCommerce Administration & Configuration Application: Built with React, Node.js, and Express. This interface allows business teams to manage the AI knowledge base, response guidelines, conversation labels, synced commerce information, fallback behavior, and other support settings.

Live Support Application: Built with React, Bun, Express, and WebSockets. Agents use this workspace to view customer conversations, monitor AI replies, take over chats, assign work, and manage related tickets.

AI Service: Built with Python and FastAPI using LangChain and Google Vertex AI with Gemini. It prepares customer responses from approved business knowledge, conversation history, and relevant commerce information.

The AI service also coordinates image and audio processing and decides when live operational information is needed.

AWS serverless services support incoming-message processing, real-time updates, queued work, scheduled processing, and other background tasks.

MongoDB stores application information. Amazon SQS supports asynchronous workloads, while Amazon S3 provides object storage where required.

Product and other suitable store information can be synchronized ahead of time. This means routine questions do not depend on a live external API call.

Current information-such as an order status, shipment update, or stock value-can still be requested when the question requires it.

This separation helps the platform remain responsive as support volume grows without making every customer message dependent on multiple real-time external calls. The source architecture similarly separates the live support application, AI service, and asynchronous AWS processing.

User Roles

  • eCommerce Business / Store Administrator: Maintains support knowledge, response rules, product information, conversation classifications, fallback behavior, and AI configuration.
  • Support Agent: Monitors conversations, checks AI responses, communicates directly with customers, takes over from AI, assigns conversations, and contributes useful support knowledge.
  • Support Manager: Reviews open and closed tickets, workload, conversation summaries, common support topics, and broader service insights.
  • Customer: Contacts the business through WhatsApp using text, images, or voice notes and continues within the same conversation whether the response comes from AI or a human agent.

Our AI Expertise

At Kanhasoft, we build AI assistants that work with real business data and real business rules.

For this platform, we combined Google Gemini, RAG, tool calling, and multimodal understanding with a live chat system where humans stay in control.

Our focus was to automate repetitive support work while keeping AI answers accurate and predictable, and to give each merchant control over how their AI talks to customers.

Results & Business Impact

The platform creates a practical balance between support automation and human service.

Key outcomes include:

  • Routine customer questions can be handled without waiting for an agent
  • Support employees can focus more attention on cases that require judgment
  • AI answers are based on business-controlled knowledge
  • Current order information can be retrieved when required
  • Live commerce calls are avoided for questions that do not need them
  • Product information can support customer queries
  • Images and voice messages become part of the same support workflow
  • Unknown questions follow a controlled fallback path
  • Agents can see what AI has said before taking over
  • Human takeover does not break the conversation history
  • Support teams can improve future AI answers from real interactions
  • Customer chats can become structured support tickets
  • Ticket summaries reduce the need to reread long conversations
  • Conversation insights highlight recurring customer needs
  • Managers gain better visibility into how AI and agents share the workload
  • The business retains control over knowledge, escalation, and final responses

These are operational benefits supported by the design of the platform. The project source does not provide verified percentage improvements in response time, support cost, or customer satisfaction, so the case study avoids inventing those metrics.

The AI answers common questions about orders, shipping, returns, and stock instantly, at any hour, so customers no longer wait for a person to reply.

Support teams spend their time on conversations that really need a human. Managers get ticket summaries and conversation insights without reading every chat.

Because answers come from approved content and live store data, and unknown questions trigger a fallback instead of a guess, merchants can trust what the AI says to their customers.

Use Cases

This type of AI WhatsApp support platform can work well for:

  • Fashion and apparel businesses
  • Beauty and personal-care stores
  • Electronics retailers
  • Furniture and home-goods businesses
  • Jewelry and accessories stores
  • Health and wellness eCommerce brands
  • Food and specialty-product businesses
  • Direct-to-consumer brands
  • Multi-product online stores
  • Multilingual eCommerce businesses
  • Online retailers receiving frequent order questions
  • Businesses with small customer-support teams
  • Companies handling customer service primarily through WhatsApp
  • Stores that need AI automation without removing human support

Frequently Asked Questions

The AI uses information approved by the business, including FAQs, support guidelines, product information, and conversation context. If a question requires current operational data, such as an order or shipment status, the system can retrieve it through the connected eCommerce service.
No. General questions can be answered from the knowledge base and synchronized business information. Live lookups are reserved for questions that depend on current data, such as an existing order, shipment, or stock status.
The system follows the business's configured fallback process instead of generating an uncertain answer. A human support agent can then continue the conversation.
Yes. Images and screenshots can be processed for useful text and context before the AI prepares its response.
Yes. Voice messages can be transcribed and passed through the same support process used for text-based questions.
Yes. Agents can monitor AI-generated messages, pause automation for an individual conversation, and start responding manually while keeping the existing conversation history.
Useful responses and corrections from real chats can be used to improve the knowledge available for future conversations. This allows everyday refinement to happen closer to the support team.
A customer conversation can create a support ticket with status, assignment, timestamps, and linked chat history. Once the issue is resolved, the ticket can be closed and summarized.
The platform can analyze recent support conversations to highlight areas such as frequently asked questions, common topics, AI-versus-human replies, customer behavior, and support handling patterns.

Talk To Us

About Your Project

About Your Project

We are here to build your software project and help you succeed & grow your business.