You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
##Q: I don't see any new tab or window opening on incoming calls.
9
+
10
+
A: When a call comes in, it rings on your softphone (or any other client with the same account). Simultaneously, the call log section in RC for Dynamics with matched entities will expand from the sidebar.
11
+
12
+
##Q: I can see some phone numbers in Dynamics, but the click-to-call icon is not displayed.
13
+
14
+
A: By default, the phone icon is present on Business Phone and Mobile Phone fields as they are of phone type. To see a phone icon beside other phone numbers for click-to-dial functionality, those fields must be configured as "Phone" fields. This configuration needs to be done separately by your administrator following the admin guide (https://assets.ringcentral.com/us/guide/admin-guide/dynamics_beta_admin.pdf) on page 15, Step 4: Enable Click to Dial with RingCentral Description.
15
+
16
+
##Q. Why isn't the RingCentral panel showing up for users?
17
+
18
+
A. After an admin completes the installation for RingCentral for Dynamics integration and CIF from the Power Platform (https://admin.powerplatform.microsoft.com/), there could be two reasons why:
19
+
20
+
Reason 1:
21
+
22
+
- Ensure that the app where the user is trying to access the RingCentral integration is added as part of 'Select Unified Interface Apps for Channel' in the Channel Integration Framework (CIF) setup.
23
+
- Ensure the user role of those not seeing the integration is added to the 'Select the Roles for Channel'.
24
+
25
+
Reason 2:
26
+
27
+
- Ensure that 'Channel Access' is included in the 'Select the Roles for Channel'.
28
+
29
+
All of this information is included in the RingCentral for Dynamics 365 admin guide (https://assets.ringcentral.com/us/guide/admin-guide/dynamics_beta_admin.pdf) on page 11, Step 3: Enable RingCentral for Dynamics.
30
+
31
+

32
+
33
+
##Q. Why do missed calls get logged to Dynamics 365, even after deselecting the options for "Missed calls with voicemail" and "Missed calls without voicemail" in the integration console?
34
+
35
+
A. Integration Console settings are specific to server-side call logging. This means when a user receives a missed call with or without voicemail on any RingCentral platform apart from the RingCentral for Dynamics integration inside Microsoft Dynamics 365, these calls do not get logged to the contact/account/leads/opportunities.
36
+
37
+
All other settings configured in the integration console (integrations.ringcentral.com) are only applicable for server-side calls (outside the RingCentral for Dynamics 365). Any call operations performed inside the RingCentral for Dynamics 365 integration within Microsoft Dynamics 365 are called client-side operations.
Copy file name to clipboardExpand all lines: docs/salesforce/questions.md
+122Lines changed: 122 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -389,3 +389,125 @@ In such cases, we recommend users follow these steps:
389
389
390
390
- Set the RingCentral for Salesforce integration app calling option to "call with RingCentral app." This allows the actual phone calls to be handled by the RC desktop app, while the CTI app should still be able to monitor and log calls.
391
391
- If users still experience audio issues, the problem may be with their network. We recommend users work with their IT department to disable the firewall and test calls or switch to a different network.
392
+
393
+
##Q. Why do I keep getting "A maximum of 5 web phones could be registered" error message?
394
+
395
+
A. This error occurs when more than 5 RingCentral webphone instances are already registered for your user account. RingCentral has a hard limit of 5 concurrent webphone registrations per user.
396
+
397
+
The error is part of RingCentral's WebRTC session management system that prevents resource abuse and ensures call quality. The limit applies across all RingCentral applications (Salesforce, Google, Outlook, Web App, etc.) for the same user account. When you hit this limit, you cannot make outbound calls until you reduce the number of active webphone registrations below 5.
398
+
399
+
**Common Scenarios That Cause This Error**:
400
+
401
+
- You have RingCentral open in 5+ browser tabs or windows
402
+
- Multiple RingCentral Applications (RingCentral for Salesforce, RingCentral for Google, RingCentral desktop, web and mobile apps)
403
+
- Multiple users accessing a single account on different devices
404
+
- Previous sessions didn't properly disconnect, leaving orphaned webphone registrations still active on the server
405
+
406
+
**Solution**:
407
+
408
+
- Close RingCentral tabs in other browsers and unused RingCentral Applications
409
+
- Go to RingCentral Web App → Settings → Switch account or Logout. Logout from other RingCentral applications
410
+
- Restrict access to the RingCentral webphone to only the account owner; avoid sharing credentials with other users
411
+
- Clear cookies and local storage for RingCentral domains. This forces fresh registration
412
+
413
+
##Q. How does the Sales Engagement feature work with RingCentral?
414
+
415
+
A. We recommend that the Salesforce admin verify the completion of the Sales Engagement setup by referring to the admin guide (https://netstorage.ringcentral.com/guides/rc-for-salesforce-admin-guide.pdf) on page 58. We must also verify if the customer has followed the exact steps mentioned in https://support.ringcentral.com/article-v2/RingCentral-Salesforce-High-Velocity-Sales-Add-on.html?brand=RC_US&product=RingEX&language=en_US. If the customer has followed the guide and still encounters issues, please collect a meeting recording demonstrating the problem and share it with RingCentral support to troubleshoot the issue.
416
+
417
+
##Q. I do not see the 'Sales Engagement Disposition' field while logging a call in RingCentral for Salesforce CTI.
418
+
419
+
A. Users do not see the Sales Engagement Disposition picklist field in the create call log screen if they initiate the call from the RingCentral for Salesforce CTI dialer itself or through the Click to Dial feature. This field only appears when a user initiates the call from the Sales Cadence work queue call button beside the contact. If this field still does not appear when the call is initiated from the work queue, then the Salesforce admin needs to check a few configurations in their Salesforce environment.
420
+
421
+
**Log Customization**:
422
+
Check if the 'Sales Engagement Disposition' field is added to the Selected fields from the Log Customization admin UI settings.
423
+
424
+
- Go to Setup → Search for Visualforce Pages in the quick find
425
+
- Select adminUI → click Preview to open the RingCentral adminUI settings
426
+
- Scroll down to 'Log Customization' section
427
+
- Ensure Sales Engagement Disposition field is added to Selected fields from the Available Fields
428
+
429
+
**Check the Field Level Security**:
430
+
431
+
- Go to Setup → Object Manager → Task/Activity → Fields & Relationships
432
+
- Click the field (Sales Engagement Disposition)
433
+
- Click Set Field-Level Security
434
+
- Ensure the profile used by the users has Visible access checked
435
+
436
+
**Add field to the Task Layout**:
437
+
438
+
- Go to Setup → Object Manager → Task
439
+
- Open Page Layouts
440
+
- Edit the layout users are using
441
+
- Drag the missing field (Sales Engagement Disposition) onto the layout
442
+
- Save
443
+
444
+
##Q. When does the Cadence move to the next step with RingCentral for Salesforce integration?
445
+
446
+
A. It should be noted that according to the implementation, the cadence only moves to the next step under specific conditions.
447
+
448
+
**Mandatory Sales Engagement Disposition field**:
449
+
450
+
The call will NOT move to the next step until:
451
+
452
+
- The call is logged as a Salesforce task AND
453
+
- A disposition value is selected AND
454
+
- The call log is saved
455
+
If the disposition is not selected:
456
+
- An error toast "Mandatory fields are required" will appear
457
+
- The call will not be logged as a Salesforce task
458
+
- The Sales Engagement work will remain in the same step.
Copy file name to clipboardExpand all lines: docs/zendesk/questions.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,28 +6,36 @@ hide:
6
6
# General Questions
7
7
8
8
## Q. I can't see RingCentral for Zendesk when I log in to Zendesk. What is the problem? Does it require some special permission?
9
+
9
10
A. No, RingCentral for Zendesk does not require any special permissions and should work for all user profiles. Please ask your Zendesk Administrator to ensure that RingCentral for Zendesk is enabled for the Zendesk role you are a member of.
10
11
11
12
## Q. Can I use the same RingCentral for Zendesk across multiple Zendesk instances?
13
+
12
14
A. Yes, you can. You will need to contact your Zendesk Administrator to set up and enable the RingCentral Cloud App for Zendesk for each of your instances.
13
15
14
16
## Q. Can I use the same RingCentral for Zendesk across multiple browsers (e.g., Internet Explorer and Firefox)?
17
+
15
18
A. Yes, you can use the same RingCentral for Zendesk across as many browsers as you want, provided that the user is not logged into two or more browsers simultaneously. This means that the user cannot be logged into Zendesk on Internet Explorer and Firefox at the same time. Simultaneous logins are not supported.
16
19
17
20
## Q. When I make a call to my own extension, the incoming call features are not functioning.
21
+
18
22
A. This behavior is expected. Calls from your own extension to your own extension will not appear in RingCentral for Zendesk.
19
23
20
24
## Q. I would like to disable this feature for now.
25
+
21
26
A. To disable this feature, you will need to contact your Zendesk Administrator. Request that they remove your Zendesk user role from RingCentral for Zendesk through the settings.
22
27
23
28
## Q. Search results are not displaying records that match the caller ID.
29
+
24
30
A. Check the format of the phone number in Zendesk. Ensure the format is standardized according to Zendesk features.
25
31
26
32
## Q. On logging into the RingCentral for Zendesk, users are getting this error message: "Your RingCentral edition does not support Zendesk Integration ‒ please call your RingCentral account representative to upgrade your RingCentral edition." What does that mean?
33
+
27
34
A. Not all RingCentral editions have the ability to use the Zendesk integration. You may have to upgrade your account to be able to
28
35
use this feature. Please contact your RingCentral representative for more information.
29
36
30
37
## Q. It is possible to create Zendesk tickets for all the voicemail messages, missed calls, texts or faxes that you get on your RingCentral phone?
38
+
31
39
A. Log into your RingCentral account at http://service.ringcentral.com by entering your RingCentral phone number and password. Navigate to Settings and expand the "Messages & Notifications" dropdown menu. Click "Edit" under Settings. (Figure below)
@@ -43,11 +51,13 @@ When a caller leaves a voicemail on your RingCentral phone, an email is sent to
43
51
Once you log into Zendesk, you will see these new tickets assigned to the group associated with the email. If the ticket was created with a voicemail, the newly created Zendesk ticket will contain a recording of the voicemail, allowing you to listen to the message left by the caller.
44
52
45
53
## Q: Tickets are not created for inbound and outbound phone calls made from RingEx by RingCentral in Zendesk
54
+
46
55
A. Users need to ensure the toggles 'Ticket on Outbound Calls' and 'Auto Create Ticket' are enabled in the integration settings. When these settings are enabled, for inbound calls, a ticket should be created in Zendesk as soon as the user accepts the call. For outbound calls, tickets are created as soon as the user dials the call.
## Q. How do I check the call data inside a ticket created by RingCentral integration?
60
+
51
61
A. The call data are updated to the RingCentral custom fields: Last Call Start, Last Call End, and Last Call Duration. If users are not seeing these fields in their ticket form, we recommend that a Zendesk admin user navigate to Zendesk Admin Center > Object and Rules > Tickets > Forms. Then, select the form the user has or the default form and add the fields mentioned above. Perform a test call, and the user should see these fields populated.
52
62
53
63

@@ -58,3 +68,9 @@ A. There are a couple of reasons why Zendesk tickets are assigned to the admin u
58
68
59
69
- If the admin selected the 'Default Zendesk rules (Recommended)' option and there are no set triggers and rules set up in Zendesk, then all the tickets created by the agent will be assigned to the admin user who completed this step in the RingCentral integration console. We recommend this option to be selected to automate ticket assignments to adhere to your Zendesk instance's set triggers and rules. Only users with appropriate permissions will receive assigned tickets.
60
70
- If the Zendesk admin selects the 'Admin-based access' option, then it will always be admin-specific ticket assignment. Any agent can create a ticket through RingCentral, but these tickets will be assigned to the admin user.
71
+
72
+
##Q. The "Ticket on Outbound Calls" option is grayed out, and there is no option to change it. The settings made in the integration console to not create tickets for outbound calls do not work.
73
+
74
+
A. The toggles "Tickets on Outbound Calls" and "Auto create tickets" will be grayed out for all users, as these configurations are controlled by the admin on the integration console (integrations.ringcentral.com). To enable these settings for all users, we recommend that the admin user disable Activity Sync from the integration console.
75
+
76
+
Integration Console settings are specific to server-side call logging. This means outbound calls made outside of Zendesk CTI (RingEx by RingCentral in Zendesk) will not create a ticket based on the customer's Integration Console settings.
0 commit comments