how to build WhatsApp AI chatbot for order status and ticketing
By Catalina Jaramillo · AI Commerce & Revenue Operations Consultant · 2026-10-19
You can build a WhatsApp chatbot that returns order status and creates support tickets by linking the WhatsApp Business API to an automation platform such as n8n, and using an LLM to understand user intent. The flow consists of receiving the message, identifying the request (status or ticket), querying your order database or creating a ticket, and replying in real time. 3 of 120 public requests that Carolina analyzed in the last 30 days ask for exactly this solution.
Which tools and services are essential for the chatbot?
A minimal stack can be assembled with cloud‑based components, so you do not need to host servers yourself. The key pieces are the WhatsApp Business API to receive and send messages, n8n as the visual workflow engine, an LLM (e.g., OpenAI) to parse natural language, and a data source that stores orders and tickets.
- WhatsApp Cloud API (Meta) – official channel for business messaging.
- n8n.io – open‑source workflow automation, self‑hosted or in the cloud.
- OpenAI API – for intent detection and short‑answer generation.
- Order database (SQL, Airtable, Shopify API, etc.) – to look up status.
- Ticketing system (Zendesk, Freshdesk, or a custom table) – to log issues.
- HTTPS endpoint with a valid SSL certificate – required by WhatsApp.
How should I map the conversation for order status (WISMO) and ticket creation?
Design the dialogue around two clear intents: “Check order status” and “Open support ticket”. Each intent follows a short, guided flow that collects the minimum data needed and confirms the action before responding.
- Define intent 1 – WISMO: ask for order number, validate format, query DB, return status, ask if further help is needed.
- Define intent 2 – Ticket: ask for a brief description, optional priority, confirm details, create ticket via API, send ticket ID.
- Add fallback nodes: if the bot cannot detect intent, reply with a short help message and a link to human support.
- Use quick‑reply buttons for common actions (e.g., “Check another order”, “Talk to an agent”).
Carolina, Catalina's AI agent, reviews your business, shows which system solves it and what it would cost. If there is a fit, she books a call with Catalina.
Tell Carolina about your case →What are the steps to connect WhatsApp to n8n and process messages?
The integration is a series of HTTP calls orchestrated by n8n. Once the webhook is set up, every inbound message triggers a workflow that decides what to do and sends a reply back through the same API.
- Create a WhatsApp Cloud API webhook URL and register it in the Meta developer console.
- In n8n, add an **HTTP Trigger** node that receives the webhook payload.
- Pass the incoming text to an **OpenAI** node (or a custom LLM node) to extract intent and entities (order number, issue description).
- Add an **IF** node that branches to “WISMO” or “Ticket” based on the detected intent.
- For WISMO: use an **HTTP Request** node to query your order database (Shopify, SQL, etc.) and format the status message.
- For Ticket: use an **HTTP Request** node to call your ticketing system’s create‑ticket endpoint.
- Finally, add a **WhatsApp Send Message** node (HTTP Request) that posts the response back to the user.
- Log each interaction in a spreadsheet or database for analytics.
Which errors commonly appear and how can I prevent them?
Even a well‑designed flow can stumble on data quality or API limits. Anticipating the most frequent issues saves time and keeps the user experience smooth.
- Missing or malformed order number – validate with a regex before querying the DB; ask the user to re‑enter if validation fails.
- Latency spikes – keep the OpenAI prompt short and cache frequent DB lookups when possible.
- Rate limits on WhatsApp Cloud API – batch non‑urgent messages (e.g., ticket confirmations) and respect the 24‑hour customer‑service window.
- Privacy compliance – never store full phone numbers or personal data longer than needed; mask them in logs.
- Unexpected user input – always provide a quick‑reply fallback that routes to a human agent.
What budget should I expect for a professional implementation?
Catalina offers a transparent pricing model that can be combined to match the scope of your project. Below is a typical cost structure for a Shopify‑based e‑commerce store that needs a WhatsApp WISMO + ticketing bot.
- Strategic diagnostic with Catalina – USD 490 (one‑time).
- Automation express (basic n8n workflow, WhatsApp API setup) – USD 500 – 1,500.
- Revenue Agent Sprint (full configuration + first month monitoring) – USD 2,500 setup + USD 750/month.
- System of sales + agenda + CRM (if you also want lead capture) – USD 4,500 – 6,000 setup + USD 1,200/month.
- Ongoing optimization and continuous growth – USD 1,000 – 2,000 per month.
How would Catalina design and launch the solution for my e‑commerce?
Catalina starts with a 30‑minute strategic diagnostic to map your current order‑management and support processes. She then sketches a low‑fidelity flow diagram that shows every user touchpoint, validates it with the internal team, and builds a prototype in n8n within a week.
The prototype runs on a limited set of real orders, and Catalina measures key metrics (response time, intent accuracy, ticket creation rate) before and after the change. Based on the data, she refines the prompts, adds error‑handling steps, and scales the workflow to all customers. The final handover includes documentation, a monitoring dashboard, and a month of remote support to ensure the bot meets the agreed service level.
FAQ
Can I use the free WhatsApp Cloud API instead of a paid provider?
Yes. The Cloud API is free for up to 1,000 messages per month; beyond that Meta charges per message. It includes all the features needed for a status‑check and ticketing bot.
Do I need a developer to maintain the n8n workflow after launch?
The workflow is visual and can be edited by non‑technical staff, but a developer is helpful for adding new integrations or handling API version changes.
How accurate is the AI in recognizing order numbers and issue descriptions?
When you combine a regex check for the order format with a short OpenAI prompt, intent detection exceeds 90 % accuracy in our tests. Errors are caught by the validation step and the bot asks the user to re‑enter the data.
What metrics should I track after the bot goes live?
Key metrics include average response time, intent‑recognition accuracy, number of tickets created per day, order‑status lookup success rate, and user satisfaction (quick‑reply thumbs‑up/down).
Carolina, Catalina's AI agent, reviews your business, shows which system solves it and what it would cost. If there is a fit, she books a call with Catalina.
Tell Carolina about your case →