Decision owner
Agent within policy authority
The named role remains accountable for the consequential decision.
Telecommunications
Designed for Contact-center agent
Let a contact-centre agent resolve a subscriber's billing, device, or coverage issue on the first call by grounding answers in the live account, plan terms, device guides, and known outages, with agent confirmation before any account change.
Contract TEL-02 · primary aggregate SubscriberContact · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Agent within policy authority
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
A subscriber disputes a 46 dollar increase after upgrading mid-cycle; the assist isolates two proration lines and one add-on trial conversion, confirms no outage is involved, drafts a plain-language explanation, and the agent applies a 19 dollar goodwill credit that sits inside their policy authority limit..
Let a contact-centre agent resolve a subscriber's billing, device, or coverage issue on the first call by grounding answers in the live account, plan terms, device guides, and known outages, with agent confirmation before any account change.
Applied credit or plan change with audit record gives Agent within policy authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Agent within policy authority verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Contact-centre agent performs verify the subscriber and load the account using Caller identity and account lookup and produces Verified SubscriberContact with account snapshot. The transition is deterministic and does not require autonomous model approval.
Why it matters: Verified SubscriberContact with account snapshot gives Real-time transcription agent the evidence needed to begin Detect intent and sentiment live, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/verify-the-subscriber-and-load-the-account
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Real-time transcription agent performs detect intent and sentiment live using Call or chat transcript and produces Ranked intents and sentiment trend. The transition is deterministic and does not require autonomous model approval.
Why it matters: Ranked intents and sentiment trend gives Service context agent the evidence needed to begin Check outages and device compatibility, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/detect-intent-and-sentiment-live
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Service context agent performs check outages and device compatibility using Subscriber location and device model and produces Known outage or device-specific cause. The transition is deterministic and does not require autonomous model approval.
Why it matters: Known outage or device-specific cause gives Agent assist copilot the evidence needed to begin Assemble the grounded resolution, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/check-outages-and-device-compatibility
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Agent assist copilot performs assemble the grounded resolution using Charge detail, guides, and policy limits and produces Cited explanation with ranked resolution offers. The transition is deterministic and does not require autonomous model approval.
Why it matters: Cited explanation with ranked resolution offers gives Agent within policy authority the evidence needed to begin Apply the account change or credit, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/assemble-the-grounded-resolution
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Agent within policy authority performs apply the account change or credit using Selected ResolutionOffer and produces Applied credit or plan change with audit record. A named human approver must review the evidence before the transition completes.
Why it matters: Applied credit or plan change with audit record gives Agent within policy authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/apply-the-account-change-or-credit
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved SubscriberContact evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
subscriberContacts/tenantId + /subscriberAccountIdA subscriber disputes a 46 dollar increase after upgrading mid-cycle; the assist isolates two proration lines and one add-on trial conversion, confirms no outage is involved, drafts a plain-language explanation, and the agent applies a 19 dollar goodwill credit that sits inside their policy authority limit.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
subscriberContacts |
Primary | /tenantId + /subscriberAccountId |
SubscriberContact, AccountSnapshot, BillingChargeDetail, ResolutionOffer |
deviceKnowledgeLibrary |
Reference | /tenantId + /deviceModelId |
DeviceSupportGuide |
networkOutageRegistry |
Reference | /tenantId + /serviceCellSiteId |
NetworkOutageNotice |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
SubscriberContact |
subscriberContacts |
/tenantId + /subscriberAccountId |
contact::{subscriberAccountId}::{contactId} |
None |
AccountSnapshot |
subscriberContacts |
/tenantId + /subscriberAccountId |
account::{subscriberAccountId} |
None |
BillingChargeDetail |
subscriberContacts |
/tenantId + /subscriberAccountId |
charge::{subscriberAccountId}::{invoiceId}::{chargeId} |
None |
DeviceSupportGuide |
deviceKnowledgeLibrary |
/tenantId + /deviceModelId |
deviceguide::{deviceModelId}::{chunkIndex} |
bodyVector |
NetworkOutageNotice |
networkOutageRegistry |
/tenantId + /serviceCellSiteId |
outage::{serviceCellSiteId}::{outageId} |
None |
ResolutionOffer |
subscriberContacts |
/tenantId + /subscriberAccountId |
offer::{subscriberAccountId}::{offerId} |
None |
Read the account snapshot, recent charges, and open offers in one partition query.
subscriberContacts
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.subscriberAccountId = @subscriberAccountId AND c.type IN ('AccountSnapshot','BillingChargeDetail','ResolutionOffer') ORDER BY c.servicePeriod DESC
Pinpoint the charges on the disputed invoice that changed versus the prior cycle.
subscriberContacts
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.subscriberAccountId = @subscriberAccountId AND c.type = 'BillingChargeDetail' AND c.invoiceId = @invoiceId AND c.chargeCategory IN ('proration','overage','oneTime') ORDER BY c.amount DESC
Knowledge-container query against networkOutageRegistry (partition-aligned to /tenantId + /serviceCellSiteId): confirm whether a known network issue explains the reported symptom; the registry fans an outage out to one document per affected cell site so the subscriber lookup is a single partition read.
networkOutageRegistry
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.serviceCellSiteId = @serviceCellSite AND c.type = 'NetworkOutageNotice' AND c.outageStatus = 'active' ORDER BY c.estimatedRestorationUtc ASC
Knowledge-container query against deviceKnowledgeLibrary (partition-aligned to /tenantId + /deviceModelId): return troubleshooting steps valid for the subscriber's device model and OS version, read as a single partition query on the device model.
deviceKnowledgeLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.deviceModelId = @deviceModelId AND c.type = 'DeviceSupportGuide' AND ARRAY_CONTAINS(c.symptomTags, @symptomTag) ORDER BY c.revisionLabel DESC