Meta App Review Case Study: 20+ Permissions Approved for Devotion + Parade
How Forbes Under 30 founder Cami Téllez and the Devotion + Parade team got 20+ Meta permissions approved across multiple Meta app reviews with Saurabh Dhar.

Meta App Review is where promising integrations go to die.
Founders ship the feature in two weeks, then spend two months watching review cycles bounce back with one-line rejections.
For Forbes Under 30 founder Cami Téllez — founder of Devotion and Parade Meta wasn't just a launch step. It was the launch bottleneck.
Over multiple review cycles, we got 20+ Meta permissions approved across Instagram Graph API, WhatsApp Business API, and Facebook Login for Business — without the back-and-forth, the developer confusion, or the rejected screencasts.
This is the playbook.
“Meta was one of our biggest bottlenecks. The documentation is really hard to navigate. Working with Saurabh completely changed that.”
— Cami Téllez, Founder, Forbes Under 30
The Outcome
In numbers:
- 20+ Meta permissions approved
- Multiple successful review cycles
- Faster launch timelines and reduced engineering rework
- Direct, real-time review issue handling
- Internal team confidence restored
- Meta stopped being the blocker on the roadmap
About Cami Téllez and Devotion + Parade
Cami Téllez is a Forbes Under 30 founder best known for building Parade — a Gen Z-native underwear and intimates brand — and now Devotion, her next venture.
Both companies operate at the intersection of consumer brand, creator economy, and direct-to-consumer commerce, where Meta platforms are critical infrastructure.
About Devotion
Devotion is Cami’s next-generation consumer venture built on top of deep integrations with Meta-owned platforms including Instagram, WhatsApp, and Facebook.
The platform depends on production-tier Meta permissions to power:
- Messaging
- Audience engagement
- Content publishing
- Commerce workflows
- Automation
About Parade
Parade became one of the most recognized Gen Z-native consumer brands in the U.S.
Its growth relied heavily on:
- Instagram-first community building
- Creator-driven marketing
- Social commerce
- Meta ecosystem integrations
For companies like Parade, Meta APIs are not optional tools. They are core business infrastructure.
The Problem: Meta Was a Launch Bottleneck
Before we started working together, the team faced the same issue most SaaS founders face when scaling Meta integrations:
The product worked.
The reviews did not.
Technical Problems
- Repeated App Review rejections with generic reviewer feedback
- Permission dependency confusion
- Business Verification mismatches
- Inconsistent reviewer outcomes
- Screencasts reviewers could not follow
- Fragmented Meta documentation
Operational Problems
- Delayed feature launches
- Developer time wasted on repeated submissions
- Escalation fatigue with Meta support
- Engineering confidence loss
- Weeks lost in avoidable review cycles
Permissions in Scope
The engagement included some of the hardest Meta permissions to get approved:
- instagram_manage_messages
- instagram_content_publish
- instagram_manage_comments
- instagram_basic
- pages_manage_metadata
- pages_read_engagement
- pages_messaging
- business_management
- ads_management
- whatsapp_business_management
- whatsapp_business_messaging
Why Meta App Review Is So Hard
Meta App Review is difficult because approval depends heavily on presentation quality.
The exact same product can pass or fail based on:
- Screencast quality
- Reviewer clarity
- Permission justification
- Test user setup
- UX simplicity
- Business Verification alignment
Common Reasons Meta Rejects Permissions
- Generic screencasts
- Permissions requested without visible product use
- Missing production-ready UX
- Weak reviewer notes
- Test users without real data
- Missing webhook implementation
- App still in Development Mode
- Business Verification mismatches
- Reviewer inability to reproduce flows
What I Actually Did
Technical Guidance
- Full API architecture review
- Endpoint-to-permission mapping
- Feature justification rewriting
- Webhook verification
- Reviewer-focused screencast planning
- Production-realistic test environment setup
Review Strategy
- Permission approval sequencing
- Dependency-aware permission batching
- Reviewer-friendly UX optimization
- OAuth flow improvements
- App configuration hardening
- Business Verification support
Fast Hands-On Support
- Late-night submission support
- Real-time OAuth debugging
- Live reviewer rejection triage
- Fast resubmission turnaround
Results: 20+ Permissions Approved
- 20+ permissions approved across Instagram, WhatsApp, and Facebook
- Multiple successful review rounds
- Faster product launches
- Reduced reviewer back-and-forth
- Higher internal developer confidence
Watch the Founder’s Testimonial
https://www.youtube.com/watch?v=l9WNCVJqcQ0
Who This Service Is For
This consulting is designed for:
- SaaS founders
- CTOs
- AI startups
- Creator economy platforms
- CRM tools
- Marketing automation tools
- WhatsApp automation companies
- Instagram engagement platforms
- Agencies managing Meta apps
My Meta App Review Process
- App architecture audit
- Permission mapping
- Business Verification alignment
- Screencast strategy
- Reviewer flow optimization
- Submission preparation
- Rejection handling
- Re-submission support
- Post-approval scaling guidance
Frequently Asked Questions
How long does Meta App Review take?
Update April 2026 - Standard Meta App Review usually takes 9-12 business days, but complex permissions can extend to several more depending on review cycles.
Why does Meta reject permissions?
Most rejections happen because of unclear screencasts, weak permission justifications, missing production-ready flows, or Business Verification mismatches.
Can Meta permissions be approved without a live product?
Yes. A public launch is not required, but a fully working end-to-end staging environment is necessary.
What is Advanced Access in Meta?
Advanced Access allows public users outside App Roles to use permission-based features in production.
How hard is Instagram Graph API approval?
Instagram Graph API approval is one of the hardest Meta review categories because it includes messaging, engagement, and publishing permissions.
Why do Meta reviewers reject working features?
Reviewers do not evaluate engineering quality. They evaluate: Demonstration clarity Reviewer reproducibility Permission visibility User flow understanding Policy alignment Working features often get rejected because: Screencasts don't clearly show permission usage Test users fail Reviewer notes are weak Privacy Policy disclosures are incomplete
Need Help With Meta App Review?
If your team is stuck with: Repeated rejections Advanced Access denials Business Verification issues Instagram approval bottlenecks WhatsApp API approval delays Saurabh Dhar helps SaaS teams navigate Meta approvals faster with hands-on technical and review guidance.

Saurabh Dhar
Meta API Expert, Full Stack Developer, Tech Founder
Meta API Expert with 12+ years in software development, specializing in Facebook and Instagram integrations. I help businesses navigate the complex Meta API ecosystem and get their apps approved with a 100% success rate. From startup full-stack developer to Meta platform specialist, I deliver solutions that not only get approved but drive real business results.
