Complaint routing API
Ship smarter support routing through one REST API
Drop ServiceFlow in front of your mobile app, SaaS, or legacy form. We classify text with TF‑IDF similarity, score confidence, and assign to the right department or agent — tenant-isolated and API-first.
- Tenant-scoped data
- Bearer API keys
- ML-assisted assignment
your-backend → ServiceFlow
$ curl -X POST https://serviceflow-lodx.onrender.com/api/complaints/create \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"title":"Refund stuck","customerName":"Ada","customerEmail":"ada@example.com"}'→ 201 profile_id · confidence · assignment
Built for teams who sell an API, not a inbox
Your customers stay in your UI; ServiceFlow is the routing brain behind POST /api/complaints/create.
REST-first
Cookie-auth dashboard for operators; Bearer keys for every integration. Same tenant, strict isolation.
Two routing modes
Department queues or direct agent vectors — controlled per tenant to match how your org works.
Similarity routing
Keywords become embeddings; complaints match the best profile with confidence you can monitor.
Go live in three steps
01
Model your teams
Define departments and agents with keyword profiles in the console — those seed the classifier.
02
Issue API keys
Rotate Bearer keys per environment. Tune routing strategy under workspace settings.
03
POST complaints
Your apps send JSON; we return assignment metadata and confidence so you can audit flows.