Summary and recommendation
Talkdesk supports SCIM 2.0 for user provisioning across all pricing tiers, starting at $85/user/month for CX Cloud Essentials. However, SCIM implementation isn't publicly documented, forcing IT teams to work directly with Talkdesk support for setup and troubleshooting. This creates deployment friction and ongoing maintenance challenges, especially for organizations that need reliable, self-service provisioning workflows.
The lack of public SCIM documentation means you're dependent on Talkdesk's support team for configuration guidance, API changes, and troubleshooting. For contact centers managing hundreds of agents with frequent turnover, this dependency can slow onboarding and create compliance gaps when user access isn't provisioned or deprovisioned promptly.
The strategic alternative
Talkdesk gates SCIM behind Enterprise. Skip the Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ✓ | Gallery app with SCIM |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Talkdesk accounts manually. Here's what that costs:
The Talkdesk pricing problem
Talkdesk gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure (Billed Annually, 3-Year Contract)
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| CX Cloud Essentials | $85/user/mo | ||
| CX Cloud Elevate | $115/user/mo | ||
| CX Cloud Elite | $145/user/mo |
Note: Healthcare and Financial Services editions start at $225/user/mo. All plans include SCIM 2.0 support, but implementation relies on undocumented configuration.
What this means in practice
The hidden costs aren't in pricing tiers—they're in implementation complexity:
Documentation gap: Talkdesk's SCIM implementation isn't publicly documented. IT teams must rely on support tickets and trial-and-error configuration, extending deployment timelines by weeks.
IdP-specific workarounds: While Okta and Entra ID have some integration guidance, the lack of standardized documentation means each IdP requires custom troubleshooting.
Ongoing maintenance risk: Without public API documentation, troubleshooting provisioning failures requires vendor support escalation rather than self-service resolution.
Additional constraints
Summary of challenges
- Talkdesk supports SCIM but only at Enterprise tier (custom pricing)
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
Talkdesk includes SCIM provisioning across all tiers, but the implementation has significant gaps:
The core issue isn't pricing tiers—it's that Talkdesk doesn't publicly document their SCIM implementation. While they support SCIM 2.0 through their API and have working integrations with major IdPs, IT teams are left to piece together configuration details from scattered support articles and third-party documentation.
For contact centers that need reliable user provisioning, this creates operational risk. You're getting SCIM functionality, but without proper documentation or clear support channels when things break.
What IT admins are saying
Community sentiment on Talkdesk's SCIM implementation is mixed, with frustration centered around documentation gaps and setup complexity. Common complaints:
- SCIM functionality exists but isn't publicly documented
- SSO and provisioning setup requires extensive coordination with Talkdesk IT teams
- Limited visibility into SCIM capabilities and limitations before implementation
- Rate limiting restrictions (4 requests/second) can slow bulk provisioning operations
The SCIM integration works but figuring out how to configure it properly was a nightmare - their support docs don't cover half the edge cases we ran into.
Why isn't SCIM documented anywhere public? We had to go through three different support channels just to get the API endpoints.
The recurring theme
While Talkdesk offers SCIM on all tiers, the lack of transparent documentation creates unnecessary friction for IT teams trying to implement automated provisioning.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM but want public documentation | Use Stitchflow: get documented automation without the guesswork |
| Using Google Workspace as your IdP | Use Stitchflow: Talkdesk doesn't support Google SSO natively |
| Want hands-off provisioning setup | Use Stitchflow: avoid IT coordination headaches for SSO/SCIM |
| Already have Talkdesk SSO working smoothly | Try native SCIM: you have the foundation in place |
| Small contact center, stable headcount | Manual may work: but monitor for provisioning gaps during busy seasons |
The bottom line
Talkdesk offers SCIM 2.0 but keeps the implementation details undocumented, forcing IT teams into trial-and-error setup processes. For contact centers that need reliable, documented provisioning automation, Stitchflow delivers managed SCIM with full transparency and 24/7 support.
Make Talkdesk workflows AI-native
Talkdesk gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
None
Key limitations
- SCIM not publicly documented
- SSO setup requires IT department coordination
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
Where to enable
Required credentials
SCIM endpoint URL and bearer token (generated in app admin console).
Configuration steps
Enable Create Users, Update User Attributes, and Deactivate Users.
Provisioning trigger
Okta provisions based on app assignments (users or groups).
Docs
Enterprise required for SCIM
Talkdesk gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
Where to enable
Required credentials
Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).
Configuration steps
Set Provisioning Mode = Automatic, configure SCIM connection.
Provisioning trigger
Entra provisions based on user/group assignments to the enterprise app.
Sync behavior
Entra provisioning runs on a scheduled cycle (typically every 40 minutes).
Enterprise required for SCIM
Talkdesk gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Talkdesk
Talkdesk gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works
