u/Key-Customer2176

I’m building BetaXLab — a SaaS platform focused on WhatsApp automation for businesses.
▲ 1

I’m building BetaXLab — a SaaS platform focused on WhatsApp automation for businesses.

Hey everyone 👋

I’m building BetaXLab — a SaaS platform focused on WhatsApp automation for businesses.

Current features include:

  • WhatsApp chatbot flow builder
  • Broadcast campaigns
  • Shared team inbox
  • Contact management / segmentation
  • Template management
  • Analytics & delivery tracking
  • Multi-tenant setup for agencies / SaaS resellers

The goal is to make WhatsApp automation easier for SMBs, agencies, D2C brands, healthcare, education, etc.

I’m currently building the chatbot builder and would love honest feedback from people who’ve used tools like Interakt, AiSensy, Wati, Gupshup, Respond.io, etc.

A few questions:

  1. What’s the most frustrating part of existing chatbot builders?
  2. What features do you wish existed?
  3. What would make you switch from your current provider?
  4. Is pricing, UX, support, or reliability the biggest factor?
  5. If you run an agency, what reseller/white-label features matter most?

Not selling anything right now — genuinely trying to build something useful and avoid solving the wrong problem.

Brutally honest feedback welcome 🙌

u/Key-Customer2176 — 1 day ago
▲ 4

Yesterday, BetaXLab applied to become a Meta Tech Partner 🚀

We’ve successfully submitted our application, and Meta indicated the review process may take up to 5 business days.

BetaXLab is building in the WhatsApp Business ecosystem to help businesses manage communication, automation, and customer engagement at scale.

For founders or teams who’ve gone through the Meta Tech Partner application process:

  • How long did your approval actually take?
  • Any common reasons for delays or rejection?
  • Anything we should proactively prepare during the review?

Would love to hear experiences from others who’ve been through this process.

#Meta #WhatsAppBusiness #MetaTechPartner #SaaS #Startup #B2B #BetaXLab

reddit.com
u/Key-Customer2176 — 2 days ago
▲ 0

I’m currently building a CRM for SMBs where most communication happens on WhatsApp, and I kept running into scaling + maintainability issues with bots.

So I moved to a 5-layer chatbot architecture — sharing it here in case it helps someone (and I’d love feedback from folks who’ve built similar systems).

Building this as part of 👉 betaxlab

🧠 The 5 Layers

1. Channel Layer (Entry Point)

This is where all messages come in.

  • WhatsApp (via Meta API)
  • Future: Instagram, Web chat, Email

Responsibilities:

  • Receive messages (webhooks)
  • Normalize payloads
  • Push into queue (Kafka / Redis)

👉 Decouples platform-specific logic

2. Message Processing Layer

Handles raw message understanding before any bot logic kicks in.

Responsibilities:

  • Message validation
  • Spam filtering
  • Media handling (image, doc, video)
  • Session mapping (user → conversation)

👉 Acts like a “sanity + structure layer”

3. Bot Execution Engine (Core Brain)

This is where most systems get messy — tried to keep it modular.

Responsibilities:

  • Flow execution (node-based bots)
  • State management
  • Rule engine (if/else, conditions)
  • Intent mapping (basic, not heavy AI)

👉 Inspired by Dialogflow but keeping it deterministic for SMB use cases

4. CRM Action Layer

Where chatbot actually drives business outcomes.

Responsibilities:

  • Create/update leads
  • Assign sales reps
  • Update pipeline stages
  • Trigger tasks / reminders
  • Send campaigns

👉 This is where bots connect to revenue

5. Analytics & Feedback Layer

Often ignored early, but super critical.

Responsibilities:

  • Conversation tracking
  • Funnel analysis (lead → conversion)
  • Bot drop-off tracking
  • Campaign attribution

👉 Helps answer: Is the bot actually working?

reddit.com
u/Key-Customer2176 — 17 days ago