COS-RTE-001
RM Brief Review & Design Routing
Purpose
After a Job is created by intake, the assigned RM reviews the AI-parsed brief, corrects any errors, confirms design category, and routes to the correct design queue. This is the human checkpoint between intake and design work beginning.
Actors
| Actor | Type | Role |
|---|---|---|
| RM (Rupsa / Rumi / Trishna) | Internal | Reviews brief, routes to design team |
| AI Routing Engine | System | Recommends which design queue and why |
Trigger
Job in state BRIEF_CONFIRMED or INTAKE_PARSED appears in RM queue.
Flow
Full Flow
1. RM opens job from queue
2. Sees: original message, reference images, AI-parsed brief (editable),
AI routing recommendation, customer history panel
3. RM confirms or edits brief fields
4. RM selects design queue (AI pre-selects, RM can override)
→ Queue load shown: "CAD HipHop — 4 jobs, ~18h wait"
5. RM taps "Route to Design"
6. System:
→ Sets state = COREL_QUEUED | CAD_QUEUED | PRICING_QUEUED
→ Notifies design queue head
→ Starts SLA timer for design stage
→ Creates job_event { event_type: "job.routed" }
7. Job leaves RM action queue → moves to monitoring view
Routing Logic
AI Routing Recommendation Logic
Hip Hop pendant, no prior CAD exists
→ Recommend: corel.hiphop
→ Reason: "Hip Hop pendants approved on Coral 80% of the time."
Bridal category
→ Recommend: cad.bridal
→ Reason: "Bridal always requires CAD for production accuracy."
Repeat order (parent_style_id exists)
→ Recommend: skip design queues entirely
→ Reason: "Design exists as CJ-YYYY-XXXXXX. Route to pricing."
Cuban / Chain
→ Recommend: cad.cuban
→ Reason: "Chain designs require specialist CAD skill."
Note: RM always has final say. AI recommendation is advisory only.
History Panel
Customer History Panel
Customer: Icechamp
─────────────────────────────────────────
Last 10 orders: [thumbnails + IDs]
Preferred metal: 14kt White Gold (9/10 orders)
Preferred setting: Bussdown, VVS
Avg budget: $8,000–$15,000
Recurring note: "Always polished inside band.
Prong tips must be rounded."
Pending approvals: 2 awaiting client response
Open in production: 3 jobs
─────────────────────────────────────────
Business Rules
| Rule | Detail |
|---|---|
| Routing SLA | RM must route within 2h of job creation. Yellow at 2h, escalate to Aayushi at 4h. |
| Required fields before routing | category, metal, karat, budget OR weight estimate — all must be filled |
| Bridal → Coral blocked | System prevents routing Bridal to Coral queue |
| Repeat confirmation | If AI flagged possible repeat, RM must confirm before routing |
| Queue load visible | RM sees estimated wait time per queue |
Data
Data Created / Modified
job {
current_state: "COREL_QUEUED" | "CAD_QUEUED" | "PRICING_QUEUED",
current_queue: "corel.hiphop" | "cad.bridal" | ...,
brief_structured: RM-confirmed version,
current_owner_id: design queue head,
sla_targets: { design: "24h" | "48h" }
}
job_event {
event_type: "job.routed",
actor_id: rm_user_id,
payload: { queue, notes, routed_at }
}
API
API Endpoints
GET /jobs?queue=rm&state=brief_confirmed&rm_id=:id
GET /queues/:queue_name/load
GET /clients/:client_id/history
PATCH /jobs/:job_id/route
Body: { queue, brief_confirmed, notes, override_reason? }
Out of Scope
| Item | Handled in |
|---|---|
| Design work | COS-DSN-001 |
| Pricing | COS-PRC-001 |
| Repeat order path | COS-ORD-001 |