Voice & Writing

Speech Guidelines

Pronunciation, pacing, and verbal communication guidelines

Production

Guidelines for verbal communication, including pronunciation, pacing, and text-to-speech (TTS) applications.

Pronunciation

Brand Name

AspectValue
TextOntopix
IPA/ɒnˈtɒpɪks/
Phoneticon-TOP-iks
Emphasissecond syllable

Don't:

  • ON-to-piks → Emphasis should be on TOP, not ON
  • on-to-PICKS → It's -piks, not -picks

Product Names

ProductPhoneticEmphasis
AudibotAW-di-botfirst syllable

Technical Terms

TermPhoneticNotes
OKLCHoak-L-C-HSpell out as letters after 'oak'
APIA-P-ISpell out, never 'appy'
CLIC-L-I or command lineSpell out or use full phrase
GDPRG-D-P-RAlways spell out
SOC 2sock twoSOC as word, 2 as number
ISOEYE-soPronounced as word, not spelled out

Pacing

SettingValue
Ratemoderate
Words per Minute150

Conversational pace, not rushed but not slow

Pause Durations

ContextDuration
After Heading0.5s
After Sentence0.3s
After Paragraph0.8s
After Section1.2s
Before Important Term0.2s
After Important Term0.3s
Before Code0.5s
After Code0.5s
Thinking Pause0.3s

By Context

ContextRateWPMNotes
Presentationslightly slower130Allow audience processing time
Demomoderate140Match action to narration
Support_calladaptive-Match customer's pace
Ttsmoderate150Clear enunciation

Intonation

Guidelines

  • Maintain conversational rhythm
  • Avoid monotone — vary pitch naturally
  • Rise slightly for questions
  • Fall for statements and conclusions
  • Emphasize key terms and brand names

Patterns

TypePattern
StatementNeutral to slight fall at end
QuestionRise at end
ListRise on items, fall on final item
EmphasisSlight pause before, slower delivery

TTS Guidelines

General

  • Maintain conversational rhythm
  • Avoid monotone — vary pitch naturally
  • Pause before and after important terms
  • Pronounce brand names correctly

Technical Content

  • Slow down slightly for code or commands
  • Spell out short variable names
  • Read URLs as 'example dot com'
  • For file paths, use 'slash' between segments
  • Say 'at sign' for @, 'underscore' for _

Code Reading

  • Read function names in camelCase as separate words (get user → 'get user')
  • Say 'equals' for '=', 'arrow' for '=>'
  • Describe code structure rather than reading syntax verbatim
  • Focus on what the code does, not exact syntax

AI Voice Agents

AI agents representing Ontopix should align with brand voice while adapting to the conversational nature of voice interactions.

Adaptations

  • Slightly more enthusiastic than written tone
  • More frequent acknowledgments ('Got it', 'Sure', 'I understand')
  • Natural filler words acceptable ('So', 'Now', 'Let me')
  • Confirm understanding before proceeding
  • Offer to clarify or repeat when helpful

Restrictions

  • Never impersonate a specific person
  • Always identify as AI when directly asked
  • Don't claim emotions or experiences
  • Be honest about limitations

Greeting Patterns

"Hi, I'm name, Ontopix's AI assistant. How can I help?" "Hello! I'm here to help with context. What can I do for you?"