Call Outcomes filter not working for calls logged via Trellus (HubSpot-native dialer)

Smart CRM & Sales Hub Sales Hub Tools
1

Hey everyone,

I use Trellus as my dialer — it runs inside HubSpot and logs calls directly as “Logged call” entries with a Call Outcome set (e.g. “Activated Lead”). The outcome is clearly visible on the contact’s activity record.

However, when I filter contacts in the list builder using Call Outcomes is any of Activated Lead, no contacts appear, even for contacts where the outcome is confirmed on the call record.

My understanding is that the native Call Outcomes contact filter only updates when calls are made through HubSpot’s own built-in dialer, not through dialers like Trellus, even though Trellus operates natively inside HubSpot.

My questions:

  1. Is this correct, or is there a setup issue on my end?
  2. Is there a way to make the Call Outcomes filter recognize calls logged via Trellus?
  3. If not, what’s the recommended native workaround?

For context — I’m on Sales Pro and currently working around this with a custom script that reads call outcomes and writes them to custom boolean contact properties, which I can then filter by. It works but requires a manual refresh after each call session.

Thanks!

2

Hi @SPG_Chris, this is expected, not a bug on your end. The filter reads the hs_call_disposition property on the Call engagement, and it only matches if that’s set to the exact internal outcome ID, not just a label that looks right on the timeline. Third-party dialers can show a matching outcome visually without writing to that field correctly, so the filter finds nothing.

Worth confirming with Trellus support whether they’re mapping to HubSpot’s native disposition IDs.

Native workaround for your script is build a workflow triggered on Call was logged, branch on the call’s Call Outcome property, and write to your custom field from there. Runs automatically, no manual refresh needed, though it still won’t help if Trellus isn’t setting the disposition property at all.

3

Thanks tee. I was trying to figure out how to do that automatically but the only solution I could come up with was to create an ‘action’ to rerun after every call logged but it looks like that feature is only available in Sales Enterprise and not Pro.

Can you advise if there is a way to do this with sales pro?

5

Thanks tee. I was trying to figure out how to do that automatically but the only solution I could come up with was to create an ‘action’ to rerun after every call logged but it looks like that feature is only available in Sales Enterprise and not Pro.

Can you advise if there is a way to do this with sales pro?

6

From what you’ve described, it sounds like a limitation rather than a configuration issue.

The Call Outcome list filter is generally most reliable for calls created through HubSpot’s native calling functionality. Many third party dialers, even those embedded in HubSpot, log call engagements with an outcome, but those values don’t always populate the contact level fields that HubSpot’s list filters rely on.

If Trellus is only creating a logged call engagement, the activity timeline will show the outcome correctly, but the contact filter may not recognize it.

A few native workarounds you could consider are:

  • Use a workflow to copy the latest call outcome into a custom contact property (if the call outcome is available as a workflow trigger in your portal).

  • If workflows can’t access that data, your current approach of syncing the outcome into custom contact properties is a practical solution.

  • You could also check with Trellus to see whether they support syncing call outcomes directly to a contact property in addition to logging the engagement.

I’d also be interested to hear if anyone has managed to get the native Call Outcome filter working with Trellus without using custom properties.

7

Unfortunately, there isn’t a native way to trigger a workflow from a Call was logged event in Sales Hub Professional. That trigger is currently available only in Sales Hub Enterprise.

With Sales Pro, your options are fairly limited:

  • Ask Trellus to map the correct HubSpot hs_call_disposition value directly when creating the call engagement (this is the most reliable fix).

  • Use a custom integration or API/middleware (e.g., Zapier, Make, or a private app) to update the contact after the call is created.

If your goal is simply to populate a custom property based on the call outcome, I’d recommend checking with Trellus first to see if they can write the native disposition ID during call creation. That would allow your existing filters to work without requiring Enterprise.

Hope that helps.