July 2018 Update - Facebook App Review Submitted How Long

Facebook introduced the new App Review process to ensure developers use granted permissions for no sick intent. Processing lasts up to several weeks, and in example of a rejected submission, feedback tin can exist generic and deficient. Thus, nosotros would similar to share our experiences and describe how we got our app approved.

chatpointment offers a Chatbot-as-a-Service for appointment booking. With our spider web app, service providers can connect chatpointment's chatbot to their Facebook page to let customers book via Messenger. To allow u.s.a. to do that, we demand approval for two essential permissions:

  • pages_messaging to allow our bot to respond to messages
  • manage_pages to subscribe our bot to a Facebook page

Prior to our submission for the new review process, we already had these permissions granted from an before review.

Messenger: Piece of cake Rider

Our follow-up App Review For Messenger submission to obtain pages_messaging was quite straight-frontwards. We filled in the form and gave a short description regarding the bot's purpose and how to test it. In our instance, we justified the need for pages_messaging to reply to messages from users who book appointments with our bot. We explained how to collaborate with the bot and gave examples of fundamental phrases that would trigger meaningful responses. For testing purposes we referred to Get Cut Or Try Dyeing, 1 of our public Hair Studio demos. That'south it!

Within a few hours after submission nosotros already saw "Messenger Review Team #2" conversation with our bot. The conversation was brief and consisted of a handful of interactions with buttons and carousel templates. The next twenty-four hour period we got approval for pages_messaging and an invitation for business verification.

When Facebook approves your requested permission.

App Review: First Blood

Our App Review for Facebook Login submission to obtain manage_pages was of course more involved. We created a detailed screencast of how to log in to our web app and how to setup and connect our chatbot to a business page. To accompany that, we wrote up detailed step-past-footstep instructions on how to employ the awarding and which permissions were needed for what.

Nosotros covered 2 different scenarios: One for a registration from scratch, and another one for a user who had already signed upwards before — a state of affairs we take prepared with a test user. To cut the long story short:

We clicked 'submit' and felt like we should earn a medal for our thorough submission.

Estimate what.

Our submission was rejected ii weeks subsequently. Wow. We had not predictable that. Following the Messenger Platform Programmer Community we knew others struggled with their review. But we were doing everything right, correct…?

The reasons given for our rejection seemed confusing at offset. Allegedly, our login was not working properly and information technology was non conspicuously visible how our app used the requested permissions. We were pretty frustrated thinking that the reviewers merely did non understood how to log in, although we had clearly described that pace. In fact, each pace of our screencast was meticulously captioned and explained which permissions applied.

Fourth dimension to rethink.

We got off our high horse and digested the trivial feedback we got. How is information technology possible that the review team would non manage to log in? Well, it turns out nosotros had carve up login and signup into two different buttons. Although hallmark with Facebook applies for both, signup required to cheque an 'I agree' box. So, a login attempt without being signed up caused a 'Sign up, please!' prompt, only.

When Facebook rejects your requested permission.

Keep information technology simple and stupid.

What seems logical at first, may easily be misunderstood. Peculiarly when you are decorated reviewing hundreds of apps a day… We concluded to simplify our login and offering just a unmarried button that would cover login and signup alike. Additionally, we used a recommended 'Keep with Facebook' push to make it fifty-fifty more clear what's going on.

TL;DR.

One time logged in, a few setup steps had to be taken before one was able to connect a bot to a folio. For instance, setting up a calendar and specifying staff members. These boilerplate activities caused our screencast to become longer than it had to be in lodge to go to the interesting parts showing how the requested permissions were used. The intent to shorten the screencast pointed us in the right direction: Brand sign-upwardly simpler and faster.

Thus, we re-structured our app, added meaningful defaults and managed to become from registration to the bot'southward kickoff response in less than a minute. Perfect for the screencast, and a real usability improvement. We as well shortened our textual description. We went with a single usage scenario (fresh registration) and focused on 'how' to test and non on 'what' the app does.

Evidence 'Em Whatcha Got.

The remark that i would non clearly see how our app used the granted permissions puzzled united states of america at offset, because our screencast was riddled with explanatory comments. When making the screencast, however, we subconsciously viewed it through the optics of the reviewer and not the actual user, who should feel a benefit from granting permissions.

Instead of lamentatory up the screencast with more managing director's comment, we instead improved our app in such a way, that it became cocky explanatory how user-granted permissions were used. For instance, we labeled a drop down with an easily understandable bulletin (Facebook pages you are admin of) to analyze why pages_show_list was requested.

App Review: Reloaded

Later making these adaptations, we resubmitted and got a positive response after x days. The video below shows the submitted screencast for our second, successful attempt. It shows the login of a test user 'Paul', who is admin of a single page, for which he activates chatpointment's chatbot. To prove that the bot is subscribed correctly, the final footstep shows him messaging his own page.

The instructions below complemented our screencast:

1. Log into Facebook equally a test user: "Paul Frank Paulie Vario", 147825336******, paul******@tfbnw.internet, Password: *******
two. Visit https://app.chatpointment.com/
3. Login with Facebook by clicking on 'Continue with Facebook'.
3.i Grant 'email' permission (nosotros need boosted contact information).
3.2 Grant 'pages_show_list' permission (we use this to show a list of pages in the drib-downwardly).
4. Afterward successful login, you are on the 'Status' page.
5. Choose 'Testpagepaulvario' from the drop-down.
6. Press 'synchronize' to import business details from the folio's public data.
7. Click 'Actuate your chatbot' at the bottom of the 'Status' folio.
seven.1 Grant 'manage_pages' (we apply this to subscribe our app to the page).
seven.two Grant 'pages_messaging' (we use this to answer for the page).
eight. chatpointment is now subscribed as an app to the page 'Testpagepaulvario'.
ix. Click 'Talk to your chatbot' at the bottom of the 'Condition' page.
10. Log into Messenger equally a test user: "Paul Frank Paulie Vario", 147825336******, paul******@tfbnw.net, Password: *******
11. Chat with your bot in Messenger.

Endmost thoughts

Facebook's App Review process has caused plenty of grief among developers. However, 1 can view the App Review stride as an opportunity to rethink and redesign. For chatpointment the results were improved usability through simplification and clarification. Peradventure our shared feel can help others getting their apps approved more smoothly.

Finally, nosotros would like to give thanks Lars Schwarz and Alex Muramoto, who moderate the Messenger Platform Developer Community, for their efforts and community support. Kudos!

Photo by Matheus Ferrero on Unsplash
Image sources:
giphy , memegenerator

Edit three.12.2018: chatpointment is continued every bit Staymate .

deffellstraindich.blogspot.com

Source: https://chatbotsmagazine.com/tell-all-how-we-got-through-facebook-app-review-b4394840759a

0 Response to "July 2018 Update - Facebook App Review Submitted How Long"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel