How it works

From scattered recordings to reviewed, PBX-ready audio.

Which number reaches which service, and what each caller hears there, usually lives in spreadsheets and old WAV files. Dialtone360 puts it in one place you can keep current.

Start free trial Book a demo

The problem

What callers hear is the least-managed part of the phone system.

Numbers, trunks and devices have inventories. The greetings, menus and hold messages on top of them usually don’t, until a migration, a new language or a closure forces a scramble.

Folders of WAVs

Prompts live in shared drives, old PBX backups and email attachments. Nobody is sure which file is live, or what it says.

Spreadsheets of numbers

Which DID reaches which auto attendant is a tab in someone’s workbook, last updated two migrations ago.

Re-record everything

Changing opening hours means a studio booking, one file per language and a different conversion for every platform.

Step 01
Load your sites and numbers
Add sites, DIDs and extensions by hand or from a spreadsheet workbook with a dry-run check, and record which phone service (auto attendant, queue or hunt group) each number reaches.
app.dialtone360.com/app/sites/dal
Step 02
Bring in your announcements
Upload the recordings you have today, or run IVR discovery against a live number to capture what callers hear now. Each prompt is transcribed for you to check, then kept as-is or re-recorded in a consistent voice.
app.dialtone360.com/app/announcements/import
Step 03
Translate, then review before anything goes live
Add the languages your callers speak. Translations and transcripts are drafts until a person approves them. When a script changes, every other language is flagged as out of date so they all stay in step.
app.dialtone360.com/app/announcements/san-jose-main-greeting
Step 04
Download for your PBX
Download each announcement in the audio format your phone platform expects and load it where it plays. Every version stays in the history for the next change.
app.dialtone360.com/app