04299396) If the issue persists after checking these areas, you may need to modify your post-call analysis configuration to clean formatting errors in the JSON output [(1) ]() .

### Answer The "Error in parsing JSON for call analysis" issue has been reported by other users and can have a few causes: Common Root Causes: 1. Unicode characters in transcripts - Smart quotes or special Unicode characters (U+201C, U+201D, U+2019) in the transcript can break JSON parsing [(1) ]() 2. Extra spaces in post-call analysis fields - Extra whitespace at the end of custom analysis fields (like appointment dates) can cause parsing errors [(2) ]() 3. Post-call analysis prompt formatting - Issues with how the analysis prompts are structured [(1) ]() Recommended Troubleshooting Steps: 1. Check your detailed call logs for: - Error messages during the analysis phase - The exact time when the analysis process fails - Whether the issue happens consistently or intermittently [(3) ]() 2. Review your

post_call_analysis_data

configuration for any extra spaces or formatting issues [(4) ]() [(2) ]() 3. Adjust your post-call analysis prompts (

analysis_successful_prompt

,

analysis_summary_prompt

,

analysis_user_sentiment_prompt

) to handle potential formatting errors [(4) ]() [(1) ]() 4. Consider sanitizing your analysis field inputs to remove trailing spaces and special characters [(1) ]() [(2) ](

​ To learn more, see the sources I considered: [[1] call history error in parsing json](https://discord.com/channels/1186424376300679209/1449983415532257280) [[2] NO PCA](https://discord.com/channels/1186424376300679209/1419739167004299396) [[3] Post-call analysis "Error in parsing openai JSON forn call anaylisis"](https://discord.com/channels/1186424376300679209/1395844709015883847) [[4] Update Voice Agent](https://docs.retellai.com/api-references/update-agent) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.