Contact Sales & Support / Ticket queue open

A ticket about this voice changer software reaches an engineer, not a script, inside one business day.

Ask about a licence quote for gaming or streaming, a refund on the fourteen-day window, or how to route the API into your own product. Every field below goes straight into the queue nineteen people work from.

1business day Typical first reply
14days Refund ticket window
2people On support full time
Send an inquiry

Tell us what you're running, and what's not holding sync

This form covers a licence quote for the Creator, Streamer Pro, Studio or Developer API tier, a support ticket on an existing installation, or a refund request against the fourteen-day window. There is no checkout here — every tier on plans.html is quoted after this form, never charged from it.

Enter your name.
Enter a phone number we can call back.
Enter a valid email address.
Enter an address or leave the field blank if not applicable.

Fields marked with an asterisk are required. Nothing here is a binding order — every tier is quoted, not charged.

A support agent at a desk wearing a headset, typing on a laptop showing a ticket queue
The queue two people work full time, ticket hours Monday to Friday
Direct

Reach a person without the form

Postal address
7 Oak Lane, Austin, Texas 54422, United States
Ticket hours
Monday to Friday, 9:00–18:00 Central. A ticket filed Saturday sits until Monday morning.

Open chat instead

The chat widget in the corner of every page on this site talks to the same ticket queue as this form. It's the faster route for a quick question — "does the API bill per minute or per seat", "will the Creator tier route into two apps at once" — where a full inquiry form is overkill. A conversation started there keeps its own token in your browser, so you can close the tab and come back to it.

Use the support chat launcher in the corner of this page to start a conversation.

Refund tickets on the fourteen-day window get checked against your own hardware, not a blanket policy. Send the setup line above — OS, the app you route into, seat count — and the note on what latency or dropout you're seeing, and the ticket moves faster.

Response time

One business day for a first reply, not a week

Two people run support full time, out of a team of nineteen. That's small on purpose — the same two people who answer a refund ticket also read the latency reports from the audio pipeline team, so a ticket that says "the pitch shift is clipping on my interface" reaches someone who can actually reproduce it, instead of a queue that forwards it three times before anyone tries.

A licence quote for Creator or Streamer Pro usually comes back same day during ticket hours. Studio and Developer API quotes take longer because they involve the partnerships side of the team checking seat counts or metered volume against your own usage estimate — plan on two business days for those.

First reply, standard ticket
< 1 business day
First reply, Studio / API quote
2 business days
Refund ticket decision
within 14 days of purchase
Ticket hours
Mon–Fri, 9:00–18:00 CT
Chat availability
Same hours, same queue
Before you send it

What actually speeds a ticket up

Name the app you route into. "Discord" alone doesn't tell us whether you're on the desktop client, the browser client, or a game with its own built-in voice chat reading the same input device — those three route differently and a support reply has to ask if you don't say.

If it's a refund ticket, say what the dropout looked like: a click, a stutter, a delay that grew over the session. "It didn't work" gets a reply asking the same question back. A specific failure gets a specific answer, usually same day.

If it's a quote for more than one seat, put the seat count in the setup field, not the notes field — that's what routes it to partnerships instead of sitting in the general queue.