The loop, in one picture<\/h2>\n\n ![\"Chatbot](\"https:\/\/www.fast2sms.com\/help\/wp-content\/uploads\/2026\/07\/chatbot-loop.png\")
Webhook in, your logic in the middle, session message API out. That is a chatbot.<\/figcaption><\/figure>\nWhat you need<\/h2>\n\n- A free Fast2SMS account<\/a> with your API key.<\/li>\n
- A connected WhatsApp Business number (free, no monthly fee<\/a>).<\/li>\n
- A public HTTPS endpoint on your server. New to webhooks? Read how webhooks work<\/a> first; it covers setup, retries, testing and security.<\/li>\n<\/ul>\n
Step 1: Catch incoming messages with a webhook<\/h2>\n
In your dashboard’s Webhooks section, create a WhatsApp webhook with the event set to received (or All). Give it a payload template with the inbound fields:<\/p>\n
{\n \"webhook_type\": \"{{webhook_type}}\",\n \"from\": \"{{from}}\",\n \"message_type\": \"{{message_type}}\",\n \"body\": \"{{body}}\",\n \"message_id\": \"{{message_id}}\",\n \"phone_number_id\": \"{{phone_number_id}}\"\n}<\/code><\/pre>\nWhen a customer writes to your number, your endpoint receives:<\/p>\n
{\n \"webhook_type\": \"incoming_message\",\n \"from\": \"919999999999\",\n \"message_type\": \"text\",\n \"body\": \"Where is my order?\",\n \"message_id\": \"wamid.HBgMOTE5...\",\n \"phone_number_id\": \"1122334455\"\n}<\/code><\/pre>\nStep 2: Reply with the session message API<\/h2>\n
Because the customer messaged you, a conversation window is open, and you can answer free-form with a session message<\/strong>: no template approval needed for the reply. One POST does it:<\/p>\ncurl -X POST \"https:\/\/www.fast2sms.com\/dev\/whatsapp-session?phone_number_id=1122334455&to=919999999999\" \\\n -H \"Authorization: YOUR_API_KEY\" \\\n -H \"Content-Type: application\/json\" \\\n -d '{ \"type\": \"text\", \"text\": \"Your order ORD4821 is out for delivery today!\" }'\n\n{ \"status\": \"success\" }<\/code><\/pre>\nSession messages support eight types: text, image, document, audio, video, location, sticker and reaction, so your bot can answer with an invoice PDF or a location pin, not just words. Full reference: session message API docs<\/a>.<\/p>\nOne distinction to keep straight: session messages are replies inside an open conversation<\/strong>. To message someone who has not written to you first, use an approved template through the WhatsApp message API<\/a>.<\/p>\nStep 3: Put your logic in the middle<\/h2>\n
Here is a complete minimal bot in PHP: it reads the webhook, routes on keywords, and replies in the same chat:<\/p>\n
<?php\n\/\/ https:\/\/yourdomain.com\/whatsapp-bot.php\n$event = json_decode(file_get_contents('php:\/\/input'), true);\n\nif (($event['webhook_type'] ?? '') === 'incoming_message') {\n $from = $event['from'];\n $text = strtolower($event['body'] ?? '');\n\n if (str_contains($text, 'order')) {\n $reply = 'Please share your order ID and we will check it right away.';\n } elseif (str_contains($text, 'price')) {\n $reply = 'Our latest price list: https:\/\/yourbrand.com\/prices';\n } else {\n $reply = 'Hi! Type ORDER for order status or PRICE for our price list.';\n }\n\n $ch = curl_init('https:\/\/www.fast2sms.com\/dev\/whatsapp-session'\n . '?phone_number_id=' . $event['phone_number_id']\n . '&to=' . $from);\n curl_setopt_array($ch, array(\n CURLOPT_RETURNTRANSFER => true,\n CURLOPT_POST => true,\n CURLOPT_HTTPHEADER => array(\n 'Authorization: YOUR_API_KEY',\n 'Content-Type: application\/json',\n ),\n CURLOPT_POSTFIELDS => json_encode(array(\n 'type' => 'text',\n 'text' => $reply,\n )),\n ));\n curl_exec($ch);\n curl_close($ch);\n}\n\nhttp_response_code(200);\necho 'OK';<\/code><\/pre>\nThat is a working chatbot in about thirty lines. From here you grow it: look up real orders in your database, hand off to a human when the customer types AGENT, or plug the text into an AI model and let it draft replies.<\/p>\n
The same pattern on RCS<\/h2>\n
RCS webhooks emit the same incoming_message events when customers reply to your RCS campaigns, with from, body and message_type fields. Catch them on an RCS webhook and respond through your RCS sending flow; rich cards and buttons make the bot feel app-like inside the default SMS app. Background: RCS messaging<\/a> and creating an RCS bot<\/a>.<\/p>\nWhat SMS webhooks automate (no inbound, still powerful)<\/h2>\n
DLT SMS and bulk SMS have no customer replies, so no chat loop, but their delivered and failed events drive serious automation:<\/p>\n
\n- Failure-triggered fallback:<\/strong> an OTP or alert reports failed, your code immediately resends on WhatsApp, or lets Smart OTP<\/a> handle the switch automatically.<\/li>\n
- List hygiene:<\/strong> numbers that consistently fail get flagged in your database, so bulk SMS campaigns<\/a> stop paying for dead numbers.<\/li>\n
- Live campaign dashboards:<\/strong> delivered counts and per-message cost (amount_debited) stream into your own reporting as each event lands.<\/li>\n
- Order flow sync:<\/strong> mark the order timeline “SMS delivered” the moment the DLT report arrives, using udf1 to carry your order ID through the loop.<\/li>\n<\/ul>\n
Every payload and placeholder for these events is documented with full samples in how webhooks work<\/a>.<\/p>\nBot ideas worth stealing<\/h2>\n\n- Order status bot:<\/strong> customer sends an order ID, your code queries the database and replies with live status.<\/li>\n
- Support triage:<\/strong> keyword menu first, human handoff on request, ticket created via your helpdesk API.<\/li>\n
- Lead qualifier:<\/strong> three questions, answers saved to your CRM, hot leads pinged to sales on their own WhatsApp.<\/li>\n
- Feedback collector:<\/strong> after the delivered webhook fires for an order SMS, wait a day and ask for a rating.<\/li>\n<\/ul>\n
Frequently asked questions<\/h2>\nDo I need template approval for bot replies?<\/h3>\n
No. Replies to an incoming customer message go as session messages, free-form, in eight content types. Templates are only for starting conversations.<\/p>\n
Which channels can run a two-way bot?<\/h3>\n
WhatsApp and RCS, since both deliver incoming replies to your webhook. SMS is one-way in India, so SMS webhooks power delivery-driven automation instead.<\/p>\n
What does the session message API cost?<\/h3>\n
Session messages are billed per WhatsApp conversation rules to your own wallet, with no monthly platform fee. Delivery-basis billing and auto refunds apply as usual.<\/p>\n
How fast does the loop run?<\/h3>\n
Incoming messages reach your webhook near real-time, and your session reply sends immediately, so a well-hosted bot answers within seconds.<\/p>\n
Can I connect an AI model?<\/h3>\n
Yes. Your code sits in the middle of the loop, so passing the body to any AI API and sending its answer back as the session message is exactly the same pattern.<\/p>\n
How do I keep the endpoint secure?<\/h3>\n
Enable webhook signing and verify the webhook_secret_key header, use HTTPS, and de-duplicate events. All covered in the webhooks guide<\/a>.<\/p>\nIs there a no-code alternative?<\/h3>\n
Yes, the free drag-and-drop chatbot builder<\/a> in your Fast2SMS panel, including an API-request block that can call your systems mid-flow.<\/p>\nBuild your first loop today<\/h2>\n
Create your free account, connect your WhatsApp number, add one webhook and one endpoint, and your bot answers its first customer this afternoon.<\/p>\n
What you need<\/h2>\n\n- A free Fast2SMS account<\/a> with your API key.<\/li>\n
- A connected WhatsApp Business number (free, no monthly fee<\/a>).<\/li>\n
- A public HTTPS endpoint on your server. New to webhooks? Read how webhooks work<\/a> first; it covers setup, retries, testing and security.<\/li>\n<\/ul>\n
Step 1: Catch incoming messages with a webhook<\/h2>\n
In your dashboard’s Webhooks section, create a WhatsApp webhook with the event set to received (or All). Give it a payload template with the inbound fields:<\/p>\n
{\n \"webhook_type\": \"{{webhook_type}}\",\n \"from\": \"{{from}}\",\n \"message_type\": \"{{message_type}}\",\n \"body\": \"{{body}}\",\n \"message_id\": \"{{message_id}}\",\n \"phone_number_id\": \"{{phone_number_id}}\"\n}<\/code><\/pre>\nWhen a customer writes to your number, your endpoint receives:<\/p>\n
{\n \"webhook_type\": \"incoming_message\",\n \"from\": \"919999999999\",\n \"message_type\": \"text\",\n \"body\": \"Where is my order?\",\n \"message_id\": \"wamid.HBgMOTE5...\",\n \"phone_number_id\": \"1122334455\"\n}<\/code><\/pre>\nStep 2: Reply with the session message API<\/h2>\n
Because the customer messaged you, a conversation window is open, and you can answer free-form with a session message<\/strong>: no template approval needed for the reply. One POST does it:<\/p>\ncurl -X POST \"https:\/\/www.fast2sms.com\/dev\/whatsapp-session?phone_number_id=1122334455&to=919999999999\" \\\n -H \"Authorization: YOUR_API_KEY\" \\\n -H \"Content-Type: application\/json\" \\\n -d '{ \"type\": \"text\", \"text\": \"Your order ORD4821 is out for delivery today!\" }'\n\n{ \"status\": \"success\" }<\/code><\/pre>\nSession messages support eight types: text, image, document, audio, video, location, sticker and reaction, so your bot can answer with an invoice PDF or a location pin, not just words. Full reference: session message API docs<\/a>.<\/p>\nOne distinction to keep straight: session messages are replies inside an open conversation<\/strong>. To message someone who has not written to you first, use an approved template through the WhatsApp message API<\/a>.<\/p>\nStep 3: Put your logic in the middle<\/h2>\n
Here is a complete minimal bot in PHP: it reads the webhook, routes on keywords, and replies in the same chat:<\/p>\n
<?php\n\/\/ https:\/\/yourdomain.com\/whatsapp-bot.php\n$event = json_decode(file_get_contents('php:\/\/input'), true);\n\nif (($event['webhook_type'] ?? '') === 'incoming_message') {\n $from = $event['from'];\n $text = strtolower($event['body'] ?? '');\n\n if (str_contains($text, 'order')) {\n $reply = 'Please share your order ID and we will check it right away.';\n } elseif (str_contains($text, 'price')) {\n $reply = 'Our latest price list: https:\/\/yourbrand.com\/prices';\n } else {\n $reply = 'Hi! Type ORDER for order status or PRICE for our price list.';\n }\n\n $ch = curl_init('https:\/\/www.fast2sms.com\/dev\/whatsapp-session'\n . '?phone_number_id=' . $event['phone_number_id']\n . '&to=' . $from);\n curl_setopt_array($ch, array(\n CURLOPT_RETURNTRANSFER => true,\n CURLOPT_POST => true,\n CURLOPT_HTTPHEADER => array(\n 'Authorization: YOUR_API_KEY',\n 'Content-Type: application\/json',\n ),\n CURLOPT_POSTFIELDS => json_encode(array(\n 'type' => 'text',\n 'text' => $reply,\n )),\n ));\n curl_exec($ch);\n curl_close($ch);\n}\n\nhttp_response_code(200);\necho 'OK';<\/code><\/pre>\nThat is a working chatbot in about thirty lines. From here you grow it: look up real orders in your database, hand off to a human when the customer types AGENT, or plug the text into an AI model and let it draft replies.<\/p>\n
The same pattern on RCS<\/h2>\n
RCS webhooks emit the same incoming_message events when customers reply to your RCS campaigns, with from, body and message_type fields. Catch them on an RCS webhook and respond through your RCS sending flow; rich cards and buttons make the bot feel app-like inside the default SMS app. Background: RCS messaging<\/a> and creating an RCS bot<\/a>.<\/p>\nWhat SMS webhooks automate (no inbound, still powerful)<\/h2>\n
DLT SMS and bulk SMS have no customer replies, so no chat loop, but their delivered and failed events drive serious automation:<\/p>\n
\n- Failure-triggered fallback:<\/strong> an OTP or alert reports failed, your code immediately resends on WhatsApp, or lets Smart OTP<\/a> handle the switch automatically.<\/li>\n
- List hygiene:<\/strong> numbers that consistently fail get flagged in your database, so bulk SMS campaigns<\/a> stop paying for dead numbers.<\/li>\n
- Live campaign dashboards:<\/strong> delivered counts and per-message cost (amount_debited) stream into your own reporting as each event lands.<\/li>\n
- Order flow sync:<\/strong> mark the order timeline “SMS delivered” the moment the DLT report arrives, using udf1 to carry your order ID through the loop.<\/li>\n<\/ul>\n
Every payload and placeholder for these events is documented with full samples in how webhooks work<\/a>.<\/p>\nBot ideas worth stealing<\/h2>\n\n- Order status bot:<\/strong> customer sends an order ID, your code queries the database and replies with live status.<\/li>\n
- Support triage:<\/strong> keyword menu first, human handoff on request, ticket created via your helpdesk API.<\/li>\n
- Lead qualifier:<\/strong> three questions, answers saved to your CRM, hot leads pinged to sales on their own WhatsApp.<\/li>\n
- Feedback collector:<\/strong> after the delivered webhook fires for an order SMS, wait a day and ask for a rating.<\/li>\n<\/ul>\n
Frequently asked questions<\/h2>\nDo I need template approval for bot replies?<\/h3>\n
No. Replies to an incoming customer message go as session messages, free-form, in eight content types. Templates are only for starting conversations.<\/p>\n
Which channels can run a two-way bot?<\/h3>\n
WhatsApp and RCS, since both deliver incoming replies to your webhook. SMS is one-way in India, so SMS webhooks power delivery-driven automation instead.<\/p>\n
What does the session message API cost?<\/h3>\n
Session messages are billed per WhatsApp conversation rules to your own wallet, with no monthly platform fee. Delivery-basis billing and auto refunds apply as usual.<\/p>\n
How fast does the loop run?<\/h3>\n
Incoming messages reach your webhook near real-time, and your session reply sends immediately, so a well-hosted bot answers within seconds.<\/p>\n
Can I connect an AI model?<\/h3>\n
Yes. Your code sits in the middle of the loop, so passing the body to any AI API and sending its answer back as the session message is exactly the same pattern.<\/p>\n
How do I keep the endpoint secure?<\/h3>\n
Enable webhook signing and verify the webhook_secret_key header, use HTTPS, and de-duplicate events. All covered in the webhooks guide<\/a>.<\/p>\nIs there a no-code alternative?<\/h3>\n
Yes, the free drag-and-drop chatbot builder<\/a> in your Fast2SMS panel, including an API-request block that can call your systems mid-flow.<\/p>\nBuild your first loop today<\/h2>\n
Create your free account, connect your WhatsApp number, add one webhook and one endpoint, and your bot answers its first customer this afternoon.<\/p>\n
Step 1: Catch incoming messages with a webhook<\/h2>\n
In your dashboard’s Webhooks section, create a WhatsApp webhook with the event set to received (or All). Give it a payload template with the inbound fields:<\/p>\n
{\n \"webhook_type\": \"{{webhook_type}}\",\n \"from\": \"{{from}}\",\n \"message_type\": \"{{message_type}}\",\n \"body\": \"{{body}}\",\n \"message_id\": \"{{message_id}}\",\n \"phone_number_id\": \"{{phone_number_id}}\"\n}<\/code><\/pre>\nWhen a customer writes to your number, your endpoint receives:<\/p>\n
{\n \"webhook_type\": \"incoming_message\",\n \"from\": \"919999999999\",\n \"message_type\": \"text\",\n \"body\": \"Where is my order?\",\n \"message_id\": \"wamid.HBgMOTE5...\",\n \"phone_number_id\": \"1122334455\"\n}<\/code><\/pre>\nStep 2: Reply with the session message API<\/h2>\n
Because the customer messaged you, a conversation window is open, and you can answer free-form with a session message<\/strong>: no template approval needed for the reply. One POST does it:<\/p>\ncurl -X POST \"https:\/\/www.fast2sms.com\/dev\/whatsapp-session?phone_number_id=1122334455&to=919999999999\" \\\n -H \"Authorization: YOUR_API_KEY\" \\\n -H \"Content-Type: application\/json\" \\\n -d '{ \"type\": \"text\", \"text\": \"Your order ORD4821 is out for delivery today!\" }'\n\n{ \"status\": \"success\" }<\/code><\/pre>\nSession messages support eight types: text, image, document, audio, video, location, sticker and reaction, so your bot can answer with an invoice PDF or a location pin, not just words. Full reference: session message API docs<\/a>.<\/p>\nOne distinction to keep straight: session messages are replies inside an open conversation<\/strong>. To message someone who has not written to you first, use an approved template through the WhatsApp message API<\/a>.<\/p>\nStep 3: Put your logic in the middle<\/h2>\n
Here is a complete minimal bot in PHP: it reads the webhook, routes on keywords, and replies in the same chat:<\/p>\n
<?php\n\/\/ https:\/\/yourdomain.com\/whatsapp-bot.php\n$event = json_decode(file_get_contents('php:\/\/input'), true);\n\nif (($event['webhook_type'] ?? '') === 'incoming_message') {\n $from = $event['from'];\n $text = strtolower($event['body'] ?? '');\n\n if (str_contains($text, 'order')) {\n $reply = 'Please share your order ID and we will check it right away.';\n } elseif (str_contains($text, 'price')) {\n $reply = 'Our latest price list: https:\/\/yourbrand.com\/prices';\n } else {\n $reply = 'Hi! Type ORDER for order status or PRICE for our price list.';\n }\n\n $ch = curl_init('https:\/\/www.fast2sms.com\/dev\/whatsapp-session'\n . '?phone_number_id=' . $event['phone_number_id']\n . '&to=' . $from);\n curl_setopt_array($ch, array(\n CURLOPT_RETURNTRANSFER => true,\n CURLOPT_POST => true,\n CURLOPT_HTTPHEADER => array(\n 'Authorization: YOUR_API_KEY',\n 'Content-Type: application\/json',\n ),\n CURLOPT_POSTFIELDS => json_encode(array(\n 'type' => 'text',\n 'text' => $reply,\n )),\n ));\n curl_exec($ch);\n curl_close($ch);\n}\n\nhttp_response_code(200);\necho 'OK';<\/code><\/pre>\nThat is a working chatbot in about thirty lines. From here you grow it: look up real orders in your database, hand off to a human when the customer types AGENT, or plug the text into an AI model and let it draft replies.<\/p>\n
The same pattern on RCS<\/h2>\n
RCS webhooks emit the same incoming_message events when customers reply to your RCS campaigns, with from, body and message_type fields. Catch them on an RCS webhook and respond through your RCS sending flow; rich cards and buttons make the bot feel app-like inside the default SMS app. Background: RCS messaging<\/a> and creating an RCS bot<\/a>.<\/p>\nWhat SMS webhooks automate (no inbound, still powerful)<\/h2>\n
DLT SMS and bulk SMS have no customer replies, so no chat loop, but their delivered and failed events drive serious automation:<\/p>\n
\n- Failure-triggered fallback:<\/strong> an OTP or alert reports failed, your code immediately resends on WhatsApp, or lets Smart OTP<\/a> handle the switch automatically.<\/li>\n
- List hygiene:<\/strong> numbers that consistently fail get flagged in your database, so bulk SMS campaigns<\/a> stop paying for dead numbers.<\/li>\n
- Live campaign dashboards:<\/strong> delivered counts and per-message cost (amount_debited) stream into your own reporting as each event lands.<\/li>\n
- Order flow sync:<\/strong> mark the order timeline “SMS delivered” the moment the DLT report arrives, using udf1 to carry your order ID through the loop.<\/li>\n<\/ul>\n
Every payload and placeholder for these events is documented with full samples in how webhooks work<\/a>.<\/p>\nBot ideas worth stealing<\/h2>\n\n- Order status bot:<\/strong> customer sends an order ID, your code queries the database and replies with live status.<\/li>\n
- Support triage:<\/strong> keyword menu first, human handoff on request, ticket created via your helpdesk API.<\/li>\n
- Lead qualifier:<\/strong> three questions, answers saved to your CRM, hot leads pinged to sales on their own WhatsApp.<\/li>\n
- Feedback collector:<\/strong> after the delivered webhook fires for an order SMS, wait a day and ask for a rating.<\/li>\n<\/ul>\n
Frequently asked questions<\/h2>\nDo I need template approval for bot replies?<\/h3>\n
No. Replies to an incoming customer message go as session messages, free-form, in eight content types. Templates are only for starting conversations.<\/p>\n
Which channels can run a two-way bot?<\/h3>\n
WhatsApp and RCS, since both deliver incoming replies to your webhook. SMS is one-way in India, so SMS webhooks power delivery-driven automation instead.<\/p>\n
What does the session message API cost?<\/h3>\n
Session messages are billed per WhatsApp conversation rules to your own wallet, with no monthly platform fee. Delivery-basis billing and auto refunds apply as usual.<\/p>\n
How fast does the loop run?<\/h3>\n
Incoming messages reach your webhook near real-time, and your session reply sends immediately, so a well-hosted bot answers within seconds.<\/p>\n
Can I connect an AI model?<\/h3>\n
Yes. Your code sits in the middle of the loop, so passing the body to any AI API and sending its answer back as the session message is exactly the same pattern.<\/p>\n
How do I keep the endpoint secure?<\/h3>\n
Enable webhook signing and verify the webhook_secret_key header, use HTTPS, and de-duplicate events. All covered in the webhooks guide<\/a>.<\/p>\nIs there a no-code alternative?<\/h3>\n
Yes, the free drag-and-drop chatbot builder<\/a> in your Fast2SMS panel, including an API-request block that can call your systems mid-flow.<\/p>\nBuild your first loop today<\/h2>\n
Create your free account, connect your WhatsApp number, add one webhook and one endpoint, and your bot answers its first customer this afternoon.<\/p>\n