Calling widget cannot be closed

Hi all,

I’ve found that when an inbound call ringing, it’s impossible to close the calling app widget if it was already open. Trying to do so simply has the Hubspot site opening it automatically again.

Is this intended behavior? Depending on the size of your widget this can be quite disruptive.

Hi @JeroenCloudCTI! Are you using HubSpot calling or another integration? When using HubSpot calling, the calling window must remain open to receive inbound calls as noted in the Knowledge Base article.

Hello @kennedyp, thank you for your response.

I’m indeed using the calling integration. What you’re describing is a different scenario, it’s still voluntary; you should keep the window open if you want to receive inbound calls, but you can close it if you want.
The situation I’m trying to describe is involuntary; Hubspot does not allow me to close the window, it reopens it immediately if I do.

Thank you for the clarification! Do you experience this behavior in other browsers as well?

Yes, it is the same in Edge, Firefox and Chrome. When I answer the inbound call, I’m able to close the window again, but not as long as it is ringing.

Interesting. Is this the calling window you are referring to? I want to make sure we are testing the same tools.

When I tested this behavior, I was able to successfully minimize and close that widget with no issue. Minimizing it just got it out of the way and closing it declined the call.

I am talking about the calling widget that can be opened by clicking the phone icon in the top header bar on the right.

To additionally clarify: I haven’t tested with calling within hubspot yet, I’ve only tested manually triggering the Calling SDK in my app to use the incomingCall, callAnswered and callEnded methods.

Hey @JeroenCloudCTI! Thanks for your patience while I was out of the office. That widget is the one I used for the pop up in my example as well, but I did use HubSpot calling. The issue may be related to your calling configuration. Do you have more context on that? Have you confirmed if the behavior continues if using HubSpot calling instead?

By now the issue does not occur anymore, thankfully, though I do not know why. I do not have HubSpot calling, so I unfortunately wasn’t able to verify if the behaviour also occurs when using that.