### Answer
This "Error in parsing JSON for call analysis" issue has been reported by other users and is typically caused by special characters in the transcript—specifically Unicode smart quotes (like curly quotes) that break JSON parsing during post-call analysis. [(1) ](
)
To resolve this:
1.
Review and adjust your post-call analysis prompting - Modify the prompts for your post-call analysis to avoid or handle formatting that could produce invalid JSON.
2.
Check detailed call logs - Look at the logs for:
- Any error messages during the analysis phase
- The exact time when the analysis process fails
- Whether the issue happens consistently or intermittently [(2) ](
)
3.
Consider sanitizing output - If your agent responses or user inputs contain special characters, you may need to adjust your prompting to produce cleaner text that won't break JSON parsing. [(1) ](
)
This is a known issue that can be addressed through prompt adjustments on your end.