Managers often need to understand why some team meetings were not recorded, so they can spot patterns, review any issues, and decide whether any follow-up is needed.
With the "Recording Outcomes" in your CSV export, you can:
quickly see which meetings were recorded and which were not
understand the reason a meeting was not recorded
spot repeated issues across your team
decide whether any action or support follow-up is needed
Where to find Recording Outcomes
Go to Team Insights → Conversations → Conferences.
Click "Download CSV"
In the CSV file:
Find the "Outcome Text" column (after "Connected")
This will show:
Recorded → the meeting was recorded successfully
Or the reason it was not recorded
Note: Only recording reasons from the current calendar year are included in the report.
Recording outcomes
Conference meetings
Outcome Text | What it means | What you can do |
Recorded | The meeting was recorded successfully. | No action needed. |
Bot denied from lobby | The bot was not let into the meeting. | Ask your team to admit the bot when joining meetings. |
Lobby timeout | The bot waited in the lobby but was never admitted. | Make sure someone admits the bot. |
Bot kicked | The bot was removed from the meeting. | Ask your team not to remove the bot during calls. |
Recording not allowed | For Zoom meetings only. Local Recording option disabled, or Zoom consent was not given. | Check out this article for more details. |
User disabled the recording | Recording setting was turned off during the meeting. | Remind your team to keep recording on. |
Recording was stopped | Recording started, but stopped because the meeting was rescheduled while the bot was still in the call. | If this happens often, try to update the meeting before it starts. |
Login required | The bot could not join because the meeting required login. | Allow external participants or review meeting settings. |
Wrong URL | The meeting link was incorrect or expired. | Check and update the meeting link in the calendar, and make sure the passcode is embedded in it. |
Consent denied by customer | A participant chose not to be recorded. | Set expectations about recording at the start of the call. |
Invalid meeting link | The meeting link is not supported or is broken. | Check and update the meeting link in the calendar, and make sure the passcode is embedded in it. |
Other | An unknown issue occurred. | If this happens often, contact Jiminny support. |
Dialer calls
Outcome Text | What it means | What you can do |
Recorded | The call was recorded successfully. | No action needed. |
Server error | A system issue prevented the recording. | Try again later. Contact support if it continues. |
Access denied | The system was not allowed to record the call. | Check permissions and dialer settings. |
Setup issue | There is an issue with the call setup or configuration. | Review integration and dialer settings. |
Empty recording | The call connected, but no audio was captured. | Check audio devices and dialer setup. |
Other | An unknown issue occurred. | If this happens often, contact Jiminny support. |
FAQ
Why do I see different reasons instead of just “not recorded”?
Why do I see different reasons instead of just “not recorded”?
Each reason shows what actually happened during the meeting, so you don’t need to investigate each call manually.
Does this fix recording issues automatically?
Does this fix recording issues automatically?
No — this gives you visibility into what happened. You can then decide if any action is needed.
What should I look for in the CSV?
What should I look for in the CSV?
Look for repeated reasons in the Outcome Text column. Patterns usually indicate a team behaviour, setup, or permissions issue.
When should I contact Jiminny support?
When should I contact Jiminny support?
Contact support if:
- You see repeated “Server error”
- You see many “Other” outcomes
- The reason does not match what you expect
- The issue continues over time
