Call Details

Bolna ID: 78598065-30aa-4a58-a893-7cf1f8fdb614

Phone: +918497050043

From: +918035316264

Status: no-answer

Processing: RETRY_NEEDED

Duration: N/A

Cost: N/A

Hangup Details

Hangup By: Carrier

Reason: Call recipient rejected

Timestamps

Started:
2025-10-06 18:26:27

Ended:
Not set

Last Processed:
2025-10-06 18:27:20

Last Retry At:
2025-10-06 18:27:20

Next Retry Scheduled:
2025-10-06 18:37:20

Next Call Scheduled:
2025-10-06 18:37:20

Retry Information

Attempts: 0

Next Retry: Not scheduled

Call Timeline 6
2025-10-06 18:26:29
CALLBACK_INITIATED MAIN
CALL_SERVICE
₹0.00
Duration: 0.00s
2025-10-06 18:26:34
INITIATED MAIN
CALLBACK_UPDATE
₹0.00
Duration: 0.00s
2025-10-06 18:26:35
RINGING MAIN
CALLBACK_UPDATE
₹0.00
Duration: 0.00s
2025-10-06 18:27:20
NO_ANSWER MAIN
CALLBACK_UPDATE
₹0.00
Duration: 0.00s
2025-10-06 18:27:20
NO_ANSWER_CHECK MAIN
RETRY_POLICY
₹0.00
Duration: 0.00s
Metadata: {createdAtStr=2025-10-06 18:27:20}
2025-10-06 18:27:20
RETRY_SCHEDULED MAIN
RETRY_POLICY
₹0.00
Duration: 0.00s
Metadata: {attempt_reason=no_answer, scheduled_for=2025-10-06T18:37:20.512964397}
Call History (Raw Callbacks) 3

{created_at_str=2025-10-06 12:56:29, agent_id=2fefba9f-c4bd-492b-8ccf-d72da990f4f0, 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-10-06T12:56:29.468149, scheduled_at=2025-10-06T12:56:29.468121, custom_extractions=null, telephony_data={duration=0.0, to_number=+918497050043, provider_call_id=0a3da12a-83ec-48c2-aadd-c58069da2f14, hosted_telephony=false, recording_url=null, provider=plivo, hangup_provider_code=3020, from_number=+918035316264, call_type=outbound, hangup_by=Carrier, hangup_reason=Call recipient rejected}, context_details={recipient_phone_number=+918497050043, recipient_data={recipient_phone_number=null, review_completed=2025-10-06 18:16:00, callback_request_id=null, is_callback=null, fullName=SHEETAL, resume_review_id=68e3b9c89f941c720e6f4791, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The layout is generally neat but lacks sectional distinction, making it slightly less readable. Including section headers with bold fonts could improve navigation., score=65, readability=The resume text is fairly readable, though some sections feel dense. Breaking down long paragraphs into succinct points would enhance skimmability., essentialSectionsPresence=All critical sections like Experience, Education, and Skills are present, providing a comprehensive professional overview. However, the hobbies section seems unnecessary and could be omitted., scale=100}, atsReadabilityScore={feedback=The resume is ATS-friendly, covering primary keywords relevant to the Service Desk Administrator role. However, explicit section labels would ensure more seamless ATS parsing., score=65, scale=100, keyElementsReadableByATS=Key information such as name, contact, and employment details are clearly presented, aiding ATS readability. Enhancing keyword density in technical areas may further improve results.}, impact={feedback=The usage of bullet points improves clarity, but more quantifiable achievements would enhance impact. Frequent repetition of verbs reduces the dynamic quality of the narrative., score=59, spellCheck=The resume appears to be free of spelling mistakes, which shows attention to detail. Regular proofreads or tools like Grammarly can ensure consistent quality., bulletPointsUsage=Bullet points are used effectively to list skills and responsibilities, but not consistently across all sections. A more uniform approach to bullet points would be beneficial., weakActionVerbs=Weak verbs like 'responsible for' appear frequently, lowering sentence impact. Replacing these with power verbs like 'spearheaded' or 'enhanced' would strengthen statements., scale=100, quantifyingImpact=Several impacts are quantified, such as 'SLA breach reduced by 15%', which is excellent. Expanding this to more achievements could further highlight the candidate’s contributions., repetitionAvoidance=There is noticeable repetition of technical skills and tasks across roles. Revise to focus on diverse skills and unique accomplishments in each role to avoid monotony., accomplishmentLanguage=Accomplishments are described with a moderate sense of results-driven language. However, more emphasis on outcomes in each role could amplify effectiveness.}, crispness={feedback=The resume is moderately crisp but could be more so by pare down descriptions. Over-reliance on lengthy bullet points and some filler words detracts from conciseness., resumeLength=The length of the resume suits the candidate's experience, maintaining a balanced detail level. Yet, trimming bloated sections could enhance focus and readability., score=60, bulletPointsCount=There is a good count of bullet points, offering a structured view of achievements. Cutting down on less relevant points would ensure only key highlights are displayed., fillerWords=Filler phrases appear occasionally, reducing the resume’s directness. Removing vague language like 'responsible for' would sharpen the overall narrative., bulletPointLength=Some bullet points are excessively long, impacting clarity. Shortening these to essential facts or splitting them into sub-points would improve comprehension., scale=100}, qualityAddOn={feedback=The use of buzzwords is minimal but apparent, aligning well within industry norms. However, a sharper focus on active voice throughout the resume could enhance the tone., score=63, buzzwordsCliches=The resume uses relevant buzzwords, but steering clear of clichés like 'highly motivated’ would provide clearer examples of abilities. Specific credentials can underscore qualifications., datesFormatting=Dates are formatted consistently, which is effective for quick reading. However, aligning all dates to a single style (e.g., MM/YYYY) would standardize entries better., activeVoice=There is a general use of the active voice, although some sections revert to passive constructs. Revising sentences to prioritize direct actions should be a goal for enhancing expression., scale=100, personalPronounsUsage=There is no use of personal pronouns, which is appropriate for resume context. This maintains a professional tone and aligns with industry standards.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-06T12:57:19.658689, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-06 12:57:19, id=78598065-30aa-4a58-a893-7cf1f8fdb614, 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=19, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=19}, 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-10-06 12:56:29, status=no-answer}

{created_at_str=2025-10-06 12:56:29, agent_id=2fefba9f-c4bd-492b-8ccf-d72da990f4f0, 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-10-06T12:56:29.468149, scheduled_at=2025-10-06T12:56:29.468121, custom_extractions=null, telephony_data={duration=0.0, to_number=+918497050043, provider_call_id=0a3da12a-83ec-48c2-aadd-c58069da2f14, 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=+918497050043, recipient_data={recipient_phone_number=null, review_completed=2025-10-06 18:16:00, callback_request_id=null, is_callback=null, fullName=SHEETAL, resume_review_id=68e3b9c89f941c720e6f4791, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The layout is generally neat but lacks sectional distinction, making it slightly less readable. Including section headers with bold fonts could improve navigation., score=65, readability=The resume text is fairly readable, though some sections feel dense. Breaking down long paragraphs into succinct points would enhance skimmability., essentialSectionsPresence=All critical sections like Experience, Education, and Skills are present, providing a comprehensive professional overview. However, the hobbies section seems unnecessary and could be omitted., scale=100}, atsReadabilityScore={feedback=The resume is ATS-friendly, covering primary keywords relevant to the Service Desk Administrator role. However, explicit section labels would ensure more seamless ATS parsing., score=65, scale=100, keyElementsReadableByATS=Key information such as name, contact, and employment details are clearly presented, aiding ATS readability. Enhancing keyword density in technical areas may further improve results.}, impact={feedback=The usage of bullet points improves clarity, but more quantifiable achievements would enhance impact. Frequent repetition of verbs reduces the dynamic quality of the narrative., score=59, spellCheck=The resume appears to be free of spelling mistakes, which shows attention to detail. Regular proofreads or tools like Grammarly can ensure consistent quality., bulletPointsUsage=Bullet points are used effectively to list skills and responsibilities, but not consistently across all sections. A more uniform approach to bullet points would be beneficial., weakActionVerbs=Weak verbs like 'responsible for' appear frequently, lowering sentence impact. Replacing these with power verbs like 'spearheaded' or 'enhanced' would strengthen statements., scale=100, quantifyingImpact=Several impacts are quantified, such as 'SLA breach reduced by 15%', which is excellent. Expanding this to more achievements could further highlight the candidate’s contributions., repetitionAvoidance=There is noticeable repetition of technical skills and tasks across roles. Revise to focus on diverse skills and unique accomplishments in each role to avoid monotony., accomplishmentLanguage=Accomplishments are described with a moderate sense of results-driven language. However, more emphasis on outcomes in each role could amplify effectiveness.}, crispness={feedback=The resume is moderately crisp but could be more so by pare down descriptions. Over-reliance on lengthy bullet points and some filler words detracts from conciseness., resumeLength=The length of the resume suits the candidate's experience, maintaining a balanced detail level. Yet, trimming bloated sections could enhance focus and readability., score=60, bulletPointsCount=There is a good count of bullet points, offering a structured view of achievements. Cutting down on less relevant points would ensure only key highlights are displayed., fillerWords=Filler phrases appear occasionally, reducing the resume’s directness. Removing vague language like 'responsible for' would sharpen the overall narrative., bulletPointLength=Some bullet points are excessively long, impacting clarity. Shortening these to essential facts or splitting them into sub-points would improve comprehension., scale=100}, qualityAddOn={feedback=The use of buzzwords is minimal but apparent, aligning well within industry norms. However, a sharper focus on active voice throughout the resume could enhance the tone., score=63, buzzwordsCliches=The resume uses relevant buzzwords, but steering clear of clichés like 'highly motivated’ would provide clearer examples of abilities. Specific credentials can underscore qualifications., datesFormatting=Dates are formatted consistently, which is effective for quick reading. However, aligning all dates to a single style (e.g., MM/YYYY) would standardize entries better., activeVoice=There is a general use of the active voice, although some sections revert to passive constructs. Revising sentences to prioritize direct actions should be a goal for enhancing expression., scale=100, personalPronounsUsage=There is no use of personal pronouns, which is appropriate for resume context. This maintains a professional tone and aligns with industry standards.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-06T12:56:34.703959, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-06 12:56:34, id=78598065-30aa-4a58-a893-7cf1f8fdb614, 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=19, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=19}, 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-10-06 12:56:29, status=ringing}

{created_at_str=2025-10-06 12:56:29, agent_id=2fefba9f-c4bd-492b-8ccf-d72da990f4f0, 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-10-06T12:56:29.468149, scheduled_at=2025-10-06T12:56:29.468121, custom_extractions=null, telephony_data={duration=0.0, to_number=+918497050043, provider_call_id=0a3da12a-83ec-48c2-aadd-c58069da2f14, 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=+918497050043, recipient_data={recipient_phone_number=null, review_completed=2025-10-06 18:16:00, callback_request_id=null, is_callback=null, fullName=SHEETAL, resume_review_id=68e3b9c89f941c720e6f4791, reviewDetails={overallScore={score=62.4, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The layout is generally neat but lacks sectional distinction, making it slightly less readable. Including section headers with bold fonts could improve navigation., score=65, readability=The resume text is fairly readable, though some sections feel dense. Breaking down long paragraphs into succinct points would enhance skimmability., essentialSectionsPresence=All critical sections like Experience, Education, and Skills are present, providing a comprehensive professional overview. However, the hobbies section seems unnecessary and could be omitted., scale=100}, atsReadabilityScore={feedback=The resume is ATS-friendly, covering primary keywords relevant to the Service Desk Administrator role. However, explicit section labels would ensure more seamless ATS parsing., score=65, scale=100, keyElementsReadableByATS=Key information such as name, contact, and employment details are clearly presented, aiding ATS readability. Enhancing keyword density in technical areas may further improve results.}, impact={feedback=The usage of bullet points improves clarity, but more quantifiable achievements would enhance impact. Frequent repetition of verbs reduces the dynamic quality of the narrative., score=59, spellCheck=The resume appears to be free of spelling mistakes, which shows attention to detail. Regular proofreads or tools like Grammarly can ensure consistent quality., bulletPointsUsage=Bullet points are used effectively to list skills and responsibilities, but not consistently across all sections. A more uniform approach to bullet points would be beneficial., weakActionVerbs=Weak verbs like 'responsible for' appear frequently, lowering sentence impact. Replacing these with power verbs like 'spearheaded' or 'enhanced' would strengthen statements., scale=100, quantifyingImpact=Several impacts are quantified, such as 'SLA breach reduced by 15%', which is excellent. Expanding this to more achievements could further highlight the candidate’s contributions., repetitionAvoidance=There is noticeable repetition of technical skills and tasks across roles. Revise to focus on diverse skills and unique accomplishments in each role to avoid monotony., accomplishmentLanguage=Accomplishments are described with a moderate sense of results-driven language. However, more emphasis on outcomes in each role could amplify effectiveness.}, crispness={feedback=The resume is moderately crisp but could be more so by pare down descriptions. Over-reliance on lengthy bullet points and some filler words detracts from conciseness., resumeLength=The length of the resume suits the candidate's experience, maintaining a balanced detail level. Yet, trimming bloated sections could enhance focus and readability., score=60, bulletPointsCount=There is a good count of bullet points, offering a structured view of achievements. Cutting down on less relevant points would ensure only key highlights are displayed., fillerWords=Filler phrases appear occasionally, reducing the resume’s directness. Removing vague language like 'responsible for' would sharpen the overall narrative., bulletPointLength=Some bullet points are excessively long, impacting clarity. Shortening these to essential facts or splitting them into sub-points would improve comprehension., scale=100}, qualityAddOn={feedback=The use of buzzwords is minimal but apparent, aligning well within industry norms. However, a sharper focus on active voice throughout the resume could enhance the tone., score=63, buzzwordsCliches=The resume uses relevant buzzwords, but steering clear of clichés like 'highly motivated’ would provide clearer examples of abilities. Specific credentials can underscore qualifications., datesFormatting=Dates are formatted consistently, which is effective for quick reading. However, aligning all dates to a single style (e.g., MM/YYYY) would standardize entries better., activeVoice=There is a general use of the active voice, although some sections revert to passive constructs. Revising sentences to prioritize direct actions should be a goal for enhancing expression., scale=100, personalPronounsUsage=There is no use of personal pronouns, which is appropriate for resume context. This maintains a professional tone and aligns with industry standards.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-06T12:56:33.459053, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-06 12:56:33, id=78598065-30aa-4a58-a893-7cf1f8fdb614, 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=19, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=19}, 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-10-06 12:56:29, status=initiated}