@absolutejs/voice 0.0.22-beta.242 → 0.0.22-beta.244

package/README.md

@@ -68,7 +68,7 @@ Use this checklist when a buyer asks, "How do I know this replaces a hosted voic
 | Can I prove provider fallback and latency? | provider contract matrix, provider status UI, `/turn-latency`, `/live-latency` | Provider choice, fallback behavior, server turn timing, browser p50/p95 timing |
 | Can operators intervene safely? | live-ops routes, action center, ops action audit routes, operations record | Pause/resume/takeover, injected instructions, operator action audit trail |
 | Can I run outbound campaigns? | `/voice/campaigns`, `/voice/campaigns/observability`, `/api/voice/campaigns/readiness-proof` | Recipient import evidence, consent/dedupe checks, scheduling policy, worker-safe attempts |
-| Can I handle post-call workflow? | reviews, tasks, integration events, outcome contracts, operations record | Summary/review artifacts, task creation, webhook/sink delivery, matched session proof |
+| Can I handle post-call workflow? | `createVoicePostCallAnalysisRoutes(...)`, reviews, tasks, integration events, outcome contracts, operations record | Extracted-field proof, task creation, webhook/sink delivery, matched session proof |
 | Can I keep data in my infrastructure? | `/data-control`, `/data-control/audit.md`, retention dry-run/apply routes | Customer-owned storage, redaction, audit export, guarded deletion, zero-retention planning |
 | Can I prove release readiness? | `/production-readiness`, `/ops-recovery`, delivery runtime, readiness profiles | Deploy gates for session health, audits, delivery queues, provider/campaign/phone proof |
 
@@ -82,6 +82,37 @@ For a demo, the fastest convincing path is:
 
 If those five surfaces are green and linked, the buyer can see the core difference from Vapi-style hosted orchestration: the operational proof lives inside the app, not in a vendor dashboard.
 
+## Post-Call Analysis Proof
+
+Use `createVoicePostCallAnalysisRoutes(...)` when the hosted-platform feature you need is call analysis plus follow-up proof. It validates that required extracted fields exist, expected ops tasks were created, integration/webhook events delivered, and the report links back to `/voice-operations/:sessionId`.
+
+```ts
+import { createVoicePostCallAnalysisRoutes } from '@absolutejs/voice';
+
+app.use(
+	createVoicePostCallAnalysisRoutes({
+		path: '/api/voice/post-call-analysis',
+		operationRecordBasePath: '/voice-operations/:sessionId',
+		reviews: runtime.reviews,
+		tasks: runtime.tasks,
+		integrationEvents: runtime.events,
+		source: ({ reviewId, sessionId }) => ({
+			reviewId,
+			sessionId,
+			// Use your own extractor output here, for example fields persisted from an LLM/tool result.
+			extractedFields: loadExtractedPostCallFields(reviewId ?? sessionId)
+		}),
+		fields: [
+			{ path: 'review.postCall.target', label: 'customer target' },
+			{ path: 'customerId' },
+			{ path: 'category' }
+		],
+		requiredTaskKinds: ['support-triage'],
+		requireDeliveredIntegrationEvent: true
+	})
+);
+```
+
 ## Use-Case Recipe: Support Triage
 
 Use this path when you want a Vapi-style support assistant that can answer web or phone calls, look up customer context, route billing issues to a specialist, create follow-up work, and leave one debuggable call record. It is a recipe over primitives, not a support app kit.

package/dist/angular/index.d.ts

@@ -1,5 +1,6 @@
 export { VoiceOpsStatusService } from './voice-ops-status.service';
 export { VoicePlatformCoverageService } from './voice-platform-coverage.service';
+export { VoiceProofTrendsService } from './voice-proof-trends.service';
 export { VoiceOpsActionCenterService } from './voice-ops-action-center.service';
 export { VoiceLiveOpsService } from './voice-live-ops.service';
 export { VoiceDeliveryRuntimeService } from './voice-delivery-runtime.service';