Tru Calling Download

1 view
Skip to first unread message

Darth Sanderson

unread,
Aug 5, 2024, 2:59:24 PM8/5/24
to minsterpcore
AHubSpot-provided phone number allows you to make outbound calls and receive incoming calls forwarded to your personal device. If you're a user with super admin permissions, you can acquire a HubSpot provided phone number then assign it to a team member.

We were pleased to have NA calling. However, there is currently no way of setting up call display to the receiving person so they know who is calling. And there is no point of escalation at Hubspot (quote/unquote from tech support) I see that people have been requesting it for a few years, and since the target market for HubSpot is b-b, the request makes total sense to me. I want to send this up the ladder, but there is no clear path to doing that...can anyone help me with a solution or at least like this post, to show support for this idea. I plan to find a way to escalate it to the president, I'm so desperate for it. I hope to be able to copy this to 4 of the executive team at HUbspot, 2 CTO's, the chief Customer Officer, and exec vp of product via LinkedIn. If you agree with me


I am a member of the Community team here at HubSpot. We appreciate the time you put in to provide this feedback regarding the Calling tool and the caller ID feature (the information that your contact sees on their device when you make an outbound call), and we understand that this feature is important for your business.


While we understand that it would be ideal to control how the caller ID is displayed to your contacts in every single phone call, the Caller ID is a complex feature that relies on the caller's and recipient's phone carrier systems and therefore cannot be configured in HubSpot. Here is a helpful overview of how the caller ID feature works.


If you've received reports from your contacts that they are seeing your caller ID displayed as "Unknown" or "No Caller ID", there are some best practices listed in this article which you can follow to help avoid caller ID issues.


We also appreciate your comment about our product feedback process; we realize that there is room for improvement here and we're working on an initiative internally to improve the product feedback experience for our customers.


You might have found this post in our Ideas forum which we use to collect product feedback: Configure caller ID name. I have shared your feedback internally with the product team and requested a status update for this feature request.


I'm completely new to zoom and I'm trying to set up Zoom Phone. There are still a few things confusing to me.

The call that I'm trying to make is from the Netherlands to the United States. So I do not have a US phone number only Dutch.



I got the unlimited US/Canada plan.


However, I am not able to assign any phone number. I added my dutch mobile phone number to my profile under "Personal". But I cannot change the Direct Number at all in that section. Does Zoom create/generate a phone number for me? A US number? Or how does this work?



I know something is wrong because when I go to my zoom desktop app and I try to call a US number I get:

"Sorry we cannot complete your call your service plan does not support calling to this destination"




I already checked "Billing" under "Account Management" and both the US and the Netherlands have been selected.



Again, I'm 100% new to this and maybe I missed a very obvious step.

Does anyone know how I could get it working?


I recently received the same error. The enablement team lead ,Zoe, figured out that you must choose a Caller ID. Yes, it's true "Hide my Caller ID" is an available option. Hiding your ID prevents the system from knowing your location.


It is likely that your direct line number is assigned successfully, but your Zoom Phone Call Out country has not been selected in the BILLING area. Kind of silly to have to choose that MULTIPLE locations for this to work but that's what fixed it for me.


It is likely that your direct line number is assigned successfully, but your Zoom Phone Call Out country has not been selected in the BILLING area. Kind of silly to have to choose that MULTIPLE locations for this to work, but that's what fixed it for me.


This article describes function calling and how to use it as part of your generative AI application workflows. Databricks Function Calling is OpenAI-compatible and is only available during model serving as part of Foundation Model APIs.


Function calling provides a way for you to control the output of LLMs, so they generate structured responses more reliably. When you use a function call, you describe functions in the API call by describing the function arguments using a JSON schema. The LLM itself does not call these functions, but instead it creates a JSON object that users can use to call the functions in their code.


Call the model again by appending the structured response as a new message. The structure of the response is defined by the functions you previously provided in tools. From here, the model summarizes the results and sends that summary to the user.


DBRX is provided under and subject to the Databricks Open Model License, Copyright Databricks, Inc. All rights reserved. Customers are responsible for ensuring compliance with applicable model licenses, including the Databricks Acceptable Use policy.


Foundation Model APIs broadly support function definitions accepted by OpenAI. However, using a simpler JSON schema for function call definitions results in higher quality function call JSON generation. To promote higher quality generation, Foundation Model APIs only support a subset of JSON schema specifications.


Prompt injection and other techniques are used to enhance the quality of tool calls. Doing so impacts the number of input and output tokens consumed by the model, which in turn results in billing implications. The more tools you use, the more your input tokens increase.


An elaborate chat completion prompt with function calling using 3.5 turbo seems to be worse than da vinci. Da vinci gave me more reliable json on the completions endpoint. It costed more tokens though.


I have tried putting in system messages and property descriptions telling it to NEVER call function if required arguments are missing etc. but it still calls the function regardless. I am utterly stuck , would appreaciate some assistance.


Put yourself in the shoes of the AI, the information you have is that contained in the API you are making at that very second, you have no history and you have no idea of the internal states of your codes parameters and variables.


As you state, the assumption has always been that the property values should be inferred from the prompt alone, no need for internal states, codes or variables. I think you may be referring to whether the function fires at all but here it is firing too often. If any required properties have been unable to be inferred, the function should not fire.


There are no validation layers or checks of any kind, this is all created by the AI being trained and fine tuned to create json formed output and to pick from an appropriate array of text identifiers that are the function names and descriptions, it is all still the AI behind the curtain doing smart things with the information it has at hand.


When crafting function calls you need to think about what information the AI has at that moment in time, what are the function names like? Informative? would it be clear to the AI what the function does and when it should use it? Imagine the AI is a new employee and you need to explain to it everything it needs to complete the task.


I will share some experience/light here since I had similar issue. I am using gpt4 and it was hallucinating with values that it has been trained on generic data. I was somehow able to override the hallucination by doing the following:


Whenever I place calls through the Hubspot dialer in the CRM, if the receiving party is using an iphone my call says "Potential Spam". Is there a way I can remedy this issue? Is this a problem with my personal phone number or is it because I am dialing through Hubspot?


There's a new extension in the marketplace (as of June 2023) that uses a STIR-SHAKEN carrier for your HubSpot calls to ensure you don't show up as "Spam Likely" on CallerID when making outbound calls.


This problem still exists. Whether the fault is on Twilio or not, I can't connect with my customers and prospects using HubSpot Desktop Web App.



And now I'm left wondering how many missed opportunities have accumulated over what period of time.


Since this is only a problem when the call is placed from a browser (not the iPhone App or me calling the number directly) isn't it a problem with Twillio? Wouldn't that be something HubSpot can develop a fix for with Twillio?


Having the same problem. The phone numbers are exacly the same on the caller ID but the calls that are connected through Teillio are flaged as SCAM LIKELY. This is not a good thing for sales people that are contacting clients. Someone needs to post a fix...


@EW2 : CA is following the US in terms of adopting STIR SHAKEN regulations for voice & text. It's just a bit behind the roll-out. You can use that HubSpot app extension I mentioned earlier and that should solve your problem. It signs all outbound calls with "A" attestation to signal to carriers you're legitmate.


I know none of that is concrete but it really depends on what country you're in, where you are calling, and what your volumes are. If you were in the US, it would be as simple as just using that HubSpot extension I mentioned in another comment.


I recently purchased an Australia and New Zealand Unlimited Plan, but have not been able to make any calls. Each time I have tried, I receive the following message "Sorry...the requested service is not available in your calling plan". Also, unable to receive calls too! So now I'm confused ( have I not set up properly, am I not dialling numbers correctly?) and worried that perhaps I have purchased an incorrect plan - although I made the purchase after long discussion and upon recommendation of Zoom's sale team.

3a8082e126
Reply all
Reply to author
Forward
0 new messages