Thank you for correcting me Nivedraj and for testing that.
That's useful to know, as it confirms that removing Conversation > Call > Add impacts both manual outbound dialing and CRM Click-to-Dial functionality.
At this point, I'm not aware of a specific permission or configuration that would allow Click-to-Dial while preventing manual dialing through the New Interaction option.
Hopefully someone from the community who has implemented a similar CRM-only outbound dialing model can share their experience or suggest an alternative approach.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 06-01-2026 08:54
From: Nivedraj P
Subject: Embeddable Framework: Prevent Manual Dialing and Enable CRM Click-to-Dial Only
Hi Phaneendra Avatapalli,
I couldn't find the Conversation > Call > Create permission. However, I can see the Conversation > Call > Add permission.
When I removed the Conversation > Call > Add permission, all outbound calling functionality was restricted, including Click-to-Dial.
Our requirement is to disable manual dialing through the New Interaction option while still allowing agents to make calls using Click-to-Dial from the CRM.
Is there a specific permission or configuration that would allow Click-to-Dial while preventing manual dialing?
------------------------------
Nivedraj P
x
------------------------------
Original Message:
Sent: 06-01-2026 05:24
From: Phaneendra Avatapalli
Subject: Embeddable Framework: Prevent Manual Dialing and Enable CRM Click-to-Dial Only
Hi Nivedraj,
I noticed the attached configuration already includes:
hideNewInteractionState: true
Since you're still asking the question, I'm assuming either that setting is not having the desired effect in your environment or it behaves differently than expected.
From my understanding, there isn't a documented native Embeddable Framework setting that reliably removes the New Interaction option itself. If the objective is to prevent manual outbound dialing, it may also be worth testing the Conversation > Call > Create permission, as that should prevent agents from manually initiating calls even if the UI element remains visible.
Hopefully someone from community would add more to this.
------------------------------
Phaneendra
Technical Solutions Consultant