# Circles powers telco personalization with OpenAI technology

Source: [OpenAI](https://openai.com/index/circles)  
Feed7 permalink: https://feed7.dev/p/circles-0qu2vnm  
Published: 2026-08-03T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Circles reports measurable telco gains from combining the OpenAI API with Codex, but the supplied case-study material gives no baseline, methodology, or detail on the developer-efficiency claim.

## Source Summary

Circles uses the **OpenAI API** and **Codex** for telco personalization. It reports **22% higher ARPU** and **9% lower churn**, plus an unspecified improvement in development efficiency.

## Practical Implication

For builders, the useful pattern is pairing customer-facing model calls with a coding agent for delivery work, then evaluating the product and engineering outcomes separately.

## Agent-Ready Context

Circles uses the **OpenAI API** and **Codex** for telco personalization. It reports **22% higher ARPU** and **9% lower churn**, plus an unspecified improvement in development efficiency.

For builders, the useful pattern is pairing customer-facing model calls with a coding agent for delivery work, then evaluating the product and engineering outcomes separately.

The material provides no baseline, measurement period, sample size, implementation detail, or quantified development-efficiency result, so the figures are directional case-study evidence rather than a reusable playbook.

## Connected Context

Feed7 judgment across 340 accumulated Signals:

This extends the enterprise-adoption evidence from internal productivity into customer-facing telco economics, while making the split between product and engineering evaluation explicit. Unlike prior cases with vague gains or one operational metric, Circles supplies ARPU and churn figures but leaves its development benefit unquantified; absent baselines and measurement details, it supports separate outcome tracking rather than a transferable implementation claim.

- [Australian Payments Plus moves faster with ChatGPT and Codex](https://feed7.dev/p/australian-payments-plus-18s6gt2) — Both pair OpenAI products with Codex in enterprise delivery, but Circles adds quantified customer outcomes while still leaving engineering gains unspecified.
- [NTT DATA Group cuts incident analysis to 30 minutes with Codex](https://feed7.dev/p/ntt-data-1sgidqg) — NTT DATA quantifies an internal operational improvement, whereas Circles quantifies product-level commercial outcomes; together they illustrate why engineering and business effects should be measured separately.
- [Forward Deployed Engineering at Cursor — Pauline Brunet](https://feed7.dev/p/forward-deployed-engineering-at-cursor-pauline-brunet-1wkd3r1) — Cursor’s playbook supplies the missing implementation discipline: choose measurable use cases and retain customer ownership before treating outcome figures as evidence of a repeatable deployment model.

## Context Map

- Layer: industry
- Domains: coding
- Topics: adoption, enterprise

## Uncertainty

- The material provides no baseline, measurement period, sample size, implementation detail, or quantified development-efficiency result, so the figures are directional case-study evidence rather than a reusable playbook.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.