8
7 Comments

I built a WhatsApp AI bot for doctors in Peru — launched 3 weeks ago, 0 paying customers, and stuck waiting for Meta to approve my app

I'm Jordy — solo dev from Chimbote, a small city in northern
Peru you've probably never heard of.

Here's the problem I kept seeing:

Patient: "Can I get an appointment tomorrow?"
Doctor types back manually: "What time works for you?"
Patient: "3pm?"
Doctor: "Let me check... actually 3pm is taken, how about 4?"
Patient ghosts. Appointment lost.

That's happening 30+ times a day in every small clinic
in Latin America. All on WhatsApp. All manual.

I decided to fix it.


What I built

Scarlyfy is a WhatsApp AI bot + digital calendar for
independent doctors and small clinics in Latin America.

The bot runs 24/7:
→ Patient texts → bot checks availability → books the slot
→ Sends automatic reminders before the appointment
→ If the patient doesn't confirm via WhatsApp, the system
automatically calls them via phone (powered by Twilio)
→ Doctor gets a clean dashboard — zero manual work

No-show rates drop. No humans needed.

Tech stack: FastAPI + React + PostgreSQL.
AI via OpenAI. WhatsApp via Meta Business API.
Calls via Twilio.


The painful part nobody warned me about

To send messages via WhatsApp officially, Meta has to
approve your app first.

I submitted on May 13th. It's now day 15.
Estimated wait: 10 days.

There's no way to contact human support while it's
pending — only if it gets rejected. So I'm just
sitting here, product ready, waiting in silence.

That's my only blocker right now.


Honest status

✅ Landing live: scarlyfy.com
✅ Full backend (auth, multi-tenant, appointments, webhooks)
✅ 14-day free trial ready
✅ Starting at $22/month
❌ Meta review pending (day 15)
❌ 0 paying customers


What building this taught me

The code was the easy part. The real challenges:

  1. Third-party approvals you can't control or rush
  2. Doctors don't speak "SaaS" — they want
    "will this save me time?" not "what's your stack?"
  3. In LATAM, most clinics still use a paper notebook.
    You're not competing with software. You're competing
    with habits.

My ask

Has anyone here gone through Meta's WhatsApp Business API
review? How long did it actually take?

If you know doctors or clinics in LATAM drowning in
WhatsApp messages — I'd love to connect.

scarlyfy.com — 14 days free, no credit card needed

What's the longest you've waited for a third-party API approval?
  1. Less than 2 weeks
  2. 2–4 weeks
  3. More than a month
  4. Still waiting right now 😅
Vote
posted to Icon for group Building in Public
Building in Public
on May 29, 2026
  1. 1

    waiting on meta business api approval is a special kind of hell lol. it's crazy how a giant corporate gatekeeper can completely freeze a solo builder's velocity even when the full backend and multitenant logic are 100% ready to deploy.

    stuck on day 15 is brutal. while you're trapped in their review queue, have you considered onboarding 1 or 2 friendly local doctors using the whatsapp business sandbox environment or just routing temporary test flows through a regular twilio number?

    getting real-world usage logs and seeing how patients interact with the openai appointment slots early might give you a huge head start before meta finally wakes up and approves the live app.

  2. 2

    The Meta approval bottleneck is brutal — you're essentially
    building on a platform that can pause your entire business
    with one decision.

    Curious: have you explored whether your target users
    (doctors) would use a web-based version as a stopgap
    while waiting for Meta? Sometimes the "worse" channel
    gets you your first paying customers faster.

    The 0 paying customers after 3 weeks is actually useful
    data. Is the blocker purely the Meta approval, or have
    you also been unable to do sales conversations in the
    meantime?

  3. 1

    Two things from running an MSP for two decades and watching a lot of clinical software adoption: 1) Meta approval will land. 10 to 25 days is the normal band. The faster path is making sure your phone number is tied to a verified Business Manager with at least one prior ad campaign, and that your template messages list a clean opt-in flow. If you get rejected, that is actually good news because then you can talk to a human. 2) Doctors are not your buyer. The receptionist or the clinic admin is. They are the one drowning in WhatsApp messages and the one who keeps her job longer when no-shows drop. Pitch to her. Use a 30-second WhatsApp voice note in Spanish from a current happy clinic admin as your cold open. Doctors trust other doctors, but admins trust other admins. While you wait on Meta, lock in 5 to 10 clinics on a verbal yes so the second you ship you can onboard live.

  4. 1

    Meta approval is the real bottleneck nobody talks about. How long has your number been stuck in review? Mine took 3 weeks — the trick was submitting from a Business Manager account with at least one active ad campaign.

  5. 1

    Strong founder-market fit and the pain is specifically observable. Three things worth pushing on.

    Meta API dependency is structural risk, not just a current delay. Rate limits, periodic re-approvals, instant bans on violations, Meta restructured pricing twice unilaterally in two years. Every clinic depends on Meta not breaking you. Build a phone-call fallback that doesn't route through Meta as Plan B.

    "Competing with habits not software" is sharp but you didn't follow through. Doctors don't have software budget — they have "stuff that saves time" budget. $22/month means break-even at $22 of recovered time. Lead the landing with "Dr. X recovered 12 appointments worth $1,400" not features.

    The Meta wait is also a pre-sell opportunity. Cold outreach 50 clinics: "approval in 10 days, want to be first." Delay becomes scarcity hook.

  6. 1

    The platform waiting game is brutal. I hit something similar with Google Play - they require 12 beta testers opted in for 14 consecutive days before unlocking production for new developer accounts. Took weeks to sort out.

    What helped was reframing the wait as forced marketing time. Can't ship, so write. Forum posts, community replies, early user calls. By the time the gate opens you have a small audience already warmed up rather than starting cold.

    On the 0 paying customers while waiting - that's the gate, not a signal. Nobody can pay if they can't access the product. Worth spending this time finding 5 doctors who are doing this manually right now and getting them on calls. When Meta approves, you'll have warm leads ready rather than needing to find them after launch.

  7. 1

    This is a strong wedge because you are not selling “AI for clinics” in the abstract. You are solving one very specific operational leak: doctors losing appointments because WhatsApp scheduling is slow, manual, and full of back-and-forth.

    For LATAM clinics, I think the clearest positioning is not the tech stack or even the AI. It is “never lose a patient conversation because the doctor was busy replying.” That is simple, practical, and tied directly to revenue.

    One thing I’d pressure-test early is the brand frame. Scarlyfy is distinctive, but for doctors, clinics, and patients, the name has to feel trustworthy very quickly. This is healthcare-adjacent, appointment-related, and tied to patient communication, so the first impression matters more than in a normal SaaS tool.

    Lyriso .com would fit this direction better as a softer, more care-oriented brand for patient scheduling and clinic communication. Same product, same WhatsApp workflow, but with a name that feels more trusted if you expand from appointment booking into reminders, follow-ups, patient intake, or small-clinic CRM.

    Since you are still blocked by Meta and have not locked in paying customers yet, this is actually the right moment to think about the name before doctors, landing pages, and clinic conversations harden around Scarlyfy.

Trending on Indie Hackers
30 days ago I posted here with $0 revenue. Here's what actually happened next. User Avatar 150 comments How to spot high-intent customers in 5 minutes, for free. User Avatar 48 comments Fixing broken scrapers instead of working on my actual product. So I made it my problem. User Avatar 39 comments I Built a Habit Tracker SaaS Alone in 6 Weeks (No CS Degree, No Team). Here's Exactly How User Avatar 39 comments I built an open-source PII masking layer for LLM APIs — early traction, looking for design partners User Avatar 29 comments How to see revenue problems before they get worse User Avatar 22 comments