Amandeep Singh

12/07/2026

🚀 New case study on the blog.

A client running a ChatPion Messenger + Instagram chatbot platform came to me after his own Meta App Review submission was rejected — and a second attempt got stuck halfway.

The real problem wasn't the chatbot. It was:
❌ A Business Manager verification conflict blocking the app
❌ Usage descriptions that didn't match what reviewers actually test
❌ 17 permissions that all had to be justified and demonstrated individually

One properly prepared submission later: 17 permissions & features approved, including pages_messaging, instagram_manage_messages, instagram_content_publish and business_management. His chatbot and in-chat store finally went live for real users.

Full breakdown 👇
https://singhamandeep.com/chatpion-messenger-chatbot-meta-permissions-approved-case-study/

If your Meta app keeps getting rejected, message me — this is what I do every day.

ChatPion Meta App Review case study: how a Messenger chatbot platform got 17 permissions approved in one prepared submission after a rejection.

03/07/2026

A client's Instagram messaging integration kept getting rejected by Meta App Review — and it had nothing to do with their code.

The reviewer's note: "no evidence of delivery to the messaging client." Their screen recording showed the app sending a message, but never showed it actually landing inside Instagram. That's one of the most common (and most avoidable) ways a working integration still fails App Review.

On top of that: a Business Verification requirement, a privacy policy hosted on the wrong domain, and a mid-review access handoff — all had to be sorted before the permission cleared.

Full breakdown of what went wrong and how it got fixed 👇
https://singhamandeep.com/instagram-business-messaging-screencast-rejection-case-study/

An Instagram messaging connector was rejected for missing delivery evidence in its screencast. Here's how the real issue was diagnosed and the permission got approved.

02/07/2026

An ads analytics SaaS platform came to us after getting rejected twice by Meta for the same permissions: business_management, ads_read, ads_management.

The problem wasn't the use case description — it was the demo video. Their Facebook app was already connected before recording started, so reviewers never saw a real OAuth connection + live data flow happen.

We rebuilt the recording from a clean state: removed the app from Facebook's connected Business Tools, recorded a fresh connect flow, imported a live ad account on camera, and showed the ads data rendering inside the dashboard.

Result: ads_read approved. business_management and ads_management are the next round.

Full case study: https://singhamandeep.com/meta-ads-api-permission-approved-after-rejection-case-study/

If your ads_read or business_management submission keeps getting rejected, message me — happy to take a look before you burn another review cycle.

A SaaS platform was rejected twice for the same ads_read submission. What the screen recording was missing, and how it got approved on the next round.

26/06/2026

A SaaS platform came to me after their Instagram API permissions had been rejected 3 times.

They needed two permissions approved:
→ instagram_business_basic
→ instagram_business_manage_insights

Their app was fine. Their submission wasn't.

They had been waiting months. They had a Meta Marketing Partner agency involved. Still nothing. No clear rejection reason — just silence and another rejection.

Here's what was actually wrong:

❌ Their use case description was the same generic paragraph for both permissions. Meta's reviewers need a separate, specific justification for each one — what data it accesses, where it appears in the app, and why it can't be removed.

❌ Their screencast skipped the OAuth authorization flow. Meta needs to see the full login → authorize → data visible sequence from a fresh disconnected state. Not just the final dashboard.

❌ Their reviewer test credentials weren't connected to a professional Instagram account. So the reviewer literally couldn't test the permissions being requested.

We fixed all three. Rewrote both use case descriptions from scratch, guided the proper screencast recording, and set up clean test credentials.

Both permissions approved. ~20 days from last rejection to approval.

If your Instagram API submission keeps coming back rejected without a clear reason — the problem is almost always in how the submission was prepared, not in your app.

Full case study: https://singhamandeep.com/instagram-business-api-permissions-approved-case-study/

29/04/2026

Waheguru

27/04/2026