Hey everyone, running into a wall and could really use input from anyone who's dealt with this. I'm setting up WhatsApp Business API for a clinic client. Business verification has now failed twice — first attempt had a phone number cache issue (now resolved), but the identity confirmation step keeps rejecting the ID even after fixing lighting, framing, corners, dark background, and file size exactly per Meta's spec. I'm currently submitting a photographed printout of an e-Aadhaar PDF Has anyone here run into this specifically? - Did switching to a different ID type (Passport/PAN/DL) fix it? - Does it have to be the original physical card, not a printed e-Aadhaar? - Any luck getting Meta support to actually clarify the rejection reason beyond the generic message? This is time-sensitive — client onboarding is blocked until this clears, and I don't want to burn another attempt guessing. Really appreciate any first-hand experience here. 🙏

I’m building a WhatsApp chatbot in n8n for a clinic. The bot needs FAQ handling, appointment booking, rescheduling/cancellation, reminders, and personalization I’m deciding between using a Switch node based workflow or the AI Agent node. My goal is fast response time and a clean production design, but I also want the bot to feel personalized. For those who have built something similar: - Is the Switch/Rules-based approach better for speed and reliability? - Does the AI Agent node make personalization easier enough to justify the extra latency? - For clinic use cases, would you keep booking/rescheduling outside the agent and use it only for FAQ or fallback? - Any best practices for storing personalization data and routing intents in n8n? I’d like advice from people who have done this in production

Hi everyone, I’m building WhatsApp chatbots for my client to sell to doctors, and I’m trying to make sure the setup is structured in the right way from the start. The chatbot will work on WhatsApp, with n8n running in the background to handle the logic, doctor-specific knowledge, bookings, and alerts. These questions are very important for me right now: - Should I clone the workflow for each doctor, or use a multi-tenant setup? - Should I create different n8n accounts for each doctor? - What is the safest way to structure this so it stays legal and compliant? I’d really appreciate advice from anyone who has already faced this kind of setup. Thanks in advance.

“Most no-code workflows break at scale, not at logic.” Came across this line recently and it got me thinking. If this is actually true, then: - why is there still huge demand for no-code automations? - what exactly breaks at scale? APIs? costs? latency? maintenance? - and how do experienced builders overcome this? For people already working with AI automations/no-code systems:Is it still worth spending serious time learning and building with these tools long-term? Would genuinely love practical insights from people who’ve faced this in real projects.

Only looking for developers with experience in voice agent automation and reasonable pricing in the following: - AI Receptionists - Lead qualification through voice agent - Call recording, transcripts - CRM Integration - Automated follow up Please only reach out if you have a portfolio with the above experience.