Conversations

Integrate Third Party Phone Systems such as GoToConnect or RingCentral - Improve API To Add Conversations
Idea: let us use a third party, dedicated phone system such as GoToConnect or RingCentral to place and receive all calls (and texts) - and integrate that with Go High Level.This will give you world class phone features, such as caller ID integration, advanced call routing and multidevice support (not to mention unllimited calls and free texting).As it stands, the conversation view in Go High Level will not include any calls made on our desk phone system, and there is no way to link them via the API.Unless you only use the soft phone to make all outbound lead and customer calls, currently the Go High Level customer conversation will only show the inbound calls, which makes it very limited.Extending the Go High Level API would fix this.For example, we use GoToConnect by LogMeIn. That system allows unlimited texts and calls and has an API to access the full call history.If you extended the Go High Level API to allow us to add conversations (phone and text) from other systems, it would be fairly straightforward to bring all of the information into Go High Level, regardless of which system actually was used. (If you can extend the API, I would be happy to write the integration and share it.)Note - this would also let you keep your existing phone numbers and skip Twilio altogether. It's simple to port numbers to GoToConnect (we did). You could use GoToConnect to make and receive all texts and calls, even to record them, and then they could be linked to Go High Level via this improved API.I get that Go High Level wants to be a "one stop shop" but without an extended API you are ending up with a mediocre version of everything and no way to integrate "best of breed" tools for those that want them.All we need is a few extra nodes on the API to post new phone and text conversations and, ideally, associate a WAV file recording. HIGHLVL-I-2437
37
·
under review
When emailing a contact, the FROM address defaults to the address of the currently logged-in HL user, when it SHOULD default to the email address specified in Settings > Email Services for the account
When emailing a contact via the HL UI, the FROM email address should always default to the email address specified in that account's Setting > Email Services configuration. Failing to do so is irrational, as defaulting to sending FROM the email address assigned to the currently logged-in user means SMTP authentication will fail, except in rare instances where it just so happens the currently logged-in user has the exact same email address as the one specified in Settings > Email Services. This is particularly egregious when one has an Agency with many subaccounts, all of whom are for different users. Example: Say my name is Bob Smith, email bob@smith.com , and I log into my account as an Agency admin. I have subaccounts for different staff members: Jim Johnson, jim@johnson.com , and Kevin Nations, kevin@nations.com . Each one of these users wants to communicate with their contacts using their own email address, so SMTP auth for each account is of course set up to use their respective email address (and, of course, their address will be used 95% of the time, since they will be the ones using the account). Because HL is configured illogically in-regards contact email FROM settings, every time I go to a specific subaccount, and attempt to send a contact an email, HL defaults to sending from bob@smith.com , my email, instead of jim@johnson.com , the email configured in Settings > Email Services.. So every single email I send to a contact on Jim Johnson's account, I have to edit the FROM field every single time. And every other user has to do the exact same thing any time they access any other subaccount that isn't their own.
45
·
Enhancement
Load More