Dashboard

{created_at_str=2025-10-15 12:33:39, agent_id=db818162-fabe-4ac8-8a6a-c61223150a70, total_cost=1.96, batch_id=null, cost_breakdown={synthesizer=1.77, transcriber=0.153, synthesizer_breakdown={welcome_message=0.0, conversation=1.77}, llm=0.041, platform=0, transcriber_breakdown={analytics=0, conversation=0.153}, network=0, llm_breakdown={analytics=0, summarization=0.003, extraction=0, conversation=0.006, hangup=0.032}}, created_at=2025-10-15T12:33:39.912465, scheduled_at=2025-10-15T12:33:39.912431, custom_extractions=null, telephony_data={duration=0.0, to_number=+918465070799, provider_call_id=fbc47933-cd0f-4e47-8e9d-7b4d705a6dd0, hosted_telephony=false, recording_url=, provider=plivo, hangup_provider_code=null, from_number=+918035316264, call_type=outbound, hangup_by=null, hangup_reason=null}, context_details={recipient_phone_number=+918465070799, recipient_data={recipient_phone_number=null, review_completed=2025-10-15 17:53:21, callback_request_id=null, is_callback=null, fullName=JEEVA, resume_review_id=68ef92109f941c720e711d8a, reviewDetails={overallScore={score=57.6, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume contains essential sections such as Summary, Experience, and Education, but these could be better organized to ensure readability. Reorganizing the Experience section in reverse chronological order would emphasize recent roles more effectively., score=65, readability=Although the resume is generally readable, some sections are densely packed and may overwhelm the reader. Breaking information into digestible parts would improve readability significantly., essentialSectionsPresence=The presence of essential sections like Summary, Experience, and Education is noted, however, the chronological order in the Experience section should begin with the most recent position to showcase the latest achievements. Including skills and achievements in a separate section could also add value., scale=100}, atsReadabilityScore={feedback=The resume is relatively ATS-friendly but could use more keywords relevant to the front-end development field. Proper section headers and a lack of tables help maintain ATS compatibility., score=60, scale=100, keyElementsReadableByATS=Most key elements such as names, titles, and dates are well-structured for ATS parsing. However, incorporating industry-specific keywords would improve ATS searchability and ranking.}, impact={feedback=Impact is conveyed somewhat through the use of bullet points, though more quantifiable achievements would enhance clarity. The language used lacks dynamism and could benefit from stronger action verbs., score=58, spellCheck=No spelling errors were detected, which contributes positively to the professionalism of the document., bulletPointsUsage=Bullet points are used throughout but can be more effectively structured to highlight accomplishments. Consider starting each bullet with a strong action verb for better impact., weakActionVerbs=The current version relies on weaker verbs, which dilute the impact of job descriptions. Replacing them with stronger verbs could enhance the perception of competency., scale=100, quantifyingImpact=The resume would benefit from quantified achievements, such as improving system efficiency or other KPIs. Currently, there's a lack of specific, measurable outcomes that could demonstrate the scope of past responsibilities., repetitionAvoidance=There is some repetition of duties across different roles without highlighting unique achievements for each position. This undermines the overall dynamism of the resume., accomplishmentLanguage=There is an opportunity to infuse more accomplishment-oriented language to demonstrate the impact and contributions made in past roles. Currently, descriptions lean towards task-oriented rather than results-oriented narratives.}, crispness={feedback=The resume is slightly verbose and could be more concise, particularly within the bullet points section. Reducing filler words and focusing on key accomplishments would improve its crispness., resumeLength=The resume's length is somewhat justified by the candidate's experience, but further tightening could improve its impact. Streamlining content to one page would enhance readability., score=50, bulletPointsCount=There's a decent number of bullet points, but they aren’t always concise or impactful. Refining these to highlight key achievements would elevate the overall quality., fillerWords=There are several filler words and fluff that detract from the main message. Eliminating unnecessary words and focusing on direct language would improve clarity., bulletPointLength=Some bullet points are overly lengthy, resulting in diluted impact. Shortening these while focusing on substantive achievements could significantly enhance crispness., scale=100}, qualityAddOn={feedback=The resume suffers from common stylistic missteps such as the use of clichés and inconsistent date formatting. Addressing these areas could significantly boost the professionalism of the document., score=55, buzzwordsCliches=There are instances of clichés like 'team player' that should be replaced with more specific skills or accomplishments. This would eliminate generalizations and enhance the resume's impact., datesFormatting=Dates are inconsistently formatted, which can confuse readers and ATS systems alike. Consistency in date formatting is critical for clarity and professionalism., activeVoice=The active voice is employed well in many sections, though not consistently. Ensuring all statements are in active voice could improve clarity and engagement., scale=100, personalPronounsUsage=The resume appropriately avoids personal pronouns, maintaining a professional tone throughout the document.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=assistant: Hi is that JEEVA?
user:  hi
assistant: rt of Times- of- India Group.
, updated_at=2025-10-15T12:34:11.945446, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-15 12:34:11, id=bc39e5f1-3bc2-4cca-b513-3b79d9ac206b, campaign_id=null, summary=The conversation begins with the agent greeting the user, confirming their identity as JEEVA. The user responds with a simple "hi." The agent then mentions their affiliation with the Times of India Group, but the context of the conversation is not fully established in the provided transcript., error_message=null, rescheduled_at_str=null, agent_extraction=null, transfer_call_data=null, parsedAgentExtraction=null, smart_status=null, conversation_duration=10.1, usage_breakdown={transcriber_usage_breakdown={transcriber_duration=9.999937, provider_connected=false}, transcriber_duration=9.999937, transcriber_model=nova-3, synthesizer_characters=194, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=177, welcome_message_cache=false, welcome_message_characters=17}, transcriber_provider=deepgram, synthesizer_model=eleven_turbo_v2_5, llmModel={gpt-4o-mini={output=55, input=25}, azure_gpt-4_1-mini={output=40, input=0}}, llmTokens=0, llm_usage_breakdown={analytics=null, summarization={output=55, input=25, provider_connected=false, provider=azure, model=gpt-4o-mini}, extraction=null, conversation={output=40, input=0, provider_connected=false, provider=azure, model=azure/gpt-4.1-mini}, hangup={output=7, input=2128, provider_connected=false, provider=openai, model=gpt-4o-mini}}, synthesizer_provider=elevenlabs}, workflow_retries=null, rescheduled_at=null, scheduled_at_str=2025-10-15 12:33:39, status=call-disconnected}

{created_at_str=2025-10-15 12:33:39, 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-10-15T12:33:39.912465, scheduled_at=2025-10-15T12:33:39.912431, custom_extractions=null, telephony_data={duration=0.0, to_number=+918465070799, provider_call_id=fbc47933-cd0f-4e47-8e9d-7b4d705a6dd0, 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=+918465070799, recipient_data={recipient_phone_number=null, review_completed=2025-10-15 17:53:21, callback_request_id=null, is_callback=null, fullName=JEEVA, resume_review_id=68ef92109f941c720e711d8a, reviewDetails={overallScore={score=57.6, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume contains essential sections such as Summary, Experience, and Education, but these could be better organized to ensure readability. Reorganizing the Experience section in reverse chronological order would emphasize recent roles more effectively., score=65, readability=Although the resume is generally readable, some sections are densely packed and may overwhelm the reader. Breaking information into digestible parts would improve readability significantly., essentialSectionsPresence=The presence of essential sections like Summary, Experience, and Education is noted, however, the chronological order in the Experience section should begin with the most recent position to showcase the latest achievements. Including skills and achievements in a separate section could also add value., scale=100}, atsReadabilityScore={feedback=The resume is relatively ATS-friendly but could use more keywords relevant to the front-end development field. Proper section headers and a lack of tables help maintain ATS compatibility., score=60, scale=100, keyElementsReadableByATS=Most key elements such as names, titles, and dates are well-structured for ATS parsing. However, incorporating industry-specific keywords would improve ATS searchability and ranking.}, impact={feedback=Impact is conveyed somewhat through the use of bullet points, though more quantifiable achievements would enhance clarity. The language used lacks dynamism and could benefit from stronger action verbs., score=58, spellCheck=No spelling errors were detected, which contributes positively to the professionalism of the document., bulletPointsUsage=Bullet points are used throughout but can be more effectively structured to highlight accomplishments. Consider starting each bullet with a strong action verb for better impact., weakActionVerbs=The current version relies on weaker verbs, which dilute the impact of job descriptions. Replacing them with stronger verbs could enhance the perception of competency., scale=100, quantifyingImpact=The resume would benefit from quantified achievements, such as improving system efficiency or other KPIs. Currently, there's a lack of specific, measurable outcomes that could demonstrate the scope of past responsibilities., repetitionAvoidance=There is some repetition of duties across different roles without highlighting unique achievements for each position. This undermines the overall dynamism of the resume., accomplishmentLanguage=There is an opportunity to infuse more accomplishment-oriented language to demonstrate the impact and contributions made in past roles. Currently, descriptions lean towards task-oriented rather than results-oriented narratives.}, crispness={feedback=The resume is slightly verbose and could be more concise, particularly within the bullet points section. Reducing filler words and focusing on key accomplishments would improve its crispness., resumeLength=The resume's length is somewhat justified by the candidate's experience, but further tightening could improve its impact. Streamlining content to one page would enhance readability., score=50, bulletPointsCount=There's a decent number of bullet points, but they aren’t always concise or impactful. Refining these to highlight key achievements would elevate the overall quality., fillerWords=There are several filler words and fluff that detract from the main message. Eliminating unnecessary words and focusing on direct language would improve clarity., bulletPointLength=Some bullet points are overly lengthy, resulting in diluted impact. Shortening these while focusing on substantive achievements could significantly enhance crispness., scale=100}, qualityAddOn={feedback=The resume suffers from common stylistic missteps such as the use of clichés and inconsistent date formatting. Addressing these areas could significantly boost the professionalism of the document., score=55, buzzwordsCliches=There are instances of clichés like 'team player' that should be replaced with more specific skills or accomplishments. This would eliminate generalizations and enhance the resume's impact., datesFormatting=Dates are inconsistently formatted, which can confuse readers and ATS systems alike. Consistency in date formatting is critical for clarity and professionalism., activeVoice=The active voice is employed well in many sections, though not consistently. Ensuring all statements are in active voice could improve clarity and engagement., scale=100, personalPronounsUsage=The resume appropriately avoids personal pronouns, maintaining a professional tone throughout the document.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-15T12:33:52.361432, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-15 12:33:52, id=bc39e5f1-3bc2-4cca-b513-3b79d9ac206b, 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=17, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=17}, 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-15 12:33:39, status=in-progress}

{created_at_str=2025-10-15 12:33:39, 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-10-15T12:33:39.912465, scheduled_at=2025-10-15T12:33:39.912431, custom_extractions=null, telephony_data={duration=0.0, to_number=+918465070799, provider_call_id=fbc47933-cd0f-4e47-8e9d-7b4d705a6dd0, 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=+918465070799, recipient_data={recipient_phone_number=null, review_completed=2025-10-15 17:53:21, callback_request_id=null, is_callback=null, fullName=JEEVA, resume_review_id=68ef92109f941c720e711d8a, reviewDetails={overallScore={score=57.6, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume contains essential sections such as Summary, Experience, and Education, but these could be better organized to ensure readability. Reorganizing the Experience section in reverse chronological order would emphasize recent roles more effectively., score=65, readability=Although the resume is generally readable, some sections are densely packed and may overwhelm the reader. Breaking information into digestible parts would improve readability significantly., essentialSectionsPresence=The presence of essential sections like Summary, Experience, and Education is noted, however, the chronological order in the Experience section should begin with the most recent position to showcase the latest achievements. Including skills and achievements in a separate section could also add value., scale=100}, atsReadabilityScore={feedback=The resume is relatively ATS-friendly but could use more keywords relevant to the front-end development field. Proper section headers and a lack of tables help maintain ATS compatibility., score=60, scale=100, keyElementsReadableByATS=Most key elements such as names, titles, and dates are well-structured for ATS parsing. However, incorporating industry-specific keywords would improve ATS searchability and ranking.}, impact={feedback=Impact is conveyed somewhat through the use of bullet points, though more quantifiable achievements would enhance clarity. The language used lacks dynamism and could benefit from stronger action verbs., score=58, spellCheck=No spelling errors were detected, which contributes positively to the professionalism of the document., bulletPointsUsage=Bullet points are used throughout but can be more effectively structured to highlight accomplishments. Consider starting each bullet with a strong action verb for better impact., weakActionVerbs=The current version relies on weaker verbs, which dilute the impact of job descriptions. Replacing them with stronger verbs could enhance the perception of competency., scale=100, quantifyingImpact=The resume would benefit from quantified achievements, such as improving system efficiency or other KPIs. Currently, there's a lack of specific, measurable outcomes that could demonstrate the scope of past responsibilities., repetitionAvoidance=There is some repetition of duties across different roles without highlighting unique achievements for each position. This undermines the overall dynamism of the resume., accomplishmentLanguage=There is an opportunity to infuse more accomplishment-oriented language to demonstrate the impact and contributions made in past roles. Currently, descriptions lean towards task-oriented rather than results-oriented narratives.}, crispness={feedback=The resume is slightly verbose and could be more concise, particularly within the bullet points section. Reducing filler words and focusing on key accomplishments would improve its crispness., resumeLength=The resume's length is somewhat justified by the candidate's experience, but further tightening could improve its impact. Streamlining content to one page would enhance readability., score=50, bulletPointsCount=There's a decent number of bullet points, but they aren’t always concise or impactful. Refining these to highlight key achievements would elevate the overall quality., fillerWords=There are several filler words and fluff that detract from the main message. Eliminating unnecessary words and focusing on direct language would improve clarity., bulletPointLength=Some bullet points are overly lengthy, resulting in diluted impact. Shortening these while focusing on substantive achievements could significantly enhance crispness., scale=100}, qualityAddOn={feedback=The resume suffers from common stylistic missteps such as the use of clichés and inconsistent date formatting. Addressing these areas could significantly boost the professionalism of the document., score=55, buzzwordsCliches=There are instances of clichés like 'team player' that should be replaced with more specific skills or accomplishments. This would eliminate generalizations and enhance the resume's impact., datesFormatting=Dates are inconsistently formatted, which can confuse readers and ATS systems alike. Consistency in date formatting is critical for clarity and professionalism., activeVoice=The active voice is employed well in many sections, though not consistently. Ensuring all statements are in active voice could improve clarity and engagement., scale=100, personalPronounsUsage=The resume appropriately avoids personal pronouns, maintaining a professional tone throughout the document.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-15T12:33:44.092905, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-15 12:33:44, id=bc39e5f1-3bc2-4cca-b513-3b79d9ac206b, 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=17, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=17}, 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-15 12:33:39, status=ringing}

{created_at_str=2025-10-15 12:33:39, 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-10-15T12:33:39.912465, scheduled_at=2025-10-15T12:33:39.912431, custom_extractions=null, telephony_data={duration=0.0, to_number=+918465070799, provider_call_id=fbc47933-cd0f-4e47-8e9d-7b4d705a6dd0, 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=+918465070799, recipient_data={recipient_phone_number=null, review_completed=2025-10-15 17:53:21, callback_request_id=null, is_callback=null, fullName=JEEVA, resume_review_id=68ef92109f941c720e711d8a, reviewDetails={overallScore={score=57.6, scale=100}, detailedFeedback={layoutAndSearchability={feedback=The resume contains essential sections such as Summary, Experience, and Education, but these could be better organized to ensure readability. Reorganizing the Experience section in reverse chronological order would emphasize recent roles more effectively., score=65, readability=Although the resume is generally readable, some sections are densely packed and may overwhelm the reader. Breaking information into digestible parts would improve readability significantly., essentialSectionsPresence=The presence of essential sections like Summary, Experience, and Education is noted, however, the chronological order in the Experience section should begin with the most recent position to showcase the latest achievements. Including skills and achievements in a separate section could also add value., scale=100}, atsReadabilityScore={feedback=The resume is relatively ATS-friendly but could use more keywords relevant to the front-end development field. Proper section headers and a lack of tables help maintain ATS compatibility., score=60, scale=100, keyElementsReadableByATS=Most key elements such as names, titles, and dates are well-structured for ATS parsing. However, incorporating industry-specific keywords would improve ATS searchability and ranking.}, impact={feedback=Impact is conveyed somewhat through the use of bullet points, though more quantifiable achievements would enhance clarity. The language used lacks dynamism and could benefit from stronger action verbs., score=58, spellCheck=No spelling errors were detected, which contributes positively to the professionalism of the document., bulletPointsUsage=Bullet points are used throughout but can be more effectively structured to highlight accomplishments. Consider starting each bullet with a strong action verb for better impact., weakActionVerbs=The current version relies on weaker verbs, which dilute the impact of job descriptions. Replacing them with stronger verbs could enhance the perception of competency., scale=100, quantifyingImpact=The resume would benefit from quantified achievements, such as improving system efficiency or other KPIs. Currently, there's a lack of specific, measurable outcomes that could demonstrate the scope of past responsibilities., repetitionAvoidance=There is some repetition of duties across different roles without highlighting unique achievements for each position. This undermines the overall dynamism of the resume., accomplishmentLanguage=There is an opportunity to infuse more accomplishment-oriented language to demonstrate the impact and contributions made in past roles. Currently, descriptions lean towards task-oriented rather than results-oriented narratives.}, crispness={feedback=The resume is slightly verbose and could be more concise, particularly within the bullet points section. Reducing filler words and focusing on key accomplishments would improve its crispness., resumeLength=The resume's length is somewhat justified by the candidate's experience, but further tightening could improve its impact. Streamlining content to one page would enhance readability., score=50, bulletPointsCount=There's a decent number of bullet points, but they aren’t always concise or impactful. Refining these to highlight key achievements would elevate the overall quality., fillerWords=There are several filler words and fluff that detract from the main message. Eliminating unnecessary words and focusing on direct language would improve clarity., bulletPointLength=Some bullet points are overly lengthy, resulting in diluted impact. Shortening these while focusing on substantive achievements could significantly enhance crispness., scale=100}, qualityAddOn={feedback=The resume suffers from common stylistic missteps such as the use of clichés and inconsistent date formatting. Addressing these areas could significantly boost the professionalism of the document., score=55, buzzwordsCliches=There are instances of clichés like 'team player' that should be replaced with more specific skills or accomplishments. This would eliminate generalizations and enhance the resume's impact., datesFormatting=Dates are inconsistently formatted, which can confuse readers and ATS systems alike. Consistency in date formatting is critical for clarity and professionalism., activeVoice=The active voice is employed well in many sections, though not consistently. Ensuring all statements are in active voice could improve clarity and engagement., scale=100, personalPronounsUsage=The resume appropriately avoids personal pronouns, maintaining a professional tone throughout the document.}}}, parentBolnaId=null, attemptType=null}, resume_review_id=null}, extracted_data=null, arq_job_id=null, transcript=null, updated_at=2025-10-15T12:33:41.265378, answered_by_voice_mail=null, batch_run_details=null, provider=plivo, updated_at_str=2025-10-15 12:33:41, id=bc39e5f1-3bc2-4cca-b513-3b79d9ac206b, 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=17, synthesizer_usage_breakdown={provider_connected=false, conversation_characters=0, welcome_message_cache=false, welcome_message_characters=17}, 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-15 12:33:39, status=initiated}