Looking for

[jfm]

I'm trying to figure out a way to keep track of my client's services with me.
I want to store many information. Ex:

Router's IP and configs if any.
Wich antivirus theyre subscribed to (licence key + date)
Wich backup service (licence key + date)
TeamViewer's ID and password.
Emails configs and passwords.

Ideally all in the same system, we started doing a sheet for each client but it's getting painfull.

Don't know if a CRM would do this.
Thanks for any idea !

 

[Slaters Kustum Machines]

We use the Wiki option in RepairShopr for this. Works great. I know there are some tax issues with RS in Canada so not sure if that is sorted or would work for you.

 

[thecomputerguy]

I use Freshbooks for invoicing and Google Keep for client specific information including passwords.

 

[cypress]

Repairshopr does this for me. Especially the License Keys. I add them to Inventory and check of Serialized Key.

I also put in the tickets Notes when it was installed, the license key and when it expires. The information shows for their proof and mine.

Also for redundant reasons I create a Spreadsheet to keep track of it on my computer.

 

[dgoglio]

We use a product called ITGlue to track all client and internal configurations. We did a lot of research and thought it was the best product out there.

 

[Vyper28]

Onenote!

 

[TECCS]

I use Freshbooks for invoicing and Google Keep for client specific information including passwords.

How safe is google keep for storing client info and especially passwords? I use it for general notes but wouldn't use it for client info and especially passwords. However I haven't looked into the security of it at all

 

[fencepost]

I'm going to recommend storing passwords and such in a separate package designed for it. I use LastPass Premium (Enterprise would be better if you're sharing among users) but you can also look at 1Password or some other options. You can also use some free options like KeePass, possibly with the keyfile stored on a shared location (dropbox, onedrive, etc.) but look into how those handle possible conflicts.

Configuration information and even license keys are much less sensitive than system and remote access passwords.

 

[HCHTech]

We currently use mSecure, but I agree with @fencepost - use a package designed for it. I haven't gotten into the asset capabilities of RepairShopr yet - I'm sure that would work as well, although I have a bit of a concern that it would tie me pretty tightly to that product. Check out their ability to export the data in usable form (like CSV) - it that exists then go for it. Especially if you have more than one tech - being able to both store it securely AND share it among your techs the key thing.

 

[PodnutzPro]

use forms at www.informedit.net

It is not a CRM, but pdf fillable forms to keep track of the info

 

[fencepost]

To expand a little, for a multi-user organization with employee techs I'd look hard at LastPass Enterprise ($24/user/year) due to the auditing and access logging capabilities - if/when someone leaves, you should be able to go in and see what accounts/passwords they've used and change passwords as required. Similarly you can do auditing to confirm that staff is not inappropriately using accounts/passwords that they actually shouldn't be.

I suspect that the 1Password for Teams product has something similar, but it's not quite as obvious from their page. They're also quite a bit more expensive at $48/year/user (current special! pricing gets "Pro for the cost of Standard" grandfathered at that price and ends 10/15, but that same pricing was "expiring this weekend" several months back as well so if you miss it just wait until Black Friday or the like).

 

[TECCS]

I'm going to recommend storing passwords and such in a separate package designed for it. I use LastPass Premium (Enterprise would be better if you're sharing among users) but you can also look at 1Password or some other options. You can also use some free options like KeePass, possibly with the keyfile stored on a shared location (dropbox, onedrive, etc.) but look into how those handle possible conflicts.

Configuration information and even license keys are much less sensitive than system and remote access passwords.

I use Keepass and store on onedrive but there is only me using it at a time don't know about more than one person reading writing to it at once

 

[jfm]

Well after looking around alot, I went back to a Gsheet for AV and backup subscriptions, seems to be the most efficient solution I found.

Anthing more than that (network configs, passwords) will go into a full documentation for the client wich I will charge for.