TA

Tashu

46.0% Critical

📞 1 calls analyzed · 100 point scale · 4 categories · 15 parameters

🔑 Captured Identifiers & Reference Numbers

AI-extracted from conversation — the final confirmed value after all corrections, not just the first mention.

📞 tashu.mp3 46.0%
EaseMyTrip Booking ID medium

EMP161388972

💡 Customer said 'Nine seven two'; agent repeated '970' at the end, creating a mismatch.

Customer email high

nitinbudeja@gmail.com

💡 Spelled out by customer.

Customer contact number high

9793996580

💡 Provided once.

Avg Score

46.0%

Resolution Rate

0.0%

Total Calls

1

Category Scores (Averages)

🎙️ Opening & Verification (15 pts) 100.0%
💬 Communication & Professionalism (25 pts) 60.0%
🎯 Resolution & Knowledge (40 pts) 25.0%
⭐ Value Creation & Closure (20 pts) 30.0%

Individual Calls

tashu.mp3

refund · partial · 4 mins 30 secs

46.0% View →

🎙️ Opening & Verification

💬 Communication & Professionalism

🎯 Resolution & Knowledge

⭐ Value Creation & Closure

🚨 Red Flags

major Refund pending for ~1.5 months with no concrete tracking/reference shared on call

📁 tashu.mp3 · 🕐 [02:00]-[04:10] · Impact: Customer left without actionable proof or traceability; high repeat-call risk.

major Confusing/possibly incorrect technical explanation ('credit card is not on this BharatPe network')

📁 tashu.mp3 · 🕐 [02:40]-[03:15] · Impact: Reduced trust and clarity; customer could not understand the reason for delay.

minor Potential booking ID digit mismatch (customer said 972; agent repeated 970)

📁 tashu.mp3 · 🕐 [00:55] · Impact: Risk of wrong-case mapping or delayed resolution.

💡 Recommendations

Alternative Solutions Offered medium

Customer offered bank details for direct refund; agent missed a chance to guide the correct process (if supported) or explain why it’s not possible.

📁 tashu.mp3

❌ What happened

[03:10] “if you require my bank details… you can deposit the amount in my bank account also.”

✅ Better approach

Confirm whether manual NEFT is possible; if not, clearly explain refunds must go to original payment method and provide next best option (escalation + tracking).

💬 Example script

"“Refunds are processed only to the original card as per policy. I can’t take bank details for this, but I will raise an escalation with case ID ____ and share the ARN once generated.”"
Product & Policy Knowledge high

Incorrect/unclear payment gateway explanations create confusion and reduce credibility.

📁 tashu.mp3

❌ What happened

[02:55] “the credit card is not on this BharatPe network”

✅ Better approach

Avoid speculative technical claims; stick to verified status from tools and explain standard refund flow for failed transactions.

💬 Example script

"“This appears as a failed/ pending transaction from the payment gateway. In such cases, the bank reverses it automatically. Let me confirm whether EMT has initiated a refund or if it’s an auto-reversal, and I’ll share the exact reference.”"
Fee Transparency high

Customer needs concrete refund traceability (amount + reference) especially after long delay; otherwise the call cannot reassure or resolve.

📁 tashu.mp3

❌ What happened

[02:00] “you need to wait for your refund… it is an issue of the payment gateway… you need to wait 24 to 48 hours”

✅ Better approach

Share refund amount, refund mode, and tracking reference (ARN/UTR) or clearly state 'not initiated yet' with a committed SLA and case ID.

💬 Example script

"“I’ve checked your booking EMP… The refund amount is ₹X. It is/ is not initiated yet. If initiated, the ARN/UTR is ____ and it should reflect within __ working days. I’m also creating case ID ____ and you’ll receive an email confirmation now.”"

💪 Key Strengths

Correctly captured the issue type (failed booking with deducted amount) and proceeded to verification.
Used hold with permission and returned to the customer.

📞 tashu.mp3

refund · 4 mins 30 secs · 46.0%