App Review

• Ensure your app abides by the Platform policies .
• Ensure your app follows the Community Standards ⁠ .
• Publish the Facebook Page associated with your app.
• Ensure your webhook is functioning as expected and returning a 200 OK response to webhook events within 20 seconds.
• If your app has gated functionality or content, provide a way for the Meta review team to access and test it. For example, if a feature requires a user to log in to your service, be sure to provide a username and password in the submission notes. Another common practice is to provide a trigger phrase that reviewers can send to your app that will allow them to start normally gated flows.

• Message templates : Templates offer a great way to structure messages, and offer a much richer conversation than plain text.
• Persistent Menu : There are a lot of ways to use the persistent menu, such as providing navigation or calling out key features. You can even make it the sole way of interacting with your app. It is also a great way to allow people to recover and restart conversation flows if an unexpected error occurs.
• Quick Replies : Asking a person to reply with plain text can make it difficult for your app to anticipate and properly respond to their message. Quick replies allow you to limit the possible responses when needed to create a more seamless experience.
• Messenger Webview : Some features can be difficult to offer inside a conversation. The Messenger Platform supports a full webview so your Messenger app can present complex user interfaces when needed.

• Email notifications: Check that your email notification settings ⁠ are correct. If your email address is incorrect, you will miss important updates about your Messenger app. You should select “All notifications, except the ones you unsubscribe from”.
• Policy enforcement events: Subscribe your app to receive messaging_policy_enforcement webhook events . You receive notifications here if your Messenger app violates a Platform policy .

• Get Started Button : Ensure your app sends a brief welcome message when it receives the messaging_postbacks event from the get started button. This message should introduce newcomers to your Messenger app and outline the features it has to offer.
• Greeting text : The greeting text is your first opportunity to present what your app has to offer and establish the style and ‘voice’ of your brand. You should also take advantage of the personalization template strings to engage the person by name.

• Responsiveness: Does your app respond quickly? Are you taking advantage of features like sender actions to signal when there may be a delay? Is your app able to handle all user input, including random inputs gracefully? Messenger is a conversational format, so keep in mind expectations differ from other types of apps. Keep your average response time under one minute.
• Error and failure states: When your Messenger app receives an unexpected input, does it fail gracefully? If it fails, are people able to recover or restart the experience?
• Conversation flows: Is there a clear path for interacting with your app from start to finish? Do you offer enough guidance and context along the way for a person to know their options at any given point?
• Scale: Does your infrastructure scale? Is your webhook able to handle unexpected spikes in webhook events?

• Click to Messenger ads : Gain exposure for your app in Facebook, Instagram, and Messenger with ads that open new conversations with your Messenger app.
• m.me Link : A shortened URL that redirects users to your Messenger. You can use it on your website, email newsletters, and even add a ref parameter to add context into the conversation.