Topic starter
08/06/2026 4:49 pm
TL;DR: C1.ai says identity support works best when it is embedded in the same channels customers already use, with Slack, Pylon, direct access, and visible feature-request tracking keeping issues moving quickly. The governance lesson is that identity operations break down when support, documentation, and product feedback are treated as separate workstreams.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “Inside C1's Customer-First Support Model”.
Key questions
Q: How should identity teams handle support requests that affect access workflows?
A: Treat them as governed operational issues, not informal help-desk noise.
Q: Why does response time matter in identity support operations?
A: Because delays in identity support often become delays in provisioning, policy clarification, or issue recovery.
Q: What do security teams get wrong about feature-request tracking in IAM?
A: They often treat it as product feedback only.
Practitioner guidance
- Embed support in identity operations Use collaboration channels, ticketing, and escalation paths as part of the operating model so access issues do not sit outside governance.
- Track feature requests as governed demand Record every recurring identity request with product area, frequency, owner, and status so operational pain turns into visible backlog.
- Measure support as a service control Review first-response time, resolution time, and ticket back-and-forth alongside access performance and adoption metrics.
Bottom line: Identity support is part of how access and workflow problems are governed, not just how customers are helped.
What's in the full article
C1.ai's full blog post covers the operational detail this post intentionally leaves for the source:
- The exact support workflow from Slack message to Pylon ticket creation.
- How feature requests are logged, categorised, and prioritised over time.
- Examples of the customer check-ins and troubleshooting touchpoints the article describes.
- The operational metrics C1.ai says it tracks to manage response and resolution quality.
👉 Read C1.ai's post on customer-first identity support and operations →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
08/06/2026 6:39 pm
Identity support is part of the control plane, not a post-sale service layer. When customers route access questions, bugs, and workflow blockers through the same operating channel that handles issue resolution, support becomes part of how identity is governed in practice. That changes the meaning of service quality in IAM: speed, traceability, and direct escalation become operational controls. Practitioners should treat support design as part of identity programme maturity, not a separate vendor experience metric.
A question worth separating out:
Q: How do teams know whether identity support is actually working?
A: Look for short response times, consistent ticket ownership, low back-and-forth, and a visible record of recurring issues being turned into improvements. If users keep reopening the same problems or bypassing the support path, the model is failing even if individual tickets are closed.
👉 Read our full editorial: ConductorOne’s customer-first support model and identity operations
This post was modified 4 days ago by NHI Mgmt Group