How I Built a Social Media Bot That Replies in 90 Seconds Across 5 Platforms (For $29/mo)

I was paying $102 a month for four separate SaaS tools to reply to customer messages, and I still missed a $1,400 order because the WhatsApp lead sat in a tab I had closed. That was the week I decided to build one social media bot to replace the whole stack. Six months later my median reply time across Instagram, WhatsApp, Messenger, Telegram, and email is 90 seconds, and my software bill dropped to $29 a month. This is exactly how I did it, including the 3am moment where the bot promised a customer a discount I do not offer.

The $102 stack I was running before

Here is what my "modern founder support stack" looked like in early 2026. I am embarrassed to write it down.

1. ManyChat at $15/mo for Instagram DM auto-replies (Pro plan, 1,000 contacts).
2. Chatfuel at $19/mo for Facebook Messenger flows.
3. WATI at $49/mo for WhatsApp Business API replies (Growth tier, 1 user).
4. Front at $19/mo for shared email inbox.

Total: $102/mo, four dashboards, four sets of prompts, four billing emails, and zero handoff between them. If a lead DMed me on Instagram and then followed up on WhatsApp, I had two different conversations in two different apps with two different bots giving two different answers. That is not automation. That is chaos with a monthly invoice.

The one tool that replaced all four

I built and now run everything through OT1-Pro Starter at $29/mo. One inbox, one AI, five platforms, one conversation history per human being regardless of which channel they touched me on. Here is the honest comparison.

The gap widens if you were already considering upgrading. Zendesk starts at $55/user/mo. Intercom's Advanced tier is $74/mo per seat and their AI Agent (Fin) adds $0.99 per resolution on top. For a solo founder or a two-person team, none of that math works.

Why "90 seconds" is the number that actually matters

Response speed is the only support metric that correlates with revenue for a small business. Meta gives you a 24-hour messaging window on Instagram and Messenger. Miss it and you cannot send a free-form reply without a paid template. On WhatsApp the same 24-hour rule applies before you have to send an approved template message and pay per conversation. If a lead messages you at 11pm and you reply at 10am the next morning, you are inside the window but the lead has already messaged three of your competitors.

My old average was 4 hours 20 minutes. My new median is 90 seconds. That change alone lifted my reply-to-sale conversion from 11% to 27% in the first 60 days. Same product, same prices, same me. The only variable was that I stopped making people wait.

The exact platform setup, in order

I connected the platforms in this order because it is the order of least friction to most friction. If you try to do WhatsApp first you will quit.

1. Telegram (5 minutes). Open @BotFather in Telegram, type /newbot, name it, copy the Bot Token, paste into OT1-Pro. Done. No approvals, no verification, no waiting.
2. Email (10 minutes). Add IMAP credentials for the inbox I actually check. The system polls every 2 minutes for new mail and threads replies correctly.
3. Instagram and Messenger (30 minutes if your Meta app is verified, one week if not). OAuth through Meta, grant pages_messaging and instagram_manage_messages, webhook subscribes to the Instagram Graph API for new DMs. Each Messenger user gets a PSID that OT1-Pro maps to the conversation.
4. WhatsApp (2 hours, or 5 minutes with the QR path). If you want the official Business API you go through Meta's tech provider onboarding. I chose the QR-code path (Evolution API under the hood) which scans like WhatsApp Web and works instantly, no template approvals, no phone number verification.

If Meta OAuth trips you up on Instagram or Messenger, I wrote a full walkthrough of exactly what "Advanced Access" means and why your app might still be stuck on "Ready to Test" here: Meta App Verification 2026 Founder Guide. That post exists because it took me two weeks of trial and error to unblock.

The two prompts that make the bot sound human

Everyone thinks the magic is in the LLM. It is not. The magic is in the two prompts you write. Here is exactly what I use.

Prompt 1: The system prompt (who the bot is)

Mine is 380 words and it does four things. It tells the AI (1) the name of my business and the one-sentence description, (2) the top 5 products with prices in a plain list, (3) three hard rules ("never invent a discount", "never promise delivery times", "if unsure, say I will check with the founder"), and (4) the tone ("write like a tired but friendly shop owner texting a regular customer"). That is it. No 4,000-word persona document. No "you are a world-class customer support agent" nonsense. The tone line is the one that changed everything, because it made the bot stop sounding like a bot.

Prompt 2: The context injection (what the bot knows right now)

Every time a message comes in, OT1-Pro appends the last 20 messages of that specific human's history (across all platforms) plus a stock-availability snippet. So when Ahmed DMs me on Instagram on Tuesday and then WhatsApps me on Friday, the bot on Friday already knows Ahmed asked about the blue medium on Tuesday and I told him it was in stock. Continuity across channels is the single feature that made customers say "wait, how do you remember?"

The 3am screw-up that taught me the guardrails

Week three, 3:14am my time. A customer messaged asking if they could get 20% off for buying two shirts. My bot, in its helpful eagerness, replied: "Absolutely, I can offer you 20% off both shirts if you order in the next hour." I do not offer volume discounts. I woke up at 8am to a paid invoice at the discounted rate and a very confused shipping label.

I ate the loss ($43) and rewrote the system prompt that morning. The fix was one line: "You have no authority to offer discounts, coupons, refunds, or free shipping. If asked, say you will pass the request to the founder for approval." Since then, zero incidents in five months. The lesson: the LLM will happily invent things that sound customer-friendly. You have to explicitly forbid the specific ways it can hurt you.

What "5 platforms in one inbox" actually feels like

The workflow now looks like this. I open one tab. There is a list of conversations sorted by most recent activity. Each conversation shows a small icon for the platform it started on. If a customer has messaged me on two platforms, the conversations are merged into one thread with icons showing which channel each message came from. When the AI replies, I get a notification if it flagged anything as "needs human review" (pricing questions, complaints, anything containing the word "refund"). Everything else, it just handles.

I check the inbox twice a day. Morning coffee and after dinner. That is the whole support ops workflow for a business doing ~200 conversations a week.

The real cost breakdown after 6 months

Here is what I actually spend now, transparently.

1. OT1-Pro Starter: $29/mo (unlimited platforms, unlimited AI replies within fair-use).
2. WhatsApp Business API fees: $0 because I use the QR path. If you go official API, Meta charges per conversation, roughly $0.005 to $0.08 depending on country and category.
3. Domain and email hosting: I already had these.

Total new spend: $29/mo. Savings vs the old stack: $73/mo, or $876/year. And that is before counting the deals I no longer miss. Full pricing details are on the pricing page.

Why I did not just use WATI

WATI is a fine tool if you only care about WhatsApp. But WhatsApp is one channel. My customers message me on Instagram first (Reels attract them), follow up on WhatsApp (they want to feel personal), and pay by email invoice (my Egyptian customers still trust email for money). A WhatsApp-only tool at $49/mo forces me to buy three more tools for the other channels. I wrote a longer breakdown of that math here: OT1-Pro vs WATI comparison.

What I would do differently if I started over

Three things. First, I would connect Telegram on day one even if I had no Telegram customers, because it is free and it trains you on how the inbox works before you touch anything with Meta approvals. Second, I would write the "no discounts, no refunds, no delivery promises" guardrail into the system prompt on day one instead of after losing $43. Third, I would not have wasted two weeks on ManyChat's flow builder trying to script every conversation branch. LLMs handle the branching. Stop building decision trees for a technology that does not need them.

Should you build this yourself instead of using OT1-Pro?

Honest answer: if you are an engineer with 40 free hours and you like maintaining webhooks, yes, you can wire up the Instagram Graph API, the Messenger Send API, the WhatsApp Cloud API, a Telegram bot, and an IMAP poller yourself. You will also need a queue worker, a database, an LLM API key, a rate limiter, and a way to handle Meta's 24-hour window logic. I did all of that. That is what OT1-Pro is. I am charging $29/mo because I already paid the cost of building it, and I would rather have 1,000 customers at $29 than 10 customers at $299.

If you would rather not maintain any of that, create a free account, connect Telegram in five minutes, and see if 90-second replies change your numbers the way they changed mine.

Run WhatsApp, Instagram, Messenger, Telegram, and email from one inbox

OT1-Pro is the unified inbox I built after losing too many deals to slow, siloed replies. One AI agent, five platforms, one conversation per human — replies in your brand voice, respects Meta's 24-hour window, and escalates to you only on real deals. Free forever plan, no credit card, founder-accessible on WhatsApp.

Start free → · Pricing from $8/mo · Why we beat WATI · The Meta verification guide founders actually need · Talk to me on WhatsApp