Customer Service Management

BC-430 Level 1 Cross-Industry 166 providers 406 API surfaces 53 rated strong or better

Inquiries, complaints, support, contact-centre operations.

Customer Service Management (BC-430) is a level-1 business capability in the Cross-Industry model. The catalog holds 406 API surface(s) from 166 provider(s) that can perform some part of it, 53 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Customer Inquiry Management BC-430.10

Inbound contacts, routing, resolution.

80 providers, 119 API surfaces

Complaints & Issue Management BC-430.20

Complaint capture, root cause, resolution.

7 providers, 9 API surfaces

Contact Centre Operations Management BC-430.30

Contact centre running, workforce management, telephony.

33 providers, 94 API surfaces

Self-Service Management BC-430.40

FAQ, knowledge base, chatbots, self-service portals.

20 providers, 34 API surfaces

Customer Feedback Management BC-430.50

Surveys, NPS, voice-of-customer programmes.

64 providers, 121 API surfaces

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 17 Complete, well-documented, and agent-ready
Strong 36 Solid coverage with minor gaps
Developing 70 Usable, with meaningful gaps to close
KlausPublicExportApi1 API53.9Back MarketCare1 API53.7QminderTickets1 API53.7VersapayCollaboration1 API53.5HiverConversations1 API53.4AvitoRatings1 API53.0BrainfishAgentsUsers2 APIs52.7AvayaAgent LocationAgentsEngagementsQueue10 APIs52.5Bright PatternCalling ListCampaignsListsMultichannel Call Recordings6 APIs52.2ev.energySupport Tickets1 API52.2LocalClarityEndpoints1 API51.8IntercomArticlesConversations2 APIs51.7LambdaSupport Tickets1 API51.7CoveoCase Assist1 API51.2PostHogconversationssurveys2 APIs51.0TrustpilotConversationsInvitationsReview ManagementReviews4 APIs51.0AuthenticxConversationsInteractions2 APIs50.7Netomizen-desk-chat-rest-controller1 API50.0AndroidReviews1 API49.9Agile CRMHelpDesk1 API49.7QualtricsDistributions1 API49.4FrontCallsConversationsInboxesKnowledge Base Articles7 APIs49.3EmotiveTickets1 API49.01NCEService Requests1 API48.9TidioLyroTickets2 APIs48.6PodiumConversationFeedbackReviewReview Invite4 APIs48.2Luma HealthchatActivitiesfeedbackResponsesfeedbackResponsesPromoterHistorieslumabotFlows4 APIs47.9PowerReviewsB2B Write a ReviewReviews2 APIs47.5VelarisSurveysTicketing2 APIs47.4Docupilotuser_satisfaction_survey1 API47.1GleapEngagement SurveyHelp centerHelp center articlesHelp center collections5 APIs46.9Help ScoutConversationsThreads2 APIs46.9DixaAgentsChatbotsConversationsKnowledge8 APIs46.5MissiveConversations1 API46.5NextivaCall ManagementConversationsDTMFEmail6 APIs46.4MacrometaSupport1 API45.9NfonCustomer IVRCustomer Queues2 APIs45.8CloudKitchensreviews_endpoints1 API45.6BirdFAQ1 API45.5Oracle Fusion Cloud ApplicationsService Requests1 API45.0RevinateHotelsReviews2 APIs45.0SurvicateRespondentsResponsesSurveys3 APIs45.0SugerSupport1 API44.6YextReviews1 API44.2ZayoTicketing1 API43.9SiteJabberProduct Review RequestsProduct ReviewsResolution AttemptsReview Requests5 APIs43.8WishTickets1 API43.8GuestReadyConversationsreviews2 APIs43.4LangChainnps1 API43.4Outdoorsyreviews1 API43.4Respond.ioConversationsMessages2 APIs43.3Root InsuranceComplaints1 API43.2HappyOrNotalert-commentsbutton-feedbacksdemographicsfollow-up-feedbacks9 APIs43.1ChatwootCSAT Survey PageCanned ResponsesClient ConversationsClient Messages13 APIs43.0ForethoughtConversationsPredictions2 APIs42.7HoliduReviews1 API42.6Cisco Voice PortalCall Detail RecordsCall Management2 APIs42.3PypestreamConversations APIEndpoints2 APIs42.1CRM BonusNps1 API42.0Incentiviosurvey-answer-controller1 API41.9FreshworksAgentsCall MetricsCallsConversations6 APIs41.8WootricDeclinesEmail SurveysMetricsResponses5 APIs41.5AvocaCalls1 API41.2WellnessLivingReviews1 API41.0Product FruitsKnowledge Base1 API40.6Radar CNPJContato1 API40.6Packet HostSupportRequest1 API40.5Stella Connect (Medallia Agent Connect)DataRecoveriesRequests3 APIs39.9PylonIssuesKnowledge Base2 APIs39.8WHMCSSupport1 API39.6
Thin 41 Limited public surface area
Emerging 2 Early or largely undocumented

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Customer Service Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →