Widget Integration
Once you have prepared the widget URL with the required parameters, embed it into your CRM platform. The embedding method depends on the CRM and version in use.
Microsoft Dynamics 365
CIF v2 (Omnichannel for Customer Service)
- Use the native Omnichannel framework to embed MiraBridge Phone.
- Configure the widget URL in the Omnichannel settings.
- Supports advanced multichannel features and real-time presence.
- 👉 See CIF v2 Setup
CIF v1 (Unified Interface / Customer Service Hub / Sales Hub)
- Use the Channel Integration Framework to add MiraBridge as a custom widget.
- Configure the widget URL in the CIF settings.
- Suitable for environments without Omnichannel licenses.
- 👉 See CIF v1 Setup
Custom Platforms
- Use a standard
<iframe>to embed MiraBridge Phone. - Provide the full widget URL as the iframe
src. - Adjust iframe size and styling as needed for your platform.
Passing Parameters
Make sure all required parameters (deploymentId, region, clientId) are included in the embedded widget URL. The deploymentId goes in the URL path, while region and clientId are query parameters. Optional flags like enableDebug and enableDiagnostics can also be added for debugging or diagnostics.
Example iframe Implementation
For custom platforms using iframe embedding:
<iframe
src="https://phone.mirabridge.cloud/api/v1/deployment/main/init?region=mypurecloud.de&clientId=your-client-id&enableDebug=true"
width="400"
height="600"
frameborder="0"
allow="microphone; camera; autoplay">
</iframe>
Important: Ensure the iframe includes
allow="microphone; camera; autoplay"to enable WebRTC functionality.
Testing Your Integration
After embedding the widget:
- Initial Load Test: Verify the widget loads without errors
- Authentication Test: Confirm agents can log in successfully
- Functionality Test: Test call handling, screen pops, and CRM automation
- Browser Console: Check for any error messages or warnings
- License Usage: Verify licenses are consumed and released properly