Customer Service Management
BC-430
Level 1
Cross-Industry
50 providers
168 API surfaces
22 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 168 API surface(s) from 50 provider(s) that can perform some part of it, 22 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.
29 providers,
62 API surfaces
Complaints & Issue Management BC-430.20
Complaint capture, root cause, resolution.
1 provider,
1 API surface
Contact Centre Operations Management BC-430.30
Contact centre running, workforce management, telephony.
17 providers,
49 API surfaces
Self-Service Management BC-430.40
FAQ, knowledge base, chatbots, self-service portals.
9 providers,
21 API surfaces
Customer Feedback Management BC-430.50
Surveys, NPS, voice-of-customer programmes.
17 providers,
24 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.
-
Brevo
Messagesconversations
exemplar
87.0
-
HubSpot
InboxesMessagesTickets
exemplar
83.0
-
Twilio
Workspaces
exemplar
73.8
-
Lucidya Ltd
CSAT AnalyticsReference Data
exemplar
68.2
-
8x8
Agent ActivityAgent statusAgentsCall Queue MetricsConversationsMessagesPhone callsQueue Agent ActivityQueuesinteractions-insighttranscript-summaries
exemplar
67.7
-
KPN
Cases
strong
65.9
-
Benchmark Email
SurveySurvey Creation
strong
65.8
-
DoiT
Support Requests
strong
64.5
-
Vendasta
Business Location ReviewsNetPromoterScoreServiceReview RequestsTemplates
strong
64.2
-
Salesforce Service Cloud APIs
bot
strong
63.7
-
Dotdigital
ApiSurvey
strong
62.9
-
Oracle Siebel
Service Requests
strong
62.9
-
Rhombus Systems
Help Webservice
strong
62.1
-
Amigo
Operators
strong
62.0
-
Lithium
Agent States Api V2DiscussionEmailPriorityResolveUuid
strong
59.3
-
Microsoft Azure
Communications
strong
58.8
-
RingCentral
Call Queues
strong
58.2
-
Zendesk
BasicsConversation LogCustom Ticket StatusesMacrosOmnichannel Routing QueuesRequestsSatisfaction RatingsSatisfaction ReasonsSkill Based RoutingSuspended TicketsTicket CommentsTickets
strong
58.1
-
Genesys
Case ManagementConversationsKnowledgeRoutingTextbotsWebChatWorkforce Management
strong
56.0
-
Platform.sh
SupportTickets
strong
56.0
-
Emotive
Tickets
strong
54.5
-
Upsun
SupportTickets
strong
54.3
-
MTN Group
trouble-ticket-aggregator-controller
developing
54.0
-
Kaseya
SurveyResultsSurveys
developing
53.2
-
VoPay
Support Endpoints
developing
52.1
-
Nfon
Customer IVRCustomer Queues
developing
51.6
-
PostHog
conversationssurveys
developing
51.4
-
Zoho
AgentPresenceArticleArticleFeedbackArticleTranslationCallCommunityCommunityCategoryCommunityCommentCommunityTopicDashboardMetricsHelpcenterNewTicketHistory
developing
51.3
-
Webex
AgentsAuto CSATCall MonitoringCampaign ManagerContact Service QueueEntry PointEstimated Wait TimeFeatures: Customer AssistFlowsMultimedia ProfileTasks
developing
51.0
-
Salesforce Service Cloud
AvailabilityCasesMessagesSessions
developing
50.9
-
Facilio
Service Requests
developing
49.3
-
Luma Health
chatActivitiesfeedbackResponsesfeedbackResponsesPromoterHistorieslumabotFlows
developing
49.0
-
Docupilot
user_satisfaction_survey
developing
47.4
-
Oracle Fusion Cloud Applications
Service Requests
developing
47.2
-
Coveo
Case Assist
developing
46.3
-
Wispr AI
Support
developing
45.0
-
Packet Host
SupportRequest
developing
43.5
-
Gleap
Engagement SurveyHelp centerHelp center articlesHelp center collectionsTicket
developing
43.1
-
Chatwoot
CSAT Survey PageCanned ResponsesClient ConversationsClient MessagesConversationConversation AssignmentsConversationsConversations APIHelp CenterInboxesMessagesMessages API
developing
41.1
-
GuestReady
Conversationsreviews
developing
40.8
-
Incentivio
survey-answer-controller
developing
39.7
-
Front
CallsConversationsInboxesKnowledge Base ArticlesKnowledge Base CategoriesKnowledge BasesMessages
developing
39.6
-
LangChain
nps
thin
38.4
-
Saxo Bank
Support - Cases
thin
35.9
-
Bitrix24
Telephony
thin
34.4
-
freshworks
AgentsCall MetricsCallsConversationsSurveysTickets
thin
32.5
-
LangSmith
nps
thin
31.0
-
HYPERLABS
ContactMessages
thin
29.0
-
WinCL
Admin FAQAdmin QnAFAQQnA
emerging
25.6
-
Amazon Web Services
ContactContact Flow ModulesContact FlowsContactsQueuesQueues SummaryQuick ConnectsRouting ProfilesSearch Routing Profiles
emerging
16.7
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 →