![](https://bot-data.s3.ap-southeast-1.wasabisys.com/livechat/2024/6/telegram/livechat-1-1718086309.png)
Flaw in embedded system
Arikrishnan
Team,
1) Currently, if a user signs up using embedded signup, he has to register manually, unless registered, the two factor authentication PIN won't be visible. So remove the manual registration process for embedded and make it as automatic along with WhatsApp business account creation. The default pin to use is 123456.
2) The catalog permission is showing as cross after the embedded sign up check this.
1) Currently, if a user signs up using embedded signup, he has to register manually, unless registered, the two factor authentication PIN won't be visible. So remove the manual registration process for embedded and make it as automatic along with WhatsApp business account creation. The default pin to use is 123456.
2) The catalog permission is showing as cross after the embedded sign up check this.
Arikrishnan
1) Currently, if a user signs up using embedded signup, he has to register manu...
and yes without registering pin number not getting activated so please make it automatically.
thanks
Hi Arikrishnan and Dishang,
Thank you for bringing these issues to our attention.
Regarding the first point about removing the manual registration process for embedded signups and making it automatic along with WhatsApp business account creation, we initially implemented an auto-register system. However, we encountered several drawbacks:
Existing Number Registration: If a number was already registered, errors would occur in the middle of the process for some numbers.
Access Token Issues: We faced issues in refreshing the access token, which caused disruptions.
PIN Visibility: Users were unable to know their PIN numbers.
Due to these issues, we intentionally switched to a manual registration process to ensure a smoother and more reliable experience for our users. At this time, we do not plan to revert to the auto-register option due to the aforementioned challenges.
Regarding the catalog permission showing as a cross after the embedded signup, we are currently investigating this issue. We will provide an update as soon as we have more information and a resolution in place.This is actually a display issue, no functionality will be affected for it.
We appreciate your understanding and patience as we work through these issues. If you have any further questions or need additional assistance, please feel free to reach out.
Best regards,
Thank you for bringing these issues to our attention.
Regarding the first point about removing the manual registration process for embedded signups and making it automatic along with WhatsApp business account creation, we initially implemented an auto-register system. However, we encountered several drawbacks:
Existing Number Registration: If a number was already registered, errors would occur in the middle of the process for some numbers.
Access Token Issues: We faced issues in refreshing the access token, which caused disruptions.
PIN Visibility: Users were unable to know their PIN numbers.
Due to these issues, we intentionally switched to a manual registration process to ensure a smoother and more reliable experience for our users. At this time, we do not plan to revert to the auto-register option due to the aforementioned challenges.
Regarding the catalog permission showing as a cross after the embedded signup, we are currently investigating this issue. We will provide an update as soon as we have more information and a resolution in place.This is actually a display issue, no functionality will be affected for it.
We appreciate your understanding and patience as we work through these issues. If you have any further questions or need additional assistance, please feel free to reach out.
Best regards,
Then you should automatically open the register popup window once embedded is done and ask user to register. This is creating many issues users dint know the process and since with registration number wont be active and they are moving out to different vendor.
Also in register popup mention like default PIN will be 123456 ..
Also in register popup mention like default PIN will be 123456 ..
OMG.. Botsailor team resolve it asap
BotSailor
Thank you for bringing these issues to our attention.
today one of my client signup using embedded singup than catalog permission was shows like attached image https://prnt.sc/Ck8j9cUlVQDw he was unable to continue after that i found work around as taken anydesk of his system opened business manager > catalog > created manually catalog > and get back to ES flow and refresh than catalog shown and after tick i continued.
so one ES flow error resolved by manual process after that 2nd error as his waba number not shows on whatsapp than i asked to register and enter pin than after some minutes got activated.
so you understand you need to fix this bug and make iit fully automatically.
tahnk you
Dishang Shah
today one of my client signup using embedded singup than catalog...
And about register phone number, we will provide warning message or will think about returning auto register .
Thanks
Dont think of auto register, you have to complete the registration process. All the other vendors are doing the same and im completely suprised why you are alone finding issues. If you dont know about the process let me know i will explain
Arikrishnan
Okay, We are releasing auto register option and also option to connect account with catalog_management permissions and without catalog_permission management in a few days.
Thanks
Thanks