Start with the recordings you already have.
Bulk upload is the day one path: export a batch of recordings, upload them, and watch each file process with a status of its own. Ask the team to confirm support for your phone platform and recording format.
Three ways calls reach the workspace.
- Step 1Choose the files
- Step 2Files process one by one
- Step 3Each call gets its status
- RecordingAdded in setup
- AgentAdded in setup
- Client accountAdded in setup
- TimestampAdded in setup
- DurationAdded in setup
- TagsAdded in setup
- Phone number, maskedAdded in setup
Every path ends in the same call log.
Where results go.
Once a call is scored, the result moves to the places the team already looks.
- Smart folders
- Email alert
- Slack channel
- CSV and PDF exports
What to confirm before the first upload.
Four details settle most of the intake conversation. Each one is confirmed with the team before the first batch is sent.
| Detail | What gets confirmed |
|---|---|
| Recording format and length | The file type the phone system produces and the typical length of a call, so the first batch is prepared the right way. |
| Call metadata available per file | Which of the seven fields travel with the file, and which get added by hand or matched from an export. |
| Client and agent identifiers | How the phone system names the client account and the agent, so tags in the call log match the names the team uses. |
| Retention and deletion expectations | How long recordings stay in the workspace, and what happens to them when the pilot ends or an account closes. |
Bring a folder of calls.
The pilot starts with one account and the recordings that already exist for it. A week of calls is enough to see the call log fill, watch each file take its status, and check that the fields the team tracks today arrive with the call.
The person who owns the phone system joins the first session, since the export and its metadata get mapped in that conversation.
Four things for the first batch.
- A week of recordings from one account.
- The export your phone system produces today.
- The fields your call log already tracks.
- The person who owns the phone system.
The first batch becomes the first review queue, and its metadata becomes the map for the scheduled drop or the platform connection.
Plan the pilotThree questions about intake.
The questions that come up before the first batch is sent.
Can we evaluate before connecting the phone system?
Yes. Bulk upload runs the whole pilot. Export a batch of recordings, upload them, and every call takes its place in the call log with a processing status of its own. The connection to the phone platform gets scoped once the team has seen the first results.
Are all phone platforms supported?
Platform support depends on where the recordings live and which metadata is available. Bring the name of your phone system and a sample export so the CallSniper team can confirm the intake path.
What formats does bulk upload accept?
Common audio and video recording formats. The exact file type and the typical call length are confirmed with the team before the first batch goes in.
Plan the recording path together.
Start with a sample demo, then agree how your own recordings will reach CallSniper for an evaluation.