Skip to main content

Programs

Programs (Genesys Cloud Speech & Text Analytics)

SectionDescription
Feature AreaQuality Management → Speech & Text Analytics
Admin LocationAdmin → Quality → Programs
Primary FunctionGroup multiple Topics into a business-level analytics package and apply them to queues or Architect flows
Data SourceInteraction transcripts generated by Speech & Text Analytics
Typical UsersQuality Administrators, Analytics Administrators
Key DependencySpeech & Text Analytics and Topics must be configured
SourceTranscript + Genesys Documentation

Programs act as the logical container for Topics and determine where those topics are applied in the contact center. This allows organizations to monitor specific customer intents (billing issues, cancellation requests, product complaints, etc.) for specific operational areas such as queues or routing flows.


Summary Table

AttributeDetails
Feature TypeSpeech Analytics Configuration
ScopeQueue or Architect Flow
FunctionTopic grouping and analytics detection
Topic LimitNot explicitly documented in Genesys UI documentation
Dialect RequirementMust match speech analytics language model
Data UsedVoice transcripts and digital interaction transcripts
Configuration LevelOrganization-wide analytics configuration

Study Notes

TopicExplanation
ProgramsContainers grouping multiple Topics for analytics
TopicsPhrase detection logic used by programs
DialectDetermines language model used for phrase matching
Queue MappingApplies program analytics to queue interactions
Flow MappingApplies program analytics to interactions routed through Architect
Intent DetectionPrograms identify business-level conversation intents

Programs allow the contact center to analyze conversations differently depending on the department or business goal.

Example:

ProgramTopicsScope
Billing InsightsBilling Dispute, Refund RequestBilling Queue
Retention InsightsCancel Subscription, Contract TerminationRetention Queue

Transcript Implementation Notes

Source: Transcript

The instructor explains how Programs function and how they are configured:

StepInstruction
Step 1Navigate to Admin → Quality → Programs
Step 2Create a program that packages related topics
Step 3Select a dialect that matches the transcript language model
Step 4Add existing topics or merge phrases into topics
Step 5Map the program to specific queues or Architect flows
Step 6Save the configuration so analytics can detect those topics

Operational insight from transcript:

  • Programs represent business-level intent detection packages
  • Different departments create different programs
  • Programs must be linked to queues or flows to analyze interactions

Example given in concept:

Program: Billing Analysis
Topics: Refund Request, Payment Issue
Queue: Billing Support

Navigation

TaskNavigation Path
View ProgramsAdmin → Quality → Programs
Create ProgramAdmin → Quality → Programs → Create Program
Edit ProgramAdmin → Quality → Programs → Edit
Delete ProgramAdmin → Quality → Programs → Delete
Manage TopicsAdmin → Quality → Topics
Discover TopicsAdmin → Quality → Topic Miner

Configuration Fields (UI Form Fields)

Main Page

UI FieldDescriptionOptions
Program ListDisplays configured programsRead-only
Program NameName of programText
DescriptionProgram explanationText
DialectLanguage model used for phrase matchingExample: English – United States
TopicsTopics assigned to the programRead-only
QueuesQueues mapped to the programRead-only
FlowsArchitect flows mapped to the programRead-only
SearchSearch programsText
Create ProgramCreate new programButton
EditModify programButton
DeleteRemove programButton
RefreshReload program listButton

Create/Edit Form

UI FieldDescriptionOptions
Program NameUnique identifierText
DescriptionExplanation of program purposeText
DialectLanguage model for topic detectionExample: English – United States
TopicsTopics included in the programMulti-select list
QueuesQueues where analytics should applyMulti-select list
FlowsArchitect flows where analytics should applyMulti-select list
TagsOptional metadata classificationTag selector
SaveSave programButton
CancelCancel configurationButton

Character limit for fields: Not explicitly documented in Genesys UI documentation


Tabs, Toggles, Dropdowns, Action Buttons

Element TypeItems
TabsTopics / Queues / Flows
DropdownsDialect
Multi-Select FieldsTopics / Queues / Flows
ButtonsCreate Program / Save / Cancel / Edit / Delete / Refresh
TogglesNot explicitly documented in Genesys UI documentation

Dependencies

ComponentPurpose
Speech & Text AnalyticsGenerates transcripts used by programs
TopicsPrograms rely on topics for phrase detection
Topic MinerHelps discover phrases that become topics
Interaction RecordingRequired for voice transcription
ArchitectFlows can be mapped to programs

Platform Integration / Related Components

ComponentRelationship
Speech & Text AnalyticsCore analytics engine
TopicsDetection logic used by programs
Topic MinerPhrase discovery tool
Sentiment FeedbackImproves sentiment classification
Interaction AnalyticsDisplays program results

Integration Examples

IntegrationDescription
Analytics APIRetrieve topic trends and analytics data
Conversations APIAccess transcripts for interactions
Notifications APISubscribe to interaction lifecycle events

Example workflow:

Customer Interaction
        ↓
Speech-to-Text Transcript
        ↓
Topic Detection
        ↓
Program Analytics
        ↓
Analytics API → External BI Dashboard

Related Topics / Further Reading

TopicDescription
Speech & Text AnalyticsTranscript analysis engine
Topic MinerPhrase discovery
TopicsPhrase detection configuration
Sentiment FeedbackCorrect sentiment classification
Evaluation FormsAgent quality evaluation

Implementation Checklist

TaskStatus
Enable Speech & Text Analytics
Create Topics
Identify queues or flows
Create Program
Assign topics to program
Map queues or flows
Validate analytics results

Implementation Guide

StepAction
Step 1Enable Speech & Text Analytics
Step 2Create required topics
Step 3Navigate to Programs
Step 4Create new program
Step 5Assign topics
Step 6Select dialect
Step 7Map queues or flows
Step 8Save configuration

How to Implement

PhaseDescription
Topic DefinitionIdentify phrases representing customer intent
Program CreationGroup topics logically
Interaction ScopeAssign queues or flows
ValidationConfirm topics appear in analytics

Workflow

Customer Interaction
      ↓
Recording Engine
      ↓
Speech-to-Text Transcription
      ↓
Topic Detection
      ↓
Program Analytics
      ↓
CX Insights Dashboard

Architecture Diagram

Customer Interaction
       ↓
Recording Engine
       ↓
Speech-to-Text
       ↓
Transcript Storage
       ↓
Topic Detection
       ↓
Programs
       ↓
Analytics Dashboard

Real Flow Scenarios

Billing Issue Detection

Customer: "I was charged twice"
      ↓
Transcript generated
      ↓
Topic: Billing Dispute detected
      ↓
Program: Billing Insights triggered

Cancellation Request

Customer: "I want to cancel my subscription"
      ↓
Topic: Cancellation Request detected
      ↓
Program: Retention Insights

Usage Scenarios

ScenarioDescription
Customer intent detectionIdentify why customers contact support
CX analyticsUnderstand frequent issues
Compliance monitoringDetect regulatory statements
Product feedback monitoringIdentify complaints

Implementation Examples

ExampleConfiguration
Billing ProgramRefund Request / Billing Dispute topics
Support ProgramTechnical Issue / Login Problem topics
Sales ProgramProduct Inquiry / Purchase Intent topics

Design Example

Support Queue
      ↓
Speech Analytics Transcript
      ↓
Topic Detection
      ↓
Program Groups Topics
      ↓
Analytics Dashboard Displays Trends

Best Practices

PracticeReason
Group topics by departmentImproves analytics clarity
Avoid overly large programsMaintain accuracy
Use clear namingImprove reporting readability
Validate topics regularlyEnsure phrase detection accuracy

Source: Operational Best Practice


Naming Convention

ResourceExample
ProgramBilling_Insights
ProgramCustomer_Retention
ProgramProduct_Feedback

Naming pattern:

<Department>_Insights

Security Considerations

ControlDescription
Role-based accessRestrict program creation
Transcript protectionProtect sensitive interaction data
EncryptionProtect stored recordings
Data retention policiesManage transcript lifecycle

Limitations / Constraints

ConstraintDescription
Requires Speech AnalyticsPrograms depend on transcripts
Topic dependencyPrograms cannot exist without topics
Dialect dependencyPhrase detection depends on language model
Topic accuracyIncorrect topics lead to false detections

Troubleshooting

IssueCauseResolution
Topics not detectedTopic not added to programAdd topic
No analytics resultsSpeech analytics disabledEnable transcription
Program not appliedQueue or flow not mappedAssign queue or flow
Incorrect detectionTopic phrases inaccurateUpdate topic configuration

Interview Cheat Sheet

QuestionAnswer
What is a Program?Container grouping topics for analytics
What does it analyze?Interaction transcripts
What components are required?Topics and Speech Analytics
Where are programs applied?Queues or Architect flows
What is the purpose?Detect business intents

Key Takeaways

TopicSummary
ProgramsGroup topics for analytics
TopicsDetect phrases in conversations
Queue MappingDetermines where analytics apply
Speech AnalyticsGenerates transcripts
Business InsightsPrograms enable intent detection

Screenshots