Hi @twilanswer,
Thanks for reaching out. To help us troubleshoot the "Call with Sidebar Demo" issue, could you please provide two key pieces of information?
-
Developer Console Errors: Please open your browser's developer console and then click the "Call with Sidebar Demo" option. Let us know if any errors appear, especially any network-related errors (they often appear in red).
-
SDK Version: Please confirm that you are using the latest version of our SDK. Using the most recent version is essential for the sidebar to function correctly.
This information will help us better investigate the source of the issue.
Best,
Justin
Hi @justin thanks for your reply. I’ve checked both of the items you recommended:
- Nothing appears in my console when triggering “Call with Sidebar Demo”. No errors or other console logs. I also don’t see any network calls at all (failed or otherwise) related to the “Call with Sidebar Demo” option.
- I’ve confirmed I’m using version 1.9.0 of the SDK.
Thanks
Hi @twilanswer!
Thanks for the detailed report and the video walkthrough—it was very helpful for our team's investigation.
We've tested this on our end but haven't been able to reproduce the behavior you're seeing; the "Call with" button from the contact preview is opening the plugin as expected. This suggests the issue may be specific to your local browser environment or machine.
To help narrow down the cause, could you please try triggering the "Call with Sidebar Demo" from an incognito or private browser window? This temporarily disables browser extensions, which can sometimes interfere with this functionality.
Let us know if that makes a difference. Thanks!
Hey @justin, I appreciate your help. I tried in an incognito window and that did not help.
To help with debugging, I uploaded the sample app to a Github repo and deployed it on Vercel. I’m not sure it would be relevant (since this error seems like it occurs prior to loading the page), but wanted to share in case.
Do you have any other thoughts on things to try debugging?
Thanks!
Hi! I’ve also been unable to reproduce this issue. I created a plug-in using your deployment, and it’s working as expected. 
Since nothing appears in the console or network logs on your side, could you let me know if this issue persists on our desktop app as well? What about if you use a different browser when testing?