Skip to main content

Overview

OPIC 1.0 is the first production release of the Operations Intent Classifier. This model provides accurate multi-class intent classification specifically tuned for ecommerce customer support scenarios.

What’s New in 1.0

  • 10 Intent Classes: Comprehensive coverage of common ecommerce support intents
  • Sub-60ms Latency: Optimized for real-time inference
  • Batch Processing: Support for classifying multiple messages in a single request
  • Confidence Thresholds: Configurable filtering of low-confidence predictions

Model Specifications

PropertyValue
Model Version1.0.0
ArchitectureFine-tuned BERT-based transformer
Training DataEcommerce customer support conversations
Intent Classes10
Max Input Length2,048 characters
LanguagesEnglish
Average Latency< 60ms (p95)

Supported Intents

IntentDescription
track_orderOrder/shipment tracking inquiries
cancel_orderOrder cancellation requests
return_itemProduct return inquiries
refund_requestRefund status or requests
product_inquiryProduct questions
change_addressDelivery address modifications
payment_issuePayment problems
complaintNegative feedback
complimentPositive feedback
otherUnclassified intents

Quick Start

Single Message Classification

curl -X POST 'https://api.usehandled.io/api/v1/ipaas/inference/intent-classify' \
  -H 'Authorization: Bearer YOUR_API_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "message": "Where is my order?",
    "model_version": "1.0.0"
  }'

Response

{
  "request_id": "req_abc123",
  "message": "Where is my order?",
  "predictions": [
    {
      "intent": "track_order",
      "confidence": 0.95
    }
  ],
  "top_intent": "track_order",
  "latency_ms": 42,
  "model_version": "1.0.0"
}

Best Practices

  1. Use confidence thresholds: Set threshold to filter out low-confidence predictions
  2. Request top-k results: Use top_k to get multiple intent predictions for ambiguous messages
  3. Batch when possible: Group multiple messages to reduce API calls

Migration Notes

OPIC 1.0 is the initial release. Future versions will maintain backward compatibility with the 1.x API contract.