u/Few-Reporter8206

Hey everyone,

I'm building a SaaS platform for private clinics in Turkey (think: AI-powered clinic assistant that handles patient communication via WhatsApp). Each clinic subscribes and connects their own WhatsApp Business number to use the AI agent.

The core problem:

I need each clinic owner to connect their own WhatsApp Business number without leaving my platform — essentially an embedded signup flow. I am NOT trying to use one shared number for all clients. Each client = their own WABA + phone number.

What I've researched so far:

• Meta Tech Provider program — the "correct" path, but 2-4 month approval process, heavy technical requirements, and I'm a non-technical founder
• 360dialog Partner program — has embedded signup ✅ but €500/month flat fee + €49/number. Way too expensive at early stage
• Twilio — explicitly says ISVs cannot use self sign-up, must go through Meta Tech Provider program
• WATI — not designed for reselling API access, per-account model
• ChakraHQ — looks promising (~$3/number/month, official Meta BSP, embedded signup), but based in India and I have serious KVKK (Turkish data privacy law) concerns since I'm handling health-adjacent data
• Desk360 (Turkish BSP) — free platform but no embedded signup, requires manual setup per client which doesn't scale

What I actually need:

1. ✅ Embedded signup — clinic owner connects their WhatsApp number inside my platform in a few clicks
2. ✅ Official Meta Cloud API (no grey-area WhatsApp Web scrapers — accounts getting banned is not an option for clinics)
3. ✅ Multi-tenant API — I manage all connected numbers programmatically via webhooks + REST API
4. ✅ Affordable at early stage (starting with 5-20 clients)
5. ✅ Ideally EU/Turkey data residency or at minimum GDPR-compliant (health data sensitivity)

Questions:

1. Has anyone actually shipped a multi-tenant WhatsApp platform as an ISV without going through the full Meta Tech Provider program? How?
2. Is ChakraHQ's embedded signup flow genuinely smooth for non-technical end users?
3. Any BSPs I've missed that offer embedded signup + ISV/partner API access at a reasonable price point?
4. How are you handling GDPR/data residency when health-related conversations flow through a third-party BSP?

Any advice from people who've actually built on top of WhatsApp Business API at scale would be hugely appreciated. This feels like a problem many vertical SaaS builders must have hit.

Hello, I've created a WhatsApp AI assistant for physiotherapy clinics using N8N. There will be a user dashboard where the clinic owner can monitor and track progress. I've also set up a subbase where the data will be stored. The workflow is ready, and I'm running tests. Do you think this model will be successful? Do you have any advice?

selamlar arkadaslar . n8n ile aı asistan geliştiriyorum yazılımcı deglım tamamen vibe coding. pazarlamacıyım. merak ettiğim konular var. bir n8n ile ve aı ile bu tarz bir ürünü yaptım ama stabil çalışması ıcın neler gerekir? bir kullanıcı paneline ihityacım var onu nasıl yaparım? hepsi ai ile bir yere kadar yapılıyor ama sonrası ıcın nasıl bir yol izlemem gerek? iş birliklerine de açığım . sıfırdan bir şeyler inşa etmek isteyen arkadaslarla konusabiliriz . adanada yasıyorum suanda