Need solution on marking wrong number for multiple numbers

In hubspot I am multiple properties for numbers
Phone Number (Hubspot)
Mobile Number (Hubspot)
Direct Cognism Number (Custom)
SDrs are dialling all numbers and marking numbers as wrong number in calling outcome
I want to add custom note next to every number if they marked as a wrong number so i can see in the contact section and apply filter with wrong number property

Hi @PPatil27

Thanks for sharing this — managing multiple phone number properties and keeping clear context for SDRs is definitely a common challenge.

I’d like to invite some Community members who are subject matter experts in calling workflows, contact properties, and SDR process design to join this conversation.
@GaroAroian @karstenkoehler @franksteiner79 — hope you’re all having a great week! Have you seen effective ways to capture which specific phone number was marked as a wrong number (e.g. via custom properties, workflows, or call outcomes) so it’s visible on the contact record and usable for filtering?

Any practical approaches or best practices here would be greatly appreciated.
Best,
Victor

I see your challenge with tracking wrong numbers across multiple phone properties. The built-in call outcome alone won’t tell you WHICH specific number was marked as wrong. Here’s the technical solution:

Option 1: Custom Wrong Number Tracking Properties (Recommended)

Create 3 custom single-line text properties:
• Phone_Number_Status (options: Valid | Wrong Number | Do Not Call)
• Mobile_Number_Status (options: Valid | Wrong Number | Do Not Call)
• Direct_Cognism_Status (options: Valid | Wrong Number | Do Not Call)

Then create a workflow:
Trigger: Call outcome = Wrong Number
Action: Branch based on Last called phone number property
IF contains [phone number value] → Update Phone_Number_Status = Wrong Number
IF contains [mobile value] → Update Mobile_Number_Status = Wrong Number
IF contains [cognism value] → Update Direct_Cognism_Status = Wrong Number

Option 2: Automated Note Creation (If on Professional+)

Workflow:
Trigger: Call outcome = Wrong Number
Action: Create note with template:
Wrong number flagged: {{Last called phone number}} on {{Date}}
Associate: To contact

This creates a timestamped record visible in the contact timeline.

Option 3: Single Invalid Numbers Property

Create multi-line text property: Invalid_Phone_Numbers
Workflow: When call outcome = Wrong Number, append:
{{Last called phone number}} - marked {{Date}}

Filtering Strategy:
Once you have status properties, create list filters:
• Phone_Number_Status is any of Wrong Number
• Mobile_Number_Status is any of Wrong Number
This lets SDRs see at a glance which specific numbers are bad.

Pro Tip:
If you’re using Cognism enrichment, also track WHY the number is wrong (disconnected vs wrong person) using a custom dropdown on the call record itself.

Let me know if that works for you!

Thanks for the solution i will try this and check

Hi @PPatil27, I’m completely biased here but if you’re looking for a solution that lets you validate phone numbers before your dialling campaigns, i’ve built an app that might help.

It’s called Clean Dial and works as a workflow action that checks if a number is valid/callable, along with some extra details like if it disconnected/reachable, carrier details, location details, voip status etc.

It writes back custom properties to the contact record like if the number is callable, a format check and timestamp so you can filter bad numbers before dialing.

I wrote a blog piece here on how you can use the validation propeties for filtering.

It currently works with the ‘Phone Number’ property, but i’ve got ‘Mobile Number’ property support coming soon (which would help with your multi-property setup).

I’d love to know if this is useful to you :slightly_smiling_face: