In-house Telecommunications United States Company newsroom

AT&T

Customer Service Automation · IT Operations Automation

AT&T needed a way for teams to automate time-consuming customer service and network-operations tasks across multiple internal systems while keeping humans in control and maintaining privacy, security, and faster response for customers.

Reported impact

Business outcome

AT&T reports that the first production workflow is delivering value at scale by improving customer experience, reducing wait times, helping employees focus on higher-priority work, and enabling faster response to network incidents.

  • Customer Experience
  • Productivity Improvement

Solution

AT&T uses Ask AT&T Workflows, an internal extension of its Ask AT&T platform, to let employees design multi-agent workflows through a graphical drag-and-drop builder instead of coding each automation from scratch. In the first production deployment, AT&T Business and technology development teams configured agents to accept customer service update requests, synchronize data across internal systems, and auto-install information in real time, with humans overseeing required checkpoints. For retrieval and context, the agents pull enterprise information from Ask Docs and Ask Data, AT&T’s proprietary GenAI tools that securely house company knowledge and data. The same pattern is applied to network operations: agents ingest alerts and telemetry, correlate issue location, retrieve recent change logs and known-issue records, open trouble tickets, propose remediations, and assemble resolution artifacts for engineer review. Logging, data isolation, retention policies, and role-based access govern each handoff between agents.

Data flow

Employee-built agents created in Ask AT&T Workflows ingest customer service requests or network alerts, pull enterprise context from Ask Docs and Ask Data plus telemetry, change logs, and known-issue records, then coordinate actions such as synchronizing records, auto-installing information, opening trouble tickets, proposing fixes, and compiling summaries for human review.

Solution architecture

3 components · 2 layers
  1. Storage
    • Ask Docs Supplies securely housed AT&T information that agents retrieve to inform decisions and actions.
    • Ask Data Supplies securely housed AT&T data that agents query during workflow execution for informed actions.
  2. Orchestration
    • Ask AT&T Workflows Provides the graphical builder and orchestration layer employees use to create and run multi-agent workflows for customer service and network operations.

Architecture clues

  • A human oversees the chain of agents and required checkpoints throughout execution.
  • Agents operate within AT&T's ecosystem and can hand work from one agent to the next.
  • Data isolation, retention policies, and role-based access are enforced across agent handoffs.
  • Every action taken by the agents is logged.
  • Network-operations agents can correlate telemetry, inspect change logs and known issues, open tickets, draft code patches, and compile post-incident artifacts.

Evidence from the source

"AI agents can take customer service update requests, synchronize data across systems, and auto-install information in real time."
"An agent can correlate telemetry to identify the location of the alert’s issue, pull recent change logs, check for known issues, and open a trouble ticket."
"Ask AT&T Workflows gives teams a graphical drag-and-drop agent builder."
"Every action the agents take is logged, and when one agent passes off a workload to the next, data isolation, retention policies and role-based access are enforced."
"The first in-production tool built with Ask AT&T Workflows is already proving its value at scale."
"These agents work within AT&T’s ecosystem, able to pull information and data from Ask Docs and Ask Data, our proprietary GenAI tools that securely house AT&T information, to give uniquely informed insights and actions."
Transparency Evidence & methodology 75/100 reference value · 95% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AT&T

    AT&T customer story

    First-party
    https://about.att.com/blogs/2025/agentic-ai.html
    Source type
    Customer-published story
    Published
    Nov 13, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. Built In

    AT&T Careers, Perks + Culture | Built In

    Independent secondary
    https://builtin.com/company/att

    The Organization JSON-LD lists streetAddress '208 South Akard Street', addressLocality 'Dallas', addressRegion 'TX', and addressCountry 'US'.

    Source type
    Structured company profile
    Supports
    • Region

Date evidence

Not separately sourced Industry, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.