Telecom Subscriber Insights

gcpAI servicegoogle-telecom-subscriber-insights

Customer-hosted models forecasting subscriber churn, upgrades and next best offers.

Provider
gcp
Category
Compute
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
authenumapi-key | oauth | iam | noneno—▸ iam
contentFilteringboolean—no—inherited
customerManagedKeysboolean—no—inherited
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
deployment · component propertyenumcustomer-hostednocustomer-hostedinherited
ingestion · component propertyenumbatch | streamingnobatchinherited
keyStoreboolean—nofalseinherited
managedboolean—nofalse▸ false
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ structured
output · component propertyenumchurn-propensity | upgrade-propensity | next-best-offer | segmentnochurn-propensityinherited
publicEndpointboolean—no—▸ false
quotaUnitsPerMinuteinteger—no—inherited
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
viaGatewayboolean—nofalseinherited
Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

  • — all of these hold:
  • — the node's `auth` is "api-key"
  • — the node's `keyStore` is false
  • — the node has at least one incoming edge from an app-server, worker or client
  • — this does not hold:
  • — the design contains a node of kind key-management
stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

  • — all of these hold:
  • — the node's `stateless` is false
  • — the node sits inside exactly 1 availability-zone group
  • — this does not hold:
  • — the node sits inside at least one cell group
Use it in a design
nodes:
  - { id: "telecom-subscriber-insights", component: "google-telecom-subscriber-insights" }
Other AI service products · 125
Content Moderationalibaba-content-moderationalibabacloudai-serviceFraud Detectionalibaba-fraud-detectionalibabacloudai-serviceID Verificationalibaba-id-verificationalibabacloudai-serviceIntelligent Robotalibaba-intelligent-robotalibabacloudai-serviceModel Studioalibaba-model-studioalibabacloudai-serviceSmart Conversation Analysisalibaba-smart-conversation-analysisalibabacloudai-serviceAmazon Bedrockaws-bedrockawsai-serviceAmazon Bedrock AgentCoreaws-bedrock-agentcoreawsai-serviceAmazon Bedrock Data Automationaws-bedrock-data-automationawsai-serviceAmazon Bedrock Guardrailsaws-bedrock-guardrailsawsai-serviceAmazon Comprehendaws-comprehendawsai-serviceAmazon Comprehend Medicalaws-comprehend-medicalawsai-serviceAWS Elemental Inferenceaws-elemental-inferenceawsai-serviceAmazon Forecastaws-forecastawsai-serviceAmazon Fraud Detectoraws-fraud-detectorawsai-serviceAWS HealthScribeaws-healthscribeawsai-serviceAmazon Lex botaws-lexawsai-serviceAmazon Lookout for Equipmentaws-lookout-for-equipmentawsai-serviceAmazon Lookout for Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Personalizeaws-personalizeawsai-serviceAmazon Pollyaws-pollyawsai-serviceAmazon Q Businessaws-q-businessawsai-serviceAmazon Rekognitionaws-rekognitionawsai-serviceAmazon Textractaws-textractawsai-serviceAmazon Transcribeaws-transcribeawsai-serviceAmazon Translateaws-translateawsai-serviceContent Safetyazure-ai-content-safetyazureai-serviceAzure AI Custom Visionazure-ai-custom-visionazureai-serviceAzure AI Faceazure-ai-faceazureai-serviceAzure Languageazure-ai-languageazureai-serviceAzure Speechazure-ai-speechazureai-serviceAzure Translatorazure-ai-translatorazureai-serviceAzure Visionazure-ai-visionazureai-serviceAzure Content Understandingazure-content-understandingazureai-serviceMicrosoft Discoveryazure-discoveryazureai-serviceAzure Document Intelligenceazure-document-intelligenceazureai-serviceFoundry Agent Serviceazure-foundry-agent-serviceazureai-serviceFoundry Modelsazure-foundry-modelsazureai-serviceAzure AI Immersive Readerazure-immersive-readerazureai-service
and 85 more → AI service page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Telecom Subscriber Insights: forecasts churn and upgrade propensity and recommends next
# best offers for a carrier's subscriber base. "Telecom Subscriber Insights documentation":
# usage records, billing, CRM and app data are ingested into BigQuery and normalised to
# predefined data models; the product ships as a Google Cloud project that is built and
# transferred to the customer, who then hosts and operates it.
schemaVersion: "1"
type: "component"
id: "google-telecom-subscriber-insights"
kind: "ai-service"
provider: "gcp"
docs: "https://docs.cloud.google.com/telecom-subscriber-insights/docs"
defaults:
  auth: "iam"
  modality: "structured"
  publicEndpoint: false
  managed: false
properties:
  deployment:
    type: "enum"
    values: ["customer-hosted"]
    default: "customer-hosted"
  ingestion:
    type: "enum"
    values: ["batch", "streaming"]
    default: "batch"
  output:
    type: "enum"
    values: ["churn-propensity", "upgrade-propensity", "next-best-offer", "segment"]
    default: "churn-propensity"

The same page as markdown, for an agent: /catalogue/components/google-telecom-subscriber-insights.md