Call Details
Bolna ID:
f52f8375-38c9-4e5e-9d7f-2593155d5d70
Phone: +919000140699
From: +918035316264
Status: busy
Processing: FAILED
Duration: N/A
Cost: N/A
Hangup Details
Hangup By: Carrier
Reason: Call recipient was busy
Timestamps
Started:
2025-11-02 12:21:26
Ended:
Not set
Last Processed:
Not set
Last Retry At:
Not set
Next Retry Scheduled:
2025-11-02 12:27:05
Next Call Scheduled:
2025-11-02 12:27:05
Call Timeline 6
Call History (Raw Callbacks) 3
{created_at_str=2025-11-02 06:51:27, agent_id=db818162-fabe-4ac8-8a6a-c61223150a70, total_cost=0.0, batch_id=null, cost_breakdown={synthesizer=0.0, transcriber=0, synthesizer_breakdown={welcome_message=0.0, conversation=0}, llm=0, platform=0, transcriber_breakdown={analytics=0, conversation=0}, network=0, llm_breakdown={analytics=0, summarization=0, extraction=0, conversation=0, hangup=0}}, created_at=2025-11-02T06:51:27.353221, scheduled_at=2025-11-02T06:51:27.353157, custom_extractions=null, telephony_data={duration=0.0, to_number=+919000140699, provider_call_id=5c6d4bfc-26be-43fb-9dff-f7d59074402e, hosted_telephony=false, recording_url=null, provider=plivo, hangup_provider_code=3010, from_number=+918035316264, call_type=outbound, hangup_by=Carrier, hangup_reason=Call recipient was busy}, context_details={recipient_phone_number=+919000140699, recipient_data={recipient_phone_number=null, review_completed=2025-11-02 12:10:46, callback_request_id=null, is_callback=null, fullName=Siva, resume_review_id=6906fcb218c34103789121f3, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume has clearly sectioned areas like Profile, Skills, and Work Experience which improves readability. However, the inclusion of more headings with separators could enhance the overall layout., score=68, readability=The contact information at the top is concise, yet crowded, and could benefit from better spacing. The Skills section is detailed but might overwhelm the reader with a lack of hierarchy., essentialSectionsPresence=Key sections such as Work Experience and Education are present, but the Projects section isn't clearly demarcated which makes following the chronology hard. Adding project titles under the appropriate experience section could provide better clarity., scale=100}, atsReadabilityScore={feedback=Overall, the resume is fairly compatible with ATS parsing due to straightforward sectioning without complex formatting. Minor improvements could increase keyword frequency for better role alignment., score=65, scale=100, keyElementsReadableByATS=The name, employer, and role are clearly visible without any unnecessary stylization. However, integrating more relevant industry keywords related to Android development could boost ATS scores.}, impact={feedback=The resume demonstrates impactful achievements, yet many lack quantifiable metrics. Consistent use of strong, active verbs could strengthen the narrative around achievements., score=62, spellCheck=There are no blatant spelling errors, ensuring the content is professional. However, grammatical consistency in terms of tense and phrasing could be reviewed for improvement., bulletPointsUsage=The bullet points are used effectively, but some are overly lengthy, making them less impactful. Consider breaking longer points into concise actions and results., weakActionVerbs=Most actions are described using active verbs, but some points can be enhanced using more dynamic terminology. For example, replace 'developed' with 'engineered' or 'executed'., scale=100, quantifyingImpact=The resume includes some quantified achievements, such as reducing app crashes by 35%. Increasing the number of quantified metrics will highlight the candidate's true impact more effectively., repetitionAvoidance=There are limited repetitions of action verbs, yet diversity in verbs could further enhance engagement. Introducing variety in language can avoid reader fatigue., accomplishmentLanguage=The language is generally accomplishment-driven, though it's important to avoid vague phrases like 'driving best practices'. Specify particular initiatives and outcomes instead.}, crispness={feedback=The resume's length is mostly appropriate but could be condensed by reducing excessive detail. Streamlining word choice would improve the overall impact., resumeLength=The overall length is fitting for a person with over nine years of experience. Yet, it can be optimized to remove less relevant details for more focused content., score=56, bulletPointsCount=There is a significant use of bullet points, which is good, yet some sections have an overwhelming quantity. Reducing the number of bullet points to highlight only the most crucial achievements could be beneficial., fillerWords=Filler words are not prevalent, but the resume could benefit from more direct language. Eliminating any passive or redundant phrases is recommended for a crisper read., bulletPointLength=Some bullet points are unreasonably long, reducing effectiveness. Aim to shorten them to one to two lines for better clarity and impact., scale=100}, qualityAddOn={feedback=The resume employs some industry jargon effectively but should minimize clichés to enhance clarity. Improved formatting of sections would also enhance professional presentation., score=61, buzzwordsCliches=There is minimal use of buzzwords, but terms like 'scalable solutions' could be replaced with more specific examples. Avoiding jargon and specifying real achievements or technologies used will improve credibility., datesFormatting=Dates are consistently formatted across the document which adds to clarity. Ensure alignment of dates with text for a cleaner look., activeVoice=Active voice is predominantly used, lending a strong narrative to achievements. To enhance further, ensure all sections maintain this active, assertive tone., scale=100, personalPronounsUsage=The resume appropriately avoids the use of personal pronouns, maintaining a professional tone. Continue to use third-person impersonal statements for a formal presentation.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-11-02T06:52:04.967921, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-11-02 06:52:04, id=f52f8375-38c9-4e5e-9d7f-2593155d5d70, campaign_id=null, summary=null, error_message=null, rescheduled_at_str=null, agent_extraction=null, transfer_call_data=null, parsedAgentExtraction=null, smart_status=null, conversation_duration=0.0, usage_breakdown={transcriber_usage_breakdown={transcriber_duration=0, provider_connected=false}, transcriber_duration=0, transcriber_model=nova-3, synthesizer_characters=16, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=16}, transcriber_provider=deepgram, synthesizer_model=eleven_turbo_v2_5, llmModel={azure_gpt-4_1-mini={output=0, input=0}}, llmTokens=0, llm_usage_breakdown={analytics=null, summarization=null, extraction=null, conversation={output=0, input=0, provider_connected=false, provider=azure, model=azure/gpt-4.1-mini}, hangup=null}, synthesizer_provider=elevenlabs}, workflow_retries=null, rescheduled_at=null, scheduled_at_str=2025-11-02 06:51:27, status=busy}
{created_at_str=2025-11-02 06:51:27, agent_id=db818162-fabe-4ac8-8a6a-c61223150a70, total_cost=0.0, batch_id=null, cost_breakdown={synthesizer=0.0, transcriber=0, synthesizer_breakdown={welcome_message=0.0, conversation=0}, llm=0, platform=0, transcriber_breakdown={analytics=0, conversation=0}, network=0, llm_breakdown={analytics=0, summarization=0, extraction=0, conversation=0, hangup=0}}, created_at=2025-11-02T06:51:27.353221, scheduled_at=2025-11-02T06:51:27.353157, custom_extractions=null, telephony_data={duration=0.0, to_number=+919000140699, provider_call_id=5c6d4bfc-26be-43fb-9dff-f7d59074402e, hosted_telephony=false, recording_url=null, provider=plivo, hangup_provider_code=null, from_number=+918035316264, call_type=outbound, hangup_by=null, hangup_reason=null}, context_details={recipient_phone_number=+919000140699, recipient_data={recipient_phone_number=null, review_completed=2025-11-02 12:10:46, callback_request_id=null, is_callback=null, fullName=Siva, resume_review_id=6906fcb218c34103789121f3, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume has clearly sectioned areas like Profile, Skills, and Work Experience which improves readability. However, the inclusion of more headings with separators could enhance the overall layout., score=68, readability=The contact information at the top is concise, yet crowded, and could benefit from better spacing. The Skills section is detailed but might overwhelm the reader with a lack of hierarchy., essentialSectionsPresence=Key sections such as Work Experience and Education are present, but the Projects section isn't clearly demarcated which makes following the chronology hard. Adding project titles under the appropriate experience section could provide better clarity., scale=100}, atsReadabilityScore={feedback=Overall, the resume is fairly compatible with ATS parsing due to straightforward sectioning without complex formatting. Minor improvements could increase keyword frequency for better role alignment., score=65, scale=100, keyElementsReadableByATS=The name, employer, and role are clearly visible without any unnecessary stylization. However, integrating more relevant industry keywords related to Android development could boost ATS scores.}, impact={feedback=The resume demonstrates impactful achievements, yet many lack quantifiable metrics. Consistent use of strong, active verbs could strengthen the narrative around achievements., score=62, spellCheck=There are no blatant spelling errors, ensuring the content is professional. However, grammatical consistency in terms of tense and phrasing could be reviewed for improvement., bulletPointsUsage=The bullet points are used effectively, but some are overly lengthy, making them less impactful. Consider breaking longer points into concise actions and results., weakActionVerbs=Most actions are described using active verbs, but some points can be enhanced using more dynamic terminology. For example, replace 'developed' with 'engineered' or 'executed'., scale=100, quantifyingImpact=The resume includes some quantified achievements, such as reducing app crashes by 35%. Increasing the number of quantified metrics will highlight the candidate's true impact more effectively., repetitionAvoidance=There are limited repetitions of action verbs, yet diversity in verbs could further enhance engagement. Introducing variety in language can avoid reader fatigue., accomplishmentLanguage=The language is generally accomplishment-driven, though it's important to avoid vague phrases like 'driving best practices'. Specify particular initiatives and outcomes instead.}, crispness={feedback=The resume's length is mostly appropriate but could be condensed by reducing excessive detail. Streamlining word choice would improve the overall impact., resumeLength=The overall length is fitting for a person with over nine years of experience. Yet, it can be optimized to remove less relevant details for more focused content., score=56, bulletPointsCount=There is a significant use of bullet points, which is good, yet some sections have an overwhelming quantity. Reducing the number of bullet points to highlight only the most crucial achievements could be beneficial., fillerWords=Filler words are not prevalent, but the resume could benefit from more direct language. Eliminating any passive or redundant phrases is recommended for a crisper read., bulletPointLength=Some bullet points are unreasonably long, reducing effectiveness. Aim to shorten them to one to two lines for better clarity and impact., scale=100}, qualityAddOn={feedback=The resume employs some industry jargon effectively but should minimize clichés to enhance clarity. Improved formatting of sections would also enhance professional presentation., score=61, buzzwordsCliches=There is minimal use of buzzwords, but terms like 'scalable solutions' could be replaced with more specific examples. Avoiding jargon and specifying real achievements or technologies used will improve credibility., datesFormatting=Dates are consistently formatted across the document which adds to clarity. Ensure alignment of dates with text for a cleaner look., activeVoice=Active voice is predominantly used, lending a strong narrative to achievements. To enhance further, ensure all sections maintain this active, assertive tone., scale=100, personalPronounsUsage=The resume appropriately avoids the use of personal pronouns, maintaining a professional tone. Continue to use third-person impersonal statements for a formal presentation.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-11-02T06:51:32.840055, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-11-02 06:51:32, id=f52f8375-38c9-4e5e-9d7f-2593155d5d70, campaign_id=null, summary=null, error_message=null, rescheduled_at_str=null, agent_extraction=null, transfer_call_data=null, parsedAgentExtraction=null, smart_status=null, conversation_duration=0.0, usage_breakdown={transcriber_usage_breakdown={transcriber_duration=0, provider_connected=false}, transcriber_duration=0, transcriber_model=nova-3, synthesizer_characters=16, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=16}, transcriber_provider=deepgram, synthesizer_model=eleven_turbo_v2_5, llmModel={azure_gpt-4_1-mini={output=0, input=0}}, llmTokens=0, llm_usage_breakdown={analytics=null, summarization=null, extraction=null, conversation={output=0, input=0, provider_connected=false, provider=azure, model=azure/gpt-4.1-mini}, hangup=null}, synthesizer_provider=elevenlabs}, workflow_retries=null, rescheduled_at=null, scheduled_at_str=2025-11-02 06:51:27, status=ringing}
{created_at_str=2025-11-02 06:51:27, agent_id=db818162-fabe-4ac8-8a6a-c61223150a70, total_cost=0.0, batch_id=null, cost_breakdown={synthesizer=0.0, transcriber=0, synthesizer_breakdown={welcome_message=0.0, conversation=0}, llm=0, platform=0, transcriber_breakdown={analytics=0, conversation=0}, network=0, llm_breakdown={analytics=0, summarization=0, extraction=0, conversation=0, hangup=0}}, created_at=2025-11-02T06:51:27.353221, scheduled_at=2025-11-02T06:51:27.353157, custom_extractions=null, telephony_data={duration=0.0, to_number=+919000140699, provider_call_id=5c6d4bfc-26be-43fb-9dff-f7d59074402e, hosted_telephony=false, recording_url=null, provider=plivo, hangup_provider_code=null, from_number=+918035316264, call_type=outbound, hangup_by=null, hangup_reason=null}, context_details={recipient_phone_number=+919000140699, recipient_data={recipient_phone_number=null, review_completed=2025-11-02 12:10:46, callback_request_id=null, is_callback=null, fullName=Siva, resume_review_id=6906fcb218c34103789121f3, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume has clearly sectioned areas like Profile, Skills, and Work Experience which improves readability. However, the inclusion of more headings with separators could enhance the overall layout., score=68, readability=The contact information at the top is concise, yet crowded, and could benefit from better spacing. The Skills section is detailed but might overwhelm the reader with a lack of hierarchy., essentialSectionsPresence=Key sections such as Work Experience and Education are present, but the Projects section isn't clearly demarcated which makes following the chronology hard. Adding project titles under the appropriate experience section could provide better clarity., scale=100}, atsReadabilityScore={feedback=Overall, the resume is fairly compatible with ATS parsing due to straightforward sectioning without complex formatting. Minor improvements could increase keyword frequency for better role alignment., score=65, scale=100, keyElementsReadableByATS=The name, employer, and role are clearly visible without any unnecessary stylization. However, integrating more relevant industry keywords related to Android development could boost ATS scores.}, impact={feedback=The resume demonstrates impactful achievements, yet many lack quantifiable metrics. Consistent use of strong, active verbs could strengthen the narrative around achievements., score=62, spellCheck=There are no blatant spelling errors, ensuring the content is professional. However, grammatical consistency in terms of tense and phrasing could be reviewed for improvement., bulletPointsUsage=The bullet points are used effectively, but some are overly lengthy, making them less impactful. Consider breaking longer points into concise actions and results., weakActionVerbs=Most actions are described using active verbs, but some points can be enhanced using more dynamic terminology. For example, replace 'developed' with 'engineered' or 'executed'., scale=100, quantifyingImpact=The resume includes some quantified achievements, such as reducing app crashes by 35%. Increasing the number of quantified metrics will highlight the candidate's true impact more effectively., repetitionAvoidance=There are limited repetitions of action verbs, yet diversity in verbs could further enhance engagement. Introducing variety in language can avoid reader fatigue., accomplishmentLanguage=The language is generally accomplishment-driven, though it's important to avoid vague phrases like 'driving best practices'. Specify particular initiatives and outcomes instead.}, crispness={feedback=The resume's length is mostly appropriate but could be condensed by reducing excessive detail. Streamlining word choice would improve the overall impact., resumeLength=The overall length is fitting for a person with over nine years of experience. Yet, it can be optimized to remove less relevant details for more focused content., score=56, bulletPointsCount=There is a significant use of bullet points, which is good, yet some sections have an overwhelming quantity. Reducing the number of bullet points to highlight only the most crucial achievements could be beneficial., fillerWords=Filler words are not prevalent, but the resume could benefit from more direct language. Eliminating any passive or redundant phrases is recommended for a crisper read., bulletPointLength=Some bullet points are unreasonably long, reducing effectiveness. Aim to shorten them to one to two lines for better clarity and impact., scale=100}, qualityAddOn={feedback=The resume employs some industry jargon effectively but should minimize clichés to enhance clarity. Improved formatting of sections would also enhance professional presentation., score=61, buzzwordsCliches=There is minimal use of buzzwords, but terms like 'scalable solutions' could be replaced with more specific examples. Avoiding jargon and specifying real achievements or technologies used will improve credibility., datesFormatting=Dates are consistently formatted across the document which adds to clarity. Ensure alignment of dates with text for a cleaner look., activeVoice=Active voice is predominantly used, lending a strong narrative to achievements. To enhance further, ensure all sections maintain this active, assertive tone., scale=100, personalPronounsUsage=The resume appropriately avoids the use of personal pronouns, maintaining a professional tone. Continue to use third-person impersonal statements for a formal presentation.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-11-02T06:51:30.624666, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-11-02 06:51:30, id=f52f8375-38c9-4e5e-9d7f-2593155d5d70, campaign_id=null, summary=null, error_message=null, rescheduled_at_str=null, agent_extraction=null, transfer_call_data=null, parsedAgentExtraction=null, smart_status=null, conversation_duration=0.0, usage_breakdown={transcriber_usage_breakdown={transcriber_duration=0, provider_connected=false}, transcriber_duration=0, transcriber_model=nova-3, synthesizer_characters=16, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=16}, transcriber_provider=deepgram, synthesizer_model=eleven_turbo_v2_5, llmModel={azure_gpt-4_1-mini={output=0, input=0}}, llmTokens=0, llm_usage_breakdown={analytics=null, summarization=null, extraction=null, conversation={output=0, input=0, provider_connected=false, provider=azure, model=azure/gpt-4.1-mini}, hangup=null}, synthesizer_provider=elevenlabs}, workflow_retries=null, rescheduled_at=null, scheduled_at_str=2025-11-02 06:51:27, status=initiated}