- Contact
- Organisation
- What you need
Scope a Korean-first voice pilot
Form interaction preview. What you type stays in this browser tab — nothing is stored, sent or logged.
What happens after you send this
A form is only worth filling in if you know where it goes. Here is the whole path, with nothing hidden behind a queue.
Immediately
It reaches a named person
Your region, size and volume band decide who picks it up. There is no routing bot and no shared inbox in between.
Day one
We map the workflow together
A short conversation about the use case, expected volume, and where it runs.
Within days
You see the shape of it
We come back with a scoped pilot, the transports it needs, and what we would measure.
After that
A pilot, or an honest no
One use case, tuned against the live stack with your team in the loop — or a straight answer that this is not the right fit yet.

Typical first reply
One business day
Requests that arrive over a weekend are picked up on the next working morning.
What a deployment needs
Teams arriving through this form are usually replacing something that already works, which makes the first conversation about migration risk more than features.
- Korean-first voice agents, tuned end-to-end for real conversations
- One team building the voice engine, operator console, and backend together
- Telephony-ready architecture, with human approval required before production changes
- Tell us about your governance and deployment requirements and we'll walk you through the fail-closed model in detail.

What is built so far
- custom voice-pipeline processors
- 30+custom voice-pipeline processors
- feature flags
- 100+feature flags
- operator-console components
- 450+operator-console components
- care and consumer backend domain modules
- 34care and consumer backend domain modules
Every figure was counted in the repository — audit, August 2026.
Would you rather read first?
You may want to see how it works before starting a conversation. The docs mark which transports are live today and which telephony path is built and key-gated, and the form above will still be here.
If the question is about cost, the pricing page explains how a deployment is scoped before any conversation.