.png)
Automate Kustomer access provisioning from Rippling so support teams get customer service platform access on day one and lose it immediately at offboarding.
The Rippling–Kustomer integration manages user lifecycle in Kustomer's customer service CRM platform based on Rippling employment data. Support agents and CX team members are provisioned into Kustomer with the appropriate role and queue assignments on hire, and deprovisioned automatically when they leave.
Kustomer is used by high-volume customer service operations for omnichannel support management. Connecting it to Rippling ensures agent access is driven by the same source of truth as every other application, and that customer conversation history is protected from access by former employees.
Support operations using Kustomer frequently experience a lag between employee termination and Kustomer access removal, during which former agents retain access to active customer conversations and contact records. Automating deprovisioning from Rippling eliminates this window.
thePeopleStack configures SAML SSO and provisioning rules between Rippling and Kustomer, mapping support team roles to Kustomer agent tiers and queue assignments. We test the deprovisioning trigger before go-live.
Kustomer integrations for thePeopleStack's Rippling clients are structured around US support team provisioning workflows.
Canadian and cross-border operations: for Canadian support agents, Kustomer provisioning follows the same Rippling-driven lifecycle as US team members.
Kustomer is a customer service CRM platform (Meta-owned) used by high-volume support operations for omnichannel ticket management, automation, and customer timeline views across email, chat, voice, and social channels.
Yes. Kustomer supports SAML SSO, and Rippling can serve as the identity provider to tie support platform access to active employment status.
Yes. Rippling's department and job title fields map to Kustomer agent roles and team assignments, ensuring new support hires are placed in the correct queue with appropriate permissions automatically.
When a support team member is terminated in Rippling, their Kustomer access is revoked and they are removed from active queues, preventing routing of customer conversations to inactive agents.
Standard SSO and provisioning setup takes 2–3 hours including queue and role mapping.
