Kaliper Documentation
Calls quality control

How it works
Once connected and allowed by API keys, Kaliper will start fetching the calls from your systems. They can not be fetched all at once, so the batches on 100 calls will be downloaded every 5 minutes, and put into processign queue.
The process goes like this:
Transcription
Taxonomy (internal process, not sure why we mention it here)
Scoring
All the new calls will be requested every 5 minutes too, apart from extra long calls (more than 20 minutes), which will arrive separately (we use "pixels" for those requests from your system).
The problems could happen in two places: system side (no recording or impossible to download a recording), and Kaliper side (processing failure). Normally it all resolves itself over 1 hour.
Scoring: setting up and using
We've added the ability to filter your collection lists in the CMS. This allows you to keep your content in a single collection, yet customize how that collection is presented on each of your web pages. For example, if you're creating docs for your app, you might want to filter articles per topic on your homepage. Or when creating a blog, you might want to filter your blog posts per category.
Near-time and overnight processing
To save credits and shmupics, you might want to switch your calls to overnight processing (done per Campaign dimension)
© 2026 A-Launch. All rights reserved.