Chatterbox Turbo Tags: All 9 Reactions and Examples
Chatterbox Turbo supports a small documented set of non-speech reaction tags: cues for laughter, sighs, coughs and related sounds. These square-bracket markers are not an open-ended language for directing every emotion. Use the exact documented spellings rather than assuming any description in brackets is a supported command.
This reference concerns Resemble AI's Chatterbox Turbo model offered in Zoice. The reaction list comes from upstream model documentation. The examples have not been runtime-tested in Zoice, and no audio was generated for this guide. Tokenizer strings discussed separately below are experimental research, not evidence of working features.
All 9 Documented Chatterbox Turbo Tags
[clear throat], [sigh], [shush], [cough], [groan], [sniff], [gasp], [chuckle], [laugh]
Chatterbox Turbo is documented as English-only. The tags above request non-speech reactions rather than a continuous emotion style. For example, [laugh] is a reaction cue; it is not a guarantee that every following sentence will sound cheerful. The voice, surrounding words and runtime integration can affect the outcome.
| Exact tag | Intended reaction | Illustrative placement |
|---|---|---|
| [clear throat] | Throat clearing | [clear throat] May I have your attention? |
| [sigh] | A sigh | [sigh] I left the keys upstairs. |
| [shush] | A shushing sound | [shush] The baby is asleep. |
| [cough] | A cough | [cough] Excuse me. Let me start again. |
| [groan] | A groan | [groan] Not another flight of stairs. |
| [sniff] | A sniff | [sniff] Is that fresh bread? |
| [gasp] | A gasp | [gasp] You found the missing letter! |
| [chuckle] | A chuckle | [chuckle] I should have guessed. |
| [laugh] | Laughter | That was my hat all along. [laugh] |
The table shows intended placement and meaning, not measured output. Keep the spelling and singular forms shown: [laugh], not an assumed variant such as [laughs]; [clear throat], not an invented alias. Documentation of one spelling is not evidence that related spellings are also supported.
How to Place Reaction Tags in a Script
Put a reaction near the point where it makes sense in the line. A gasp before a surprise or a sigh before a resigned sentence is easier to interpret than a cluster of unrelated reactions. As an editing starting point, use one or two cues per sentence at most. This is a conservative writing suggestion, not a documented parser limit.
Do not infer precise timing from the tag's position. A reaction marker does not establish the exact duration, loudness or location of the resulting sound. If you later generate a clip, listen to the surrounding words as well as the reaction and adjust one element at a time.
Copyable Reaction-Only Script Examples
A short comic story
I finally finished the puzzle [laugh] and it was missing one piece. [sigh] Of course it was. [chuckle] Do not tell anyone.
An interruption and restart
[clear throat] Welcome, everyone. [cough] Excuse me. Let me start again. Thank you for joining us this afternoon.
A quiet discovery
[shush] Someone is coming down the hall. [gasp] It is the person we have been waiting for.
These scripts use only the documented reaction set. They are illustrative text, not recordings, tested examples or promises of a particular performance. Keep an untagged copy of your script so you can compare the effect if you decide to test it yourself.
10 Tokenizer-Derived Style Tokens: Unverified
The following strings appear in the model's token file. They are preserved here as experimental research, separate from the 9 documented reaction tags:
[angry], [fear], [surprised], [whispering], [crying], [happy], [sarcastic], [dramatic], [narration], [advertisement]
Tokenizer presence alone does not prove that inference code recognizes a string as a delivery control, that the selected checkpoint responds to it, or that an app integration preserves it. Their behavior is unverified and runtime-dependent. This guide does not claim that putting one at the start of a sentence activates a style, and none appears in the reaction-only example scripts above.
Do not present these 10 strings as additional supported tags when describing the model to someone else. Establishing support would require actual runtime testing with the relevant model, voice and integration. No such tests were performed here, so these tokens are not a basis for a production feature promise.
Using the Reference With Zoice AI Voice
Open app.zoice.com/voice and choose Chatterbox Turbo when available in the model selector. Use English text and start with a single documented reaction cue. The existing screenshots below show shared composer controls only. They do not show Chatterbox selected, a Chatterbox voice list or a generated result.
1. Enter a short script
This crop shows the Enter the script here field. After selecting Chatterbox Turbo, enter a short line such as [sigh] I left the keys upstairs. The screenshot itself contains no tagged script and is not evidence of reaction support.
2. Choose from the available voice options
The crop shows the Select voice control. Choose a voice option exposed for your selected model; do not assume a voice shown for another model is available here. This guide has not tested the model-specific picker or generated audio.
3. Check the model and exact spelling
Before using Generate, confirm the model and the spelling of the reaction tag. If you choose to request output, evaluate it before relying on it. There is no generated player or download demonstration in this reference.
Troubleshooting Without Assuming Support
If a reaction is ignored or spoken aloud, first confirm the selected model and documented tag spelling. Simplify the sentence and remove extra cues before drawing conclusions. A single unexpected output cannot identify whether the cause is text preparation, voice behavior or the integration. This guide does not guarantee that unsupported tags are always read aloud; they may also be ignored or handled inconsistently.
There is no documented pause tag in the reaction set. Use ordinary punctuation to structure the script, without promising an exact silence duration. Do not invent [pause] or assume an XML break control is supported by this model merely because a different system accepts it.
FAQ
Can I make custom Chatterbox Turbo tags?
Free-form custom tags are not a documented Chatterbox Turbo feature. Use the 9 documented reaction spellings rather than treating arbitrary bracketed text as a supported control.
Are [happy] and [whispering] supported emotion controls?
They appear in the tokenizer-derived research list, not the documented reaction set. Their presence is insufficient to establish working style control, and their behavior has not been tested here.
Does Chatterbox Turbo support other languages?
Chatterbox Turbo is documented as English-only. This guide does not extend claims from other Chatterbox model variants to Turbo.
Does [shush] make the whole sentence a whisper?
[shush] is a documented non-speech reaction cue, not a documented sentence-wide whisper instruction. Do not conflate a reaction sound with continuous vocal style.
Have these tags been tested in Zoice?
No. The supported-list wording refers to upstream documentation, not Zoice runtime verification. The 10 experimental strings are even more limited evidence: tokenizer entries only, with no working inference claim.
Open Zoice AI Voice
Inspect the available model options in Zoice AI Voice. For application integration details, use Zoice developer documentation and check the current endpoint's exposed model options.