feedback

In Review

<p>Stop populating a contact with Frivolous log entries and give the user the option to log or not. Without the choice, we populate the contact for no reason. Here's an example: <a target="_blank" rel="noopener noreferrer nofollow" href="https://share.nmblc.cloud/7918c641">https://share.nmblc.cloud/7918c641</a></p><p>On another note that I will be logging as well, it appears that Crelate and RingCentral are not talking to each other fluidly and henceforth are not bringing over notes and summaries of calls that are generated in RingCentral. This is caused by the Crelate app that is incapable of incorporating the full resources of RingCentral.</p>

Stop populating a contact with Frivolous log entries and give the user the option to log or not. Without the choice, we populate the contact for no reason. Here's an example: https://share.nmblc.cloud/7918c641On another note that I will be logging as well, it appears that Crelate and RingCentral are not talking to each other fluidly and henceforth are not bringing over notes and summaries of calls that are generated in RingCentral. This is caused by the Crelate app that is incapable of incorporating the full resources of RingCentral.

Fred Khachi

Stop populating a contact with Frivolous log entries and give the user the option to log or not. Without the choice, we populate the contact for no reason. Here's an example: [https://share.nmblc.cloud/7918c641](https://share.nmblc.cloud/7918c641)

On another note that I will be logging as well, it appears that Crelate and RingCentral are not talking to each other fluidly and henceforth are not bringing over notes and summaries of calls that are generated in RingCentral. This is caused by the Crelate app that is incapable of incorporating the full resources of RingCentral.



RingCentral Frivolous log entries

Subscribe to post