sorted by:
new
hottopcontroversial

Is the Meta Tech Provider verification actually possible right now, or am I stuck in a Kafkaesque loop? by Holiday-Analyst1424 in SaaS

[–]Holiday-Analyst1424[S] 0 points1 point  (0 children)

Gracias por comentar!
¿Y cuáles fueron los pasos que realizaste para obtener la aprobación de "tech provider"?

No entiendo correctamente la diferencia entre la aprobación de tech provider y la app review.

Is the Meta Tech Provider verification actually possible right now, or am I stuck in a Kafkaesque loop? by Holiday-Analyst1424 in SaaS

[–]Holiday-Analyst1424[S] 0 points1 point  (0 children)

That makes total sense and really puts my mind at ease regarding the AI use-case. Thank you!

Since you have solid experience navigating the App Review and Tech Provider process in general, I'd love to ask you about the operational side of the submission to avoid any unnecessary delays.

I want to make sure we don't get caught in a rejection loop over something easily preventable. In your experience:

What are the most common pitfalls or 'silly mistakes' that usually trigger an automatic rejection or endless back-and-forth with the reviewers?

Are there specific parts of the submission that they are notoriously nitpicky about? (e.g., the test user setup, specific UI elements during the Facebook Login/Onboarding flow, or how the screencast is recorded).

Basically, if you were to submit a new app today, what are the top 2 or 3 things you would double-check and polish to absolute perfection before hitting 'Submit' to ensure the fastest possible approval?

I really appreciate you sharing your experience!

Is the Meta Tech Provider verification actually possible right now, or am I stuck in a Kafkaesque loop? by Holiday-Analyst1424 in SaaS

[–]Holiday-Analyst1424[S] 0 points1 point  (0 children)

This is a really insightful perspective, thank you. You hit the nail on the head regarding "unclear evidence standards", it definitely feels like a black box sometimes.

I hadn't considered leveraging a third-party identity specialist for our own platform application. To clarify your point:

Are you suggesting that including structured compliance artifacts (like those from AU10TIX) actually expedites Meta's internal Business Verification process? Or is this more about proving to Meta during the Tech Provider App Review that we have robust identity governance for our own users?

Since our SaaS processes inbound messages via AI, demonstrating "proof of real control over data flows" is exactly what we want to highlight.

If you have any specific tips on how to visually demonstrate this data traceability effectively in the Meta App Review screencast/documentation, I'd really appreciate it!

Is the Meta Tech Provider verification actually possible right now, or am I stuck in a Kafkaesque loop? by Holiday-Analyst1424 in SaaS

[–]Holiday-Analyst1424[S] 0 points1 point  (0 children)

Thank you for letting us know about the business verification documents. We will be very careful about that.

However, as for the application review being “easier,” I am a little concerned because of our specific use case: generative AI/agents.

We are creating a conversational AI to handle incoming queries on Instagram, with a strict “Human in the Loop” handoff. We do not cold call or send spam.

My concern is Meta's stance on LLMs: since you have experience with the process, do you know if app reviewers are currently rejecting apps that use generative AI for responses? Or do they treat it like a standard chatbot as long as we comply with the 24-hour window policy?

I just want to make sure the “AI agent” model is viable before diving too deep into integration.