Microsoft ArchitectureHow My Rogers Works

Customer drops in a competitor bill

A phone photo or the PDF from TELUS's portal. The Foundry Agent Service owns the conversational front door and routes the file to the comparison flow.

Document Intelligence + multimodal model read the bill

Layout-aware OCR extracts line items; a multimodal model in Azure AI Foundry normalizes them into provider, monthly total, internet speed, TV, mobile lines and equipment fees with confidence scores.

PII is minimized before anything is stored

Account numbers and addresses are redacted by Purview-governed policies; only the pricing shape of the bill continues downstream.

Comparison Agent maps competitor services to Rogers equivalents

Fabric holds the governed product catalog and current promotional pricing, so 300 Mbps + 2 lines + TV resolves to a concrete Rogers bundle, not a guess.

Serviceability and real price checked through existing APIs

An OSS call confirms what can actually be delivered at the address; a BSS pricing call returns taxes, fees and promo duration — so the quoted savings survive contact with billing.

Assistant narrates the delta honestly

Month 1–12 vs month 13+, what's included, what changes. Where Rogers isn't cheaper, the agent says so — grounded answers only, no invented pricing.

Customer accepts; order and lead are written back

Confirmation-gated order to provisioning, opportunity and transcript to CRM, outcome synced to Fabric for conversion analytics.