Cresta was named a Leader in The Forrester Wave: Conversation Intelligence in the Contact Center, Q2 2025 – Access the report!

  • Products
    Back
    PLATFORM
    AI Platform
    Cresta is the enterprise-grade Gen AI platform built for the contact center and trained on your data.
    • Cresta Opera
    • Integrations
    • Responsible AI
    PRODUCTS
    AI Agent
    Cut costs, not quality, with human-centric AI agents you can trust
    Agent Assist
    Harness real-time generative AI to empower agents with unmatched precision and impactful guidance.
    • Knowledge Assist
    • Auto-Summarization
    Conversation
    Intelligence
    Discover and reinforce the true drivers of contact center performance.
    • Cresta Insights
    • Cresta Coach
    • Cresta Quality Management
    • Cresta AI Analyst
  • Solutions
    Back
    USE CASES
    Sales
    Discover and reinforce behaviors that accelerate revenue growth
    Customer Care
    Deliver brand-defining CX at a lower cost per contact
    Retention
    Transform churn risks into
 lifelong promoters
    Collections
    Accelerate collections while minimizing compliance risk
    INDUSTRIES
    Airlines
    Automotive
    Finance
    Insurance
    Retail
    Telecommunications
    Travel & Hospitality

    Cresta’s AI Agent is Omnichannel: Seamless Conversations, Anytime, Anywhere

    LEARN MORE
  • Customers
    Back
    Customer Stories
    Learn how Cresta is delivering lasting value for our customers.
    • CarMax
    • Oportun
    • Brinks Home
    • Snap Finance
    • Vivint
    • Cox Communications
    • Holiday Inn
    • A Top Telecom
    • View all case studies

    Our Own Zero to One: Lessons Learned in Building The Brinks Home AI Agent

    LEARN MORE
  • Resources
    Back
    Resources Library
    • Webinars
    • Ebooks
    • Reports
    • Solution Briefs
    • Data Sheets
    • Videos
    • Infographics
    • Media Coverage
    • Press Releases
    Blog
    Industry News
    Help Center
    Solution Bundles

    AI Maturity Blueprint: A Practical Guide to Scaling AI Adoption in the Contact Center

    LEARN MORE
  • Company
    Back
    About Cresta
    Careers
    Trust
    Customers
    Partners

    Cresta Named a Leader and “…a Force To Be Reckoned With” in The Forrester Wave™: Conversation Intelligence Solutions for Contact Centers, Q2 2025

    READ THE POST
Request a demo
Request a demo
  • Cresta Blog
  • Technology

Understanding Cresta’s Voice Platform – Handling Incoming Traffic with Customer-Specific Subdomains

Cresta’s voice platform is a cutting-edge solution designed to provide real-time insights and actionable intelligence during customer interactions. It integrates with a wide variety of Contact Center as a Service (CCaaS) platforms, capturing and processing live audio streams to assist agents with timely guidance and recommendations. To shed light on this technology, we’ve divided our exploration into a three-part series, that will be published over the next couple weeks:

Part One (this article): Handling Incoming Traffic with Customer-Specific Subdomains

In this first installment, we dive into how Cresta manages incoming traffic efficiently, including how customer-specific subdomains ensure scalability and isolation. We’ll explore the role of DNS, ingress controllers, and AWS Elastic Load Balancers in routing traffic to the right services.

Part Two: Voice Stack

The second article will focus on how the platform processes live audio streams through its voice stack and how business logic layers power real-time guidance for agents. This part will highlight key components like speech recognition and how conversation data flows through the system.

Part Three: ML Services, Inference Graphs, and Real-Time Intelligence

The final installment will take you deeper into the machine learning (ML) stack, exploring how inference graphs orchestrate model workflows, how customer-specific policies influence ML processing, and how Cresta delivers actionable insights in real-time.

Glossary

Going forward, we want to clearly define some domain- or Cresta-specific terms

  1. Customer profile — this is a partitioning detail for the customer data, with an 1 to n relationship between customers and profiles (one customer can have multiple profiles), with each profile residing in an AWS region.
  2. CCaaS — Contact Center as a Service – a cloud-based solution that provides contact center functionality, such as call handling, customer support and communication management. Examples include Amazon Connect, 8×8, Five9, etc. Cresta currently supports over 20 CCaaS integrations.

Overview of Traffic Handling in Cresta’s Platform

Cresta’s voice platform needs to handle incoming traffic efficiently and route it to the appropriate services. Cresta employs a system to manage customer-specific subdomains, ensuring scalability and flexibility.

Each customer has their own unique subdomain, e.g.’customer1.us-west2.cresta.ai’ that acts as an entry point. This isolates customer traffic, ensuring that the requests and resources are routed to their specific environments, without coupling the underlying compute infrastructure (EKS in our case) to the URLs, and without requiring a separate routing service to proxy requests from a generic domain, e.g. ‘platform.cresta.ai’, to the environment where the customer’s resources are located.

This also helps provide transparency to the hosting region, for data sovereignty considerations, as customers may want data to not pass across regions. For examples, customers in the EU will want all their data held in EU data centers due to GDPR.

Our services are hosted inside Kubernetes clusters (EKS), which means all traffic will eventually end up being served by one of our Kubernetes deployments. Handling traffic and routing to the correct services has a few moving parts:

  1. DNS Resolution
    We use **AWS Route 53** as our DNS service for resolving domain names to the correct cluster’s load balancer.
  2. ExternalDNS Controller
    Kubernetes controller that synchronizes exposed Kubernetes Ingresses hosts with DNS providers (Route 53 in our case). It creates or updates DNS records in Route 53 based on the spec.rules.host field in Ingress resources.
  3. AWS Load Balancer Controller
    Kubernetes controller that provisions and manages **AWS Elastic Load Balancers (ELBs)**.
  4. Ingress Controller
    The **NGINX Ingress Controller** manages and routes in-cluster traffic based on Ingress rules. Requests are routed to the appropriate service by matching rules like domain name or path.

Traffic flow

Whenever a new customer profile (a partitioning detail for a customer’s data, 1 customer can have n profiles) is registered, the profile has a specific subdomain that will be created in the ingress rules. In practice, our customer profile provisioning flow will create the new ingress rules using Flux-CD which will lead to DNS entries being provisioned.

  1. DNS Entry Creation (ExternalDNS):
    When an Ingress rule (like `api.us-west-2-staging.cresta.ai`) is registered, the external-dns controller creates a DNS entry in Route 53 pointing to the load balancer’s endpoint.

  2. Load Balancer Provisioning (AWS Load Balancer Controller):The AWS load balancer controller creates ELBs in AWS based on the LoadBalancer Kubernetes services. In our case, for handling external traffic there is an ELB associated with the NGINX LoadBalancer service.
  3. Routing Within the Cluster (Ingress Controller):Once the ELB forwards the traffic to the Kubernetes cluster, the NGINX Ingress Controller evaluates the domain and path to route the traffic to the appropriate service. Cresta uses Wallarm, based on the Community NGINX Ingress Controller, which adds additional security features like real-time attack detection, API Security, detailed analytics, etc.Example of incoming request:POST https://api.us-west-2-staging.cresta.ai/v1/customers/

    Ingress rule that matches the request and redirects it to the apiserver service inside the cluster: 

We don’t want to get in too many of the nitty gritty details, but one important aspect that needs to be mentioned as part of the routing mechanism is handling long-running calls / audio streams. In case the connection to our servers gets severed, we need to be able to recover the connections and resume the calls.

For the app installed on the agent’s desktop, since we control the audio paths so we have implemented recovery protocols. If the streaming connection is interrupted, these protocols can re-establish the connection and resume the stream from the point of disruption, ensuring minimal data loss.

For CCaaS we rely on the external platform’s stream recovery mechanism.

We will go deeper into the voice stack in part 2 of this article series. Stay tuned.

 

Author:

Florin Szilagyi

February 25, 2025

100 South Murphy Ave Ste 300
Sunnyvale, California 94086

Karl-Liebknecht-Str. 29A
10178 Berlin, Germany

100 King Street West
1 First Canadian Place, Suite 6200
Toronto ON M5X 1E8

Info
  • AI Platform
  • Customers
  • Resources
  • Partners
  • Trust
  • About
  • Careers
  • Blog
  • Support
  • Contact Us
Follow us
  • LinkedIn
  • YouTube
  • Twitter

Newsletter

Subscribe for the latest news & updates

© 2025 Cresta

  • Terms of Service
  • Privacy Policy
  • Employee Privacy Notice
  • Privacy Settings