Additional Metadata

When you push your audio to our platform, whichever the protocol (SIPREC, an API integration, an FTP upload...), we get some metadata about the call.

But the platform managing the calls does not always have access to all the metadata you're interested in so that your analysis will be relevant. Some data might be stored in your CRM, or any other data platform you have.

This is what we call additional metadata, and we got a way for you to integrate them in uh!ive's platform.

How does it work

For the sake of the example, let's say calls are ingested into uh!ive with SIPREC protocol, and that you have additional data in your CRM. We need to find a way to match the SIPREC metadata to the CRM one.

More specifically:

1. We set up an FTP account on which you'll upload on a regular basis a CSV file coming from the CRM. One header must be named the same way as one metadata we gather with SIPREC. We store this CSV.
2. We define a metadata key that we know will be present both in the CRM additional metadata, and in the "regular" metadata we get with the call's SIPREC headers. That's our reconciliation key.
3. Each time a call is processed, we look for this one key, and look for its value within the CRM CSV
4. If found, we add the whole matching CSV line as new metadata for the call

For example

Let's say the reconciliation key is named agent_id, and the CRM CSV looks like:

And now we receive a phone call via SIPREC, and the headers metadata are as follow:

• datetime = 2026-01-30T12:34:56Z
• phonenumber = +33102030405
• agent_id = cindy

From the CRM CSV, we retrieve the line where agent_id is equal to cindy, there is a result. Therefote the following metadata will be appened to the call, and be visible in the WebApp and our Activate API:

• team_name = diamond
• expertise = sales
• city = Helsinki