Entity

Customer Inquiry

An inbound customer question or request — channel, subject, shipment reference, resolution status, and response time that tracks customer interactions requiring attention.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI chatbots handle routine inquiries while sentiment analysis detects escalation risk; without inquiry records, systems cannot route appropriately or measure service quality.

Customer Service & Order Management Capacity Profile

Typical CMC levels for customer service & order management in Logistics organizations.

Formality
L2
Capture
L2
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Customer Inquiry. Baseline level is highlighted.

L0

Customer inquiries are phone conversations and emails that may or may not get documented. When a customer calls back about the same issue, the CSR has no record of the previous conversation. There's no inquiry tracking system.

None — AI cannot route inquiries, detect patterns, or measure response quality because no inquiry record exists.

Create a basic inquiry log in a spreadsheet or helpdesk system with at least customer name, contact channel, subject, shipment reference (if applicable), and resolution status for every customer contact.

L1

Customer inquiries get logged in a shared email inbox or basic ticketing system. Each inquiry has a subject line and the customer's question. Resolution notes are sometimes added, sometimes not. Response times aren't tracked. Priority is whatever the CSR remembers.

AI could count inquiry volumes by subject keyword, but cannot route intelligently, predict escalations, or measure service quality because inquiry records are incomplete and inconsistent.

Implement a helpdesk system with enforced fields — customer ID, inquiry channel (phone/email/chat/portal), category, shipment reference, priority level, assigned CSR, timestamp, and resolution status — for every inquiry.

L2Current Baseline

All customer inquiries are documented in the helpdesk with complete attributes — customer, channel, category, shipment reference (if applicable), priority, assigned CSR, timestamps for received/first-response/resolved, and resolution notes. Managers can report on inquiry volume by category and response time metrics. But inquiries don't link to broader customer context or trigger proactive alerts.

AI can analyze inquiry patterns and route based on category keywords. Cannot predict escalation risk or personalize responses because inquiries aren't connected to customer sentiment history, account value, or shipment status.

Link each customer inquiry to its full context — customer account profile, related shipment records, previous inquiry history, customer service tier, and current relationship health — so the inquiry carries the full customer situation.

L3

Customer inquiries are comprehensive service records — each inquiry links to the customer account profile, related shipment (with real-time status), inquiry history, service tier commitments, sentiment analysis from the interaction, and escalation triggers. A service manager can query 'show me all premium customers with delay-related inquiries and negative sentiment' and get precise, contextualized results.

AI can perform intelligent inquiry management — routing based on customer value and issue urgency, predicting escalation risk from sentiment and history, automating routine responses, and triggering proactive outreach for at-risk relationships.

Add real-time inquiry intelligence — automated sentiment detection, urgency scoring, similar-issue matching, and recommended resolution paths that update as the inquiry conversation progresses rather than being determined at inquiry creation.

L4

Customer inquiries are dynamic interaction documents updated in real-time — sentiment analysis updates with each message, urgency scores recalculate as deadlines approach, knowledge base articles surface automatically, and resolution paths adapt based on customer responses. Each inquiry is a living service episode with full context and intelligence.

AI can autonomously manage routine inquiries — answering common questions, providing shipment updates, handling simple requests — while routing complex or emotional issues to human CSRs with full context.

Implement fully autonomous inquiry handling where AI chatbots and virtual agents manage the majority of customer inquiries from first contact to resolution without human CSR involvement for routine matters.

L5

Customer inquiries are autonomously managed end-to-end — AI virtual agents handle initial contact, classify urgency and category, access shipment status and customer context, provide personalized responses, resolve routine issues, and escalate complex matters to humans with full briefing. The inquiry record documents the entire service episode from all participants.

Fully autonomous inquiry management for routine matters. AI handles the majority of customer service interactions with human CSRs focused on complex issues and relationship management.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Customer Inquiry

Other Objects in Customer Service & Order Management

Related business objects in the same function area.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.