Summary and recommendation
Aircall, the cloud-based phone system for customer support and sales teams, does not offer native SCIM provisioning on any plan. While the platform does support SAML 2.0 SSO (available only through account manager request), user provisioning requires a third-party connector from Aquera that only works with Okta. This creates a problematic dependency on external vendors and limits IT teams to a single identity provider ecosystem, even on Aircall's Custom/Enterprise plan that starts at 25 users minimum with custom pricing.
The reliance on third-party provisioning connectors introduces operational risk and vendor lock-in that most IT teams want to avoid. Organizations using Azure AD, Google Workspace, or OneLogin are left with no automated provisioning option, forcing manual user management for a platform that handles sensitive customer communications. This gap becomes particularly problematic for growing support teams where rapid onboarding and offboarding is critical for maintaining security and compliance standards.
The strategic alternative
Stitchflow provides managed provisioning automation for Aircall that works with any identity provider—Okta, Azure AD, Google Workspace, or OneLogin—regardless of your Aircall plan. Flat pricing under $5K/year with SOC 2 Type II certification and 24/7 human-in-the-loop support.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No native SCIM. Aquera connector provides create, update, deactivate, delete users. SOC 2 Type II audited service. Aircall planning native Okta OIN integration. |
| Microsoft Entra ID | Via third-party | ❌ | No Azure AD/Entra ID SCIM integration documented. |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Aircall accounts manually. Here's what that costs:
The Aircall pricing problem
Aircall gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Essentials | $30/user/month (annual) | ||
| Professional | $50/user/month (annual) | ||
| Custom/Enterprise | Contact sales (25-user minimum) | ⚠️ Okta only (via Aquera) |
Pricing structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Essentials | $30/user/month (annual) | ||
| Professional | $50/user/month (annual) | ||
| Custom/Enterprise | Contact sales (25-user minimum) | ⚠️ Okta only (via Aquera) |
What this means in practice
For a 100-user organization on Professional plans ($50/user/month), upgrading to Custom for provisioning functionality means:
The real problem is architectural: Aircall built their platform without identity management in mind, forcing customers to rely on external solutions that create additional failure points.
Additional constraints
Summary of challenges
- Aircall does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What Aircall actually offers for identity
No Native SCIM Support
Aircall does not offer native SCIM provisioning. The only automated provisioning option requires a third-party connector:
| Feature | Support Level |
|---|---|
| Native SCIM | ❌ None |
| Okta provisioning | ✓ Via Aquera third-party connector only |
| Azure AD/Entra provisioning | ❌ None |
| Google Workspace provisioning | ❌ None |
| Generic SCIM | ❌ None |
SAML SSO (Limited Availability)
Aircall's SSO implementation has significant restrictions:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Availability | Limited - must request from account manager |
| Self-service setup | ❌ No |
| IdP-initiated login | ❌ Not supported |
| JIT provisioning | ❌ No |
Critical limitation: SSO is not available as a standard feature. You must contact your Aircall account manager to request SSO enablement, and approval is not guaranteed.
Aquera Third-Party Connector (Okta Only)
The only provisioning option uses Aquera's third-party service:
Why this falls short: Third-party connectors introduce additional points of failure, vendor dependencies, and security considerations. You're essentially trusting a connector service to maintain uptime and security for your identity workflows, with no direct support relationship if issues arise.
What IT admins are saying
Community sentiment on Aircall's identity management reveals significant frustrations around their third-party dependency and enterprise gatekeeping:
- No native SCIM support forces reliance on third-party connectors like Aquera
- SSO requires special approval from account managers rather than self-service setup
- High 25-user minimum just to access enterprise features like automated provisioning
- Even higher-tier plans include only one phone number, forcing additional per-number fees
SSO not self-service - must contact account manager to enable
IDP-initiated SAML sign-in not supported
SSO limited availability - must request from account manager
The recurring theme
Aircall treats identity management as a premium service requiring sales conversations and third-party vendors, rather than a standard IT requirement. Teams end up paying enterprise prices and managing additional vendor relationships just to automate basic user lifecycle tasks.
The decision
| Your Situation | Recommendation |
|---|---|
| Small call center (<25 agents) | Manual management acceptable, but watch for growth |
| Growing team approaching 25+ users | Use Stitchflow: avoid the Custom plan jump and third-party complexity |
| Enterprise with Okta requiring automation | Evaluate Aquera connector vs. Stitchflow simplicity |
| Multi-IdP environment (Entra, Google Workspace) | Use Stitchflow: Aquera only supports Okta |
| Compliance-focused organization | Use Stitchflow: direct SCIM beats third-party dependency |
The bottom line
Aircall forces you into expensive Custom plans and third-party connectors for basic provisioning automation. With no native SCIM and SSO requiring account manager approval, Stitchflow delivers the modern identity management that Aircall should have built.
Automate Aircall without third-party complexity
Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Aircall at <$5K/year, flat, regardless of team size.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No native SCIM support - requires third-party Aquera connector
- SAML SSO only available to select customers via account manager request
- IDP-initiated SAML sign-in not supported
- 25-user minimum for Custom (enterprise) plan
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
No native SCIM. Aquera connector provides create, update, deactivate, delete users. SOC 2 Type II audited service. Aircall planning native Okta OIN integration.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Aircall
Aircall doesn't offer SCIM. Get an enterprise-grade SCIM endpoint in your IdP, even without native support.
See how it works