# Calling from Contact View triggers onDialNumber event in Calling Extensions SDK with unintended objectId

**URL:** <https://community.hubspot.com/t/calling-extensions-sdk-ondialnumber-objectid/156206>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [August 17, 2026, 4:55am UTC](https://community.hubspot.com/t/calling-extensions-sdk-ondialnumber-objectid/156206 "2026-08-17T04:55:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuki.tanaka-revcomm](https://avatars.discourse-cdn.com/v4/letter/y/c2a13f/32.png) [@yuki.tanaka-revcomm](https://community.hubspot.com/u/yuki.tanaka-revcomm)\
**Post date:** [August 17, 2026, 4:55am UTC](https://community.hubspot.com/t/calling-extensions-sdk-ondialnumber-objectid/156206/1 "2026-08-17T04:55:25Z")

</div>

## Summary

We are developing a calling application for call integration using the Calling Extensions SDK ([GitHub - HubSpot/calling-extensions-sdk: A JavaScript SDK for integrating calling apps into HubSpot. · GitHub](https://github.com/HubSpot/calling-extensions-sdk)).

It appears that in the HubSpot CRM contact view (`/contacts/:id/objects/0-1/views/all/list`), the `onDialNumber` event is sometimes triggered with an unintended `objectId` when initiating a call by clicking a phone number for a specific contact record.

## Issue Details

### Steps to Reproduce

1. Open the HubSpot CRM contact view (`/contacts/:id/objects/0-1/views/all/list`).

2. Open the detail view for any contact record (Contact A) (`/contacts/:id/record/0-1/:objectId`) and initiate a call using the “Call” button → **In this case, the `onDialNumber` event is triggered with the correct `objectId` set.**

3. Return to the HubSpot CRM contact view (`/contacts/:id/objects/0-1/views/all/list`) using the web browser’s back button.

4. From the HubSpot CRM contact view (`/contacts/:id/objects/0-1/views/all/list`), click the phone number in the “Phone Number” column for any contact record (Contact B) to initiate a call → In this case, the `onDialNumber` event is triggered with the `objectId` for Contact A instead of Contact B.

### Expected Behavior

In step 4 of the “Steps to Reproduce” above, the `objectId` for Contact B should be passed.

## Impact

The calling application incorrectly assumes that a call was made to an unintended contact.

---

<div class="post-metadata">

**Author:** ![JSilva66](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@JSilva66](https://community.hubspot.com/u/JSilva66)\
**Post date:** [August 17, 2026, 8:19am UTC](https://community.hubspot.com/t/calling-extensions-sdk-ondialnumber-objectid/156206/2 "2026-08-17T08:19:06Z")

</div>

You should use read `calleeInfo.calleeId`

> **[​onDialNumber - Calling extensions SDK - HubSpot docs](https://developers.hubspot.com/docs/api-reference/latest/crm/extensions/calling-extensions/calling-sdk#ondialnumber)**
>
> Was this page helpful? | Overview of the calling extensions SDK