SMS Orchestrator — AI Integration

Status: populated Owner: Platform Engineering Last updated: 2026-04-18

1. Current usage

None. The orchestrator performs no AI calls in its current scope. SMS pipeline decisions (routing, validation, retry) are deterministic.

2. Forward-looking (not in scope of current release)

Potential future AI uses — all would require a dedicated ai-gateway adapter and an ADR:

Candidate	Purpose
Spam / abuse classification	Pre-send content scoring; high-risk content rejected or queued for review
Intent classification for replies	If inbound MO SMS is added later, classify customer replies
Sender ID similarity check	Detect impersonation attempts

If introduced, AI calls must go through a future ai-gateway-service per platform rules (no direct vendor SDK imports from this service).

3. Provenance

Any persisted AI-derived field would require an AIProvenance VO stored on the SmsMessage aggregate:

interface AIProvenance {
  purpose: string;
  model: string;
  version: string;
  promptHash: string;
  decisionId: string;
  at: string;
}

Not present today.