31–40 of 112 posts
Earlier quoted context omitted.
IMO if I lose someone's business because they can't pay the bill... Good? Right?
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
If they can pay, then just pay for the service they got.
Seems pretty straightforward.
Earlier quoted context omitted.
IMO if I lose someone's business because they can't pay the bill... Good? Right?
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
It's not the provider's responsibility to help their customer get their sh#t together.
Earlier quoted context omitted.
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
Once they figure it out, they can come back as a paying customer. :) It's not the provider's responsibility to help their customer get their sh#t together.
Earlier quoted context omitted.
IMO if I lose someone's business because they can't pay the bill... Good? Right?
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
That's a problematic customer you don't want unless you're otherwise broke or want to keep them for other reasons (e.g. publicity).
Earlier quoted context omitted.
It's a pretty good way to get the bill paid to be honest I also run a B2B SaaS and I have found that over time the customers who I think are going to be terrible for paying, typically tend to be very good at paying and the customers who I think are going to be very good for paying (in that they have good standing in the community in things like that) tend to be pretty bad at paying on time (and with NET30 and all) Ul…
We've been overdue on something like this, but a public notice would have left us moving to a competitor. It's easy for it to happen if a colleague is away for a month, or has left, and the bill isn't being seen by anyone. Do you read (do you even receive?) out-of-office replies to your invoices? Of course it shouldn't be on an individual's email, but with annual billing it's easy to overlook.
In your scenario, the hosting company’s reaction seems extreme. In mine, it seems mild. The truth is we just don’t know and should refrain from bold defences until more details are in.
I guess we should expect more incidents like this the time to come.
Earlier quoted context omitted.
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
You'd lose out on headaches from your customer not paying and having to waste resources following up on it. If they can pay, then just pay for the service they got. Seems pretty straightforward.
The ones that contact support for every little thing or those that have a million strange feature requests on the other hand.
I suspect the moral of the story is devops and operations staff need to keep all payments, secret rotations, certificate expirations, etc. on a calendar so no one forgets to pay the bills. I hope the employee who forgot to pay the bill learns from this.
Earlier quoted context omitted.
Is this a case of can’t pay? It sounds more like a error. So you would loose out on future revenue.
You typically get multiple reminders. If that's "an error", then that's an error that will happen again and again and again. That's a problematic customer you don't want unless you're otherwise broke or want to keep them for other reasons (e.g. publicity).
The time this happened to us, I was pleased the company looked at our website and phoned the receptionist. We paid the bill within an hour, and moved the responsibility to the finance and IT teams.
Maybe there are too many customers who just ignore bills for services they no longer want to use, I don't know, but given these companies usually have a sales team it would seem worth the time to make a call or write a personal email to an existing customer to maintain their custom.