Thanks for the suggestion! Yes, I’ve confirmed that my onCallerIdMatchSucceeded handler is properly defined inside my eventHandler code.
I have handlers set up for all events, including catch-alls for unhandled events that log to the console, so I’m confident nothing is being missed on my end.
At this point, I’m increasingly convinced there’s a fundamental issue with how HubSpot is handling inbound call notifications.
I currently have two open community posts regarding issues with onCallerIdMatchSucceeded and onCreateEngagementSucceeded events. What’s notable is that both of these issues are specifically occurring with inbound calls when using:
cti.incomingCall
When I trigger outbound calls using:
cti.outgoingCall
I successfully receive the onCreateEngagementSucceeded event as expected.
This works consistently.
Given this pattern, I’m now strongly suspecting there’s a bug in the SDK on HubSpot’s side that’s preventing both onCreateEngagementSucceeded and onCallerIdMatchSucceeded events from firing correctly for inbound calls.
I’ve considered submitting this through the Developer Feedback form, but in my experience, there’s typically no response or follow-up from HubSpot through that channel.
Is there anyone from HubSpot who could investigate this and confirm whether there’s a known issue with inbound call event handling?
I’d really appreciate any guidance on the proper escalation path for what appears to be an SDK bug.
Thanks for any help you can provide!