Customer Service Management › Customer Inquiry Management

Customer Inquiry Management

BC-430.10 Level 2 Cross-Industry 80 providers 119 API surfaces 22 rated strong or better

Inbound contacts, routing, resolution.

Customer Inquiry Management (BC-430.10) is a level-2 business capability under Customer Service Management in the Cross-Industry model. The catalog holds 119 API surface(s) from 80 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

Inquiry Intake and Routing BC-430.10.10

Multi-channel intake, classification, and routing of inquiries.

no catalog coverage

Case Management BC-430.10.20

Case creation, ownership, and resolution tracking.

no catalog coverage

Service Request Fulfilment BC-430.10.30

Fulfilment of standard service requests and account changes.

no catalog coverage

Escalation Management BC-430.10.40

Escalation paths, severity rules, and management of escalated cases.

no catalog coverage

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 8 Complete, well-documented, and agent-ready
HubSpotMessages1 API91.6XquikSupport1 API88.7BrevoMessagesconversations2 APIs81.7OpenMercantilSupport1 API80.6Microsoft AzureCommunications1 API76.2ZendeskConversation LogRequestsSkill Based RoutingSuspended Tickets7 APIs72.2Oracle SiebelService Requests1 API70.4DoiTSupport Requests1 API68.4
Strong 14 Solid coverage with minor gaps
8x8ConversationsMessages2 APIs65.3ZohoNewTicketHistorySkillThreadTicket7 APIs65.1WebexTasks1 API63.8Rhombus SystemsHelp Webservice1 API63.4KPNCasesResults2 APIs61.9Spruce HealthConversations1 API61.2EntergramTickets1 API61.0GenesysConversationsWebChat2 APIs60.3UpsunSupportTickets2 APIs60.1GladlyCommunicationsConversations2 APIs59.4PagesnapSupport1 API58.5Platform.shSupportTickets2 APIs57.9ASAPPGenerativeAgent1 API57.8VoPaySupport Endpoints1 API57.0
Developing 35 Usable, with meaningful gaps to close
QminderTickets1 API53.7HiverConversations1 API53.4AvayaEngagements1 API52.5ev.energySupport Tickets1 API52.2IntercomConversations1 API51.7LambdaSupport Tickets1 API51.7PostHogconversations1 API51.0Netomizen-desk-chat-rest-controller1 API50.0Agile CRMHelpDesk1 API49.7FrontConversationsMessages2 APIs49.3EmotiveTickets1 API49.01NCEService Requests1 API48.9TidioTickets1 API48.6PodiumConversation1 API48.2Luma HealthchatActivities1 API47.9VelarisTicketing1 API47.4Help ScoutConversationsThreads2 APIs46.9DixaChatbotsConversationsMessages3 APIs46.5MissiveConversations1 API46.5NextivaEmail1 API46.4MacrometaSupport1 API45.9Oracle Fusion Cloud ApplicationsService Requests1 API45.0SugerSupport1 API44.6ZayoTicketing1 API43.9WishTickets1 API43.8GuestReadyConversations1 API43.4Respond.ioConversationsMessages2 APIs43.3ChatwootClient ConversationsClient MessagesConversationConversation Assignments8 APIs43.0ForethoughtConversationsPredictions2 APIs42.7PypestreamConversations APIEndpoints2 APIs42.1FreshworksConversationsTickets2 APIs41.8Radar CNPJContato1 API40.6Packet HostSupportRequest1 API40.5PylonIssues1 API39.8WHMCSSupport1 API39.6
Thin 21 Limited public surface area
SleekFlowConversations1 API38.7TrengoMessagesTickets2 APIs38.2PapercupsConversationsMessages2 APIs37.7MealMeSupport Chat1 API37.0TweedTickets1 API36.7SobotUser1 API35.2HospitableMessages1 API35.0Google Business MessagesConversations1 API34.9FreshchatConversationsMessages2 APIs34.7MadeiramadeiraMensageria1 API34.5FreshdeskConversationsTickets2 APIs31.8Saxo BankSupport - Cases1 API31.4WMCases & Tickets1 API31.4KustomerConversations1 API30.7LiveChatChats1 API30.5TelemetronTicket1 API29.5CrispConversations1 API29.0OlarkChat1 API28.8RefurbedTicketService1 API28.5HYPERLABSContactMessages1 API28.3HostBillTickets1 API26.3
Emerging 2 Early or largely undocumented
Zoho DeskTickets1 API24.2WinCLAdmin QnAQnA2 APIs22.0
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 Inquiry 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 →