Hi Fatos, I’m experiencing issues with the Whitelabel Facepop where it’s showing ‘answerly’ for the img src when the widget is inspected. This causes issues with my target clients as they’re SaaS owners. These people are savvy enough to inspect the code… and the most obvious one is the img src showing Answerly immediately when inspected.
Other whitelabel issues are not that apparent so can you please prioritize fixing this so that I can proceed with selling the bot? ? (Note that I’ve reported this in another thread since about 2 weeks+ ago, and yes I have used the correct whitelabel embed code instead of non-whitelabel one)
Have you received any updates on this issue? I agree that we need to correct this. There should be no references in the code to Facepop, Answerly, or any domain that could lead someone back to those platforms.
I suggest that Answerly create a new domain name that doesn’t have any connection to Answerly or Facepop. This would be the preferred solution.
In your code above, I noticed that the image source (src) is also showing from “answerly.cloud/facepop/…”. Additionally, the alt tag contains “Facepop preview”. Both of these need to be changed so that there is no connection to Answerly or Facepop.
The Answerly code renders differently depending on whether you access our products directly or through your whitelabeled dashboards.
Please avoid using our official product dashboards, or your admin accounts, as references when analyzing mentions of our product names.
Our branding is not concealed in the official product dashboards, and many elements are still visible to white label administrators as well, even when accessing the whitelabeled dashboard.
Instead, use a client account logged into your whitelabeled dashboard, to analyze the full whitelabel experience.
That being said, all code visible to the user is currently fully whitelabeled. If your clients decide to dig into our source code, they might find traces of FacePop or Answerly.
However, these traces function merely as software resources, and not branding, such as a “Built by Answerly” label within the code.
I did mention that I’m using the whitelabelled client dashboard’s code, and not directly. However, inside code inspection it’s still immediately seen
→ Yes I use this “Instead, use a client account logged into your whitelabeled dashboard, to analyze the full whitelabel experience.”
See my photos, those are from a client account logged into my whitelabelled dashboard.
“However, these traces function merely as software resources, and not branding, such as a “Built by Answerly” label within the code.”
It’s not fully whitelabelled unless the source code is whitelabelled too.
@Fatos Please do fix the source code part for the image resource for Facepop, I think that’s pretty simple to fix, just need to point it to somewhere else that’s not Answerly for the image resource. Only that particular part of the code would suffice…
