Exporting conversation data
Export hands a finished conversation's outputs to IntelieKonnect, which delivers them to an external destination. This page covers what leaves the platform, and how to tell whether a delivery arrived.
- The Voice IntELIEgence module visible in your left-hand navigation.
- These permissions: Voice · Export — VIEW, Voice · App — UPDATE.
- A destination already connected to this application — this screen cannot create one. Until one exists, Export reads No export destinations yet and nothing is delivered.
If Voice IntELIEgence isn't in your navigation, your role doesn't have visibility for it — ask a workspace administrator, or see Permissions and module visibility.
Steps
Open the application and select Export in the left rail, below Settings and Personas.
The Active destination card names the connector and its Trigger — Auto on completion or Manual. Payload counts the mapped fields; Last delivery and Success (30d) are derived from the jobs below.
Select Edit to open Payload field mapping — one row per Voice output (Summary, Action items, Topics & sentiment, Talk time, Grade), each with a Destination field name and an Include switch.
Turn Include off for anything that must not leave, name the fields you keep, then select Save mapping. Two included fields may not resolve to the same name.
Export jobs lists one row per conversation per destination — Job, Destination, Trigger, Conversations, Status, Delivered. A job starts at Pending and settles to Delivered or Failed.
What success looks like
- Payload reports the number of fields you left included.
- A row for the conversation reaches Delivered, and Last delivery shows its timestamp.
What actually leaves the platform
Each delivery is one JSON artefact for one conversation: its id, a reference to the canonical transcript — the redacted one wherever redaction ran, never the raw transcript — and the outputs. With no mapping saved, every output the conversation produced is included. Saving a mapping pins a new application version, so it governs conversations processed from then on and never changes what has already been sent.
If something goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| No export destinations yet. | Nothing is connected for this application. | Nothing is exported until a destination is connected; raise it with your platform administrator. |
| No exports yet, but a destination is shown. | Export is off for the application, or the Trigger is Manual — this screen raises no manual delivery. | Switch export on in Settings → Export and set it to run on completion. Only conversations that finish afterwards are delivered. |
| A row stays at Pending. | IntelieKonnect has the payload and has not reported back. | Reload the page — this table does not refresh itself. |
| A row reads Failed. | The destination refused the delivery. | Hover the pill to read the error, then fix the destination. This screen does not re-send a failed job. |
| An output you expected is absent from the payload. | Its Include switch is off, or the application never generated it — Grade is off by default. | Re-check the row in Payload field mapping, then the application's outputs. |
Next
- Voice application settings — switching export on and choosing its trigger.
- Managing voice application access — who can see deliveries.