It's not just about 'getting' the call queue, it's about adding to it, creating predefined call queues, etc.
Simple example: A marketing workflow, enrollment critiera: visited 20 pages in last 5 days, opened a marketing email, workflow step: add contact to owners 'Today's Calls' queue.
.... We would do that all day long.
Another example: Create Call Queue API -> For each salesperson in team X create queues call 'Followup Calls', 'First Contact Calls', 'Follow up emails'.
As a automation and data integration specialist, I would argue that nearly every piece of functionality available to an end user should be available as an api.
Please, Hubspot, adopt an api first development methodology.
Most, if not all of your key market competitors have.
"The ********** API landscape is as vast as the ocean blue. That’s because ********** takes an API-first approach to building features on the ********** Platform.
We want to drive consistent processes through automation.
Queues are way more useful with automation. Marketing automation can’t add a call to a queue when a customer event occurs that triggers a call. The task can be there, but to be able to drop it right into a call back queue… that’s where it’s at.
Queues are awesome. they should absolutely have their own first calls api representation.
.png "HubSpot Employee"){kind=icon}
