The person being helped should never get a bill
Vukalink charges the technician and nobody else. It sounds like a pricing footnote. It decides whether support happens at all.
By Howell Asava, Developer, Vukalink ยท
Think about the moment a support call usually goes wrong. It is rarely the fault itself. It is the five minutes beforehand, when the technician says: first you will need to download something, make an account, confirm your email, and choose a plan.
By then the customer has a printer that will not print and a growing suspicion that this is going to cost money. Some give up. Others install whatever they are told and resent it.
One side pays
Vukalink removes that moment. Receiving support is free, without a time limit and without an account. The customer downloads one installer, opens it and reads out a nine-digit ID. That is the whole of their part.
Only the computer a technician connects from needs a plan, and plans are counted per technician. A freelancer supporting forty small offices pays for one seat. An IT department with six technicians pays for six.
Why it matters more than it seems
Pricing by technician is easy to reason about. You count the people who give support. You do not count sessions, or "channels", or how many devices happened to be online on Tuesday. When a business grows, the bill grows when it hires, which is when it can afford it.
It also changes the conversation with customers. A technician can say, truthfully, that the program costs them nothing and asks them for nothing. We expect that sentence to do more for a first appointment than any feature list.
The numbers
Premium is USD 12 per technician a month when billed yearly, or USD 15 month by month. Enterprise, for IT teams, is USD 29 billed yearly or USD 35 monthly, from five technicians. Every new computer starts with 60 days of everything, and when that ends the program carries on as a Free version with limits by amount.
The customer's side stays at zero throughout. We intend to keep it there.