Kevin Rose · Jun 26, 2025 · 4:51 PM
Inbound · 04:17 · Planner: Anastasia Thomas · +17752246283
“I just went through this two weeks ago. It's been corrected but it doesn't look like it, at least not for me.”
Contact Kevin by July 1st with a manual reminder that his final payment is due July 3rd, and escalate to the tech team immediately to diagnose why the automatic 10-day notice is not triggering. Follow up with Don to confirm the coding issue is actually fixed before Kevin's next booking.
Full analysis
What happened
Kevin called to report a recurring billing notification problem with his Windstar cruise booked for October with a July 3rd final payment due. He received the final payment notification on the due date itself two weeks ago (June 17), despite Pavlus's stated 10-day notice policy. Don had emailed an apology citing an internal coding issue that had been 'corrected,' but Kevin has not received a notification for his upcoming July 3rd payment either—suggesting the fix didn't work. Anastasia acknowledged the pattern, agreed it sounds like a broader system issue, and committed to escalating to the tech team and following up with Don. The call ended with Kevin's concern noted but unresolved.
Emotional read
Kevin is frustrated and skeptical, speaking from experience as a repeat customer. He remains professional and measured throughout—not angry, but clearly exasperated that a claimed fix hasn't worked. He shows pragmatism (keeps detailed notes on bills) and mild concern for other customers who may be caught off-guard by surprise charges.
Emotional arc through the call
Kevin remained steady throughout—frustrated but measured—neither warming nor cooling. His skepticism about the 'correction' was validated by the agent's agreement that the problem likely persists system-wide.
How customer sees Pavlus
- negative · internal coding issue prevented payment notice from being properly routed and delivered within the intended timeframe, and this problem appears to persist despite a claimed fix
- negative · as a repeat customer, Kevin has 'dealt with you guys all the time' and expects reliable process; the recurring failure to deliver 10-day notice is out of standard for service
Process friction
- final payment notification email not delivered until the due date, rather than 10 days prior
- internal coding issue preventing proper routing and delivery of payment notices
- issue persists after customer reported it and received assurance that it was corrected
Value perception
Kevin is a repeat customer and maintains the relationship, but expresses frustration with reliability. He noted that unexpected large bills are 'quite a surprise' and he has to manage around Pavlus's process failures by keeping his own careful records.
Customer behaviors
reporting a recurring system failure affecting billing notificationsdocumenting payment due dates manually to avoid surprise chargesexpressing concern that issue may affect other customers broadlyfollowing up on a prior promise of resolution
Topics & signals
| Topics | final payment notification timingsystem coding issueemail delivery failureunexpected billing surprisecruise booking management |
|---|---|
| Cruise lines | Windstar |
| Objections | promised 10-day payment notice not being delivered consistentlyinternal coding issue still unresolved despite prior claim of correctionconcerned about unexpected large bills arriving without proper warning |
Analyzed 2026-05-27 17:32:23 by claude-haiku-4-5-20251001. Confidence 0.92.
Transcript (3,926 chars)
Agent (Anastasia Thomas): Ts travels, this is a station. Gusts how can I help you today? Customer: Yeah, this is Kevin rose, is don class sign in? I got an email from her. Agent (Anastasia Thomas): Oh, okay, I can see and while I'm looking, is there anything that I can help with? Customer: Yeah, you, I deal with you guys all the time. So, usually before a final payments due, you send me an email. Agent (Anastasia Thomas): Oh, okay, yeah. Customer: It last two weeks ago, I got the email on the day the final payment was due even though it said you would get a ten day notice. Customer: So don emailed me back and said we're sorry we've corrected the problem and I, and I haven't responded because I have a payment to July 3rd, which is like seven days away and I haven't got an email from talas saying your final payment to do and supposed to be ten days. Agent (Anastasia Thomas): Okay. Oh, dear, that sounds to me like the coding issue was still occurring then. Customer: Yeah. Customer: Is she yeah. Customer: She said, yup, he says we discovered an internal coding issue prevented your notice from being properly routed and delivered within the attended timeframe. This was not the standard for service at Ablis. In yada, yada, yada, and yada, yada, yada, this says this has been corrected but I don't think it's been corrected. Agent (Anastasia Thomas): No, I'm in, can to agree. So I'm looking at your bookings. Customer: Yeah, it's with WinStar and it's say cruise in October and the final payment is a due July 3rd. Agent (Anastasia Thomas): Okay. Customer: I just looked at my pales invoice. Unfortunately, I write these down because if not sometimes a big bill comes in. I can not expecting it. It's quite a surprise. Agent (Anastasia Thomas): Okay. Agent (Anastasia Thomas): Yeah, that's understandable. Customer: Yeah, cause I'm no money around. Agent (Anastasia Thomas): Okay. Agent (Anastasia Thomas): I see here. Okay, so this is what I'm going to do. Agent (Anastasia Thomas): I'm making some notes as we speak. Customer: Yeah. Agent (Anastasia Thomas): And just making sure that we're able to get in touch with our tech team on this, so that they can get this corrected. Customer: Yeah, cause I just went through this two weeks ago. Oh, no, see Friday the, no, June 17th. I can email from Ablis I'd be saying. Customer: Upcoming payment and I also got charge that day. Agent (Anastasia Thomas): Okay, yeah, that's. Customer: And that's when I send it, yeah, I'm send her an email she said it's been corrected but it doesn't look like, at least not for me. Agent (Anastasia Thomas): Okay, no, I, and I would imagine if it hasn't been corrected for you. It hasn't been corrected for anybody, because I know it, yeah, this could be a, a bigger concern for sure. Customer: That's what I'm thinking. Customer: That's kind of. Customer: Yeah, I just, yeah, cause I know some people don't like surprises, you know, it's. Agent (Anastasia Thomas): No. Agent (Anastasia Thomas): And we don't like you have to have those surprises. Customer: Yeah, yeah, unfortunately, I put them on my calendar so I know what's coming but I just wanted to let know that I don't think there any problems been resolved. Agent (Anastasia Thomas): Yeah, I agree. Alright. So what I've done is access to my notes. I'll also talk with don. It looks like she's on a call right now. But I'll make sure to follow up with her. Yeah, I'm with our tech team and just thank you for letting us know we appreciate that. Customer: Alright. Customer: Okay, that's fine. Yeah, okay. Customer: No, no worries at, like I said I put it on my calendar but I'm sure some people don't write it on there calendar or if they do that check it so yeah, alright, sounds good. Super! Alright, thank you. Agent (Anastasia Thomas): Yeah, alright. Agent (Anastasia Thomas): My pleasure, thank you for calling. Customer: You bet. Bye. Agent (Anastasia Thomas): Bye.