Back to case studies

Top European telco provider

Building an Always-On Content Engine for AI Search

How a five-phase agentified content lifecycle drives improvements in generative-search visits.

A neon phone surrounded by 5 independant tiles

Building an always-on agentic content engine for search and AI discovery

Keeping digital content current, useful and visible is a persistent challenge for telecommunications providers.

Customer interests change rapidly. New devices enter the market, product offers evolve and seasonal demand creates new questions about topics such as roaming, model releases, international travel and eSIMs. At the same time, competitors are continually publishing content designed to capture the same customer attention.

The way people discover that content is also changing. Customers still use conventional search engines, but a growing number now use generative AI services to research products, compare options and ask detailed questions before making a purchase.

For telecommunications brands, visibility therefore means more than ranking for a fixed set of keywords. Content needs to answer real customer questions, remain factually accurate and perform across both traditional and emerging discovery channels.

Working with our client, we developed a five-phase content architecture that continuously identifies opportunities, creates content, coordinates human approval, publishes approved material and reviews its performance.

The five phases were:

  • Topic research and opportunity identification
  • Content generation and refinement
  • Subject-matter expert review
  • Content management system integration
  • Ongoing content monitoring and optimisation

Together, they formed a continuous content lifecycle rather than a one-off publishing process.

Phase one: identifying valuable content opportunities

Before producing content, the client needed to understand what customers were asking, where demand was changing and where the brand had an opportunity to improve its visibility.

Some telecommunications topics are relatively consistent. Customers will continue to ask what particular services are, how products work and how to resolve common issues. Other topics are more dynamic, responding to new phone releases, changing product propositions, travel seasons and emerging consumer trends.

The first phase used agents to connect with specialist search engine optimisation and generative-search visibility tools. It analysed search demand, relevant questions, emerging topics and gaps in the client’s existing content.

The system also tested representative customer questions across generative search experiences to assess whether the client appeared in relevant responses and how its visibility compared with competitors.

Because generative responses can vary, this was not treated as a single fixed ranking. Instead, the system considered indicators such as brand visibility, citation frequency, competitor presence and coverage of important customer questions.

These findings were converted into a prioritised content backlog. Each opportunity could be ranked according to customer relevance, search demand, existing coverage and potential business value before progressing to content creation. All without the content management team needing to lift a finger.

Phase two: generating and refining content

Once an opportunity had been identified, the next phase produced an initial draft.

The content-generation agents were configured with the client’s tone of voice, brand personality, editorial standards, product information and approved terminology. This helped ensure that drafts reflected the brand and were grounded in relevant source material.

The workflow could create an outline, produce the first draft and refine the article through several targeted review steps. Where visual content was required, the system could retrieve approved assets from the client’s digital asset management platform or initiate an appropriate image-production workflow.

Additional review agents checked drafts against the client’s brand and editorial requirements. These checks could identify prohibited topics, restricted terminology, unsupported product statements, repetitive language and common characteristics of low-quality AI-generated copy.

When a draft failed to meet the required standard, it was returned to a controlled redrafting workflow with more specific instructions and guardrails.

The objective was not to remove editorial judgment. It was to give subject-matter experts a stronger first draft, reducing the time they needed to spend correcting basic structural, stylistic and brand issues. All of this standardised across the digital content team, removing the need for each colleague to configure their own standards and prompts.

Phase three: coordinating human review and approval

Human review was a deliberate control within the architecture.

AI-generated content can be well structured and persuasive while still containing factual errors, inappropriate wording or claims that do not reflect the latest product information. Mistakes can happen. Publishing such material could confuse customers and damage trust in the brand.

Once a draft had passed the automated checks, the workflow created a review case in the client’s enterprise work-management and project portfolio management system.

The case contained the proposed article and the information needed for review. An appropriate subject-matter expert could open the item from their existing work queue, examine the content, make edits and either approve it or return it for further revision.

Closing the review task as approved initiated the next stage automatically. This integration created a visible handover between AI-supported production and accountable human approval without requiring teams to coordinate the process through emails and separate documents.

Phase four: creating the article in the CMS

After approval, a separate workflow prepared the article in the client’s content management system.

The system mapped the content to the correct page structure and taxonomy, applied the required formatting and prepared supporting elements such as images, tables, headings and metadata.

This reduced the repetitive work involved in transferring approved copy into the CMS and helped ensure that articles followed a consistent structure.

As a deliberate publishing control, the workflow could create and populate an article but could not publish it directly to the live website.

Instead, it saved the completed page as a draft. A site manager could then preview the article, confirm that its formatting and visual presentation were correct, and publish it through the standard CMS approval process.

This preserved a final human checkpoint immediately before content became publicly available.

Phase five: managing the 100-day content lifecycle

Publishing an article was not the end of the process.

Search demand changes, product information evolves and content that performs well today may lose relevance over time. An effective content operation therefore needs to review existing pages as systematically as it creates new ones.

The fifth phase introduced a 100-day review cycle. The system regularly reassessed existing content using many of the same signals applied during the initial research phase.

It could identify pages experiencing declining search visibility, reduced generative-search referrals or outdated topic coverage. It could also highlight overlapping articles that might be consolidated and pages that no longer served a useful purpose.

The findings were presented to the content team through a dashboard. The team could decide whether an article should be updated, expanded, consolidated, redirected or retired.

Approved refresh opportunities were then returned to the content backlog, beginning the cycle again.

This connected new content creation with the ongoing management of the client’s existing content estate, reducing the risk of producing more pages while older material became inaccurate or irrelevant.

Creating a scalable content lifecycle

The five phases created an always-on content operation:

  1. Identify what customers want to know.
  2. Prioritise the most valuable opportunities.
  3. Produce a brand-aligned initial draft.
  4. Route it through accountable human review.
  5. Prepare the approved content in the CMS.
  6. Monitor its performance and refresh it when required.

This approach reduced duplication between research, writing, approval and publishing. It also allowed each team to continue working through familiar enterprise systems while automation coordinated the movement of content between them.

Most importantly, the architecture combined scale with control. AI agents handled research, drafting, validation and administration, while subject-matter experts retained responsibility for factual accuracy, brand suitability and final approval.

The pilot result

During the pilot, measurable visits to the client’s website from generative-search referrals increased statistically significantly, as did the clients site average page ranking. Specific metrics are not publicly sharable to protect anonymity of the client.

While generative search remained one part of the client’s wider acquisition strategy, the result demonstrated the growing value of producing content that can be discovered through both conventional search and AI-generated answers.

The wider opportunity extends beyond an individual traffic metric. A continuous content lifecycle enables the client to respond to changing customer interests more quickly, keep existing pages relevant and direct expert time towards judgment and quality rather than repetitive administration.

In a market where customer questions, products and discovery channels are constantly evolving, content operations need to evolve with them.

To learn more about this case study, or how an always-on content architecture could improve your search visibility and content operations, get in touch with us below.

Have a challenge worth solving?

Start a conversation