About Bargguo
I was working on a service desk when I built Bargguo, since I thought the tools we had could be better. It first ran the tickets for our own department. Now I am developing it further as a product.
Background
Back then it handled the tickets for an internal desk, with intake by email, follow-up on SLAs, a portal for customers and a knowledge base. It was in production for a long time. Only then did anyone else get to use it.
This shows. What is in the product is what a support desk needed on a normal working day, each feature was added since someone missed it.
When is support open?
Support is open 08:00 to 17:00 on weekdays and 10:00 to 16:00 during weekends, in Swedish. The person you talk to knows the system and can make changes in it, so a question rarely has to be passed on.
Report an issue and it goes straight to the person who wrote the code. Anything that comes in during the week is usually resolved that same week.
How is the company funded?
Bargguo is funded by what customers pay. There is no external owner and no resellers, so the price list is public and short. Everyone pays the same price, no matter how big a procurement is or how the negotiation went.
Depending on one person
Bargguo is developed by a single person. That is a risk to take into account, and I would rather bring it up myself than have you ask.
You can check for yourselves that nothing locks you in. The database is yours, you run the export without our help and mail comes in to an address you already have. If development stopped, your environment would keep working. You take all of it with you, wherever you want.
Data portability
Your data is kept in your own database. Anything with an export button you can export yourself whenever you like. Ask for the whole workspace and you will get it exported within 14 days. Email arrives at an address you control, even when you cancel.
Hosting and encryption, sub-processors and retention are described on Security and data.