lpopejoy
February 2nd, 2018, 09:04 AM
Ok, this one is going to be hard to explain...
But here's what I'm thinking.
As MSP's we all over a catalogue of services to our customers. There are times when we all need to be able to immediately filter our client list to a specific set of customers - maybe a vendor is having a problem and we need to send a quick email to everyone affected. Or we need to send an upsell email targeting everyone who DOESN'T have product X.
I'm thinking that CommitCRM could easily build this out. We would build out each product leveraging existing filter logic. For instance, make a filter that finds everyone with "offsite backup" charges for the last 12 mo. There would be a new tab on each account that would show the product matrix and see exactly what products they have or don't have. The nice thing is this would auto populate based on charge history - or however we built the filter.
Now, one of the challengs is that this results in a LOT of database queries and could slow the UI down. I would propose that this process run each night as part of the server service - and actually update DB fields - this way it can be reported and filtered against (as opposed to a real time query each time you load the tab).
Ping me offline if you need more details, I could send you a screenshot of what I'm thinking about.
I think this could be massively useful to all MSP's!
But here's what I'm thinking.
As MSP's we all over a catalogue of services to our customers. There are times when we all need to be able to immediately filter our client list to a specific set of customers - maybe a vendor is having a problem and we need to send a quick email to everyone affected. Or we need to send an upsell email targeting everyone who DOESN'T have product X.
I'm thinking that CommitCRM could easily build this out. We would build out each product leveraging existing filter logic. For instance, make a filter that finds everyone with "offsite backup" charges for the last 12 mo. There would be a new tab on each account that would show the product matrix and see exactly what products they have or don't have. The nice thing is this would auto populate based on charge history - or however we built the filter.
Now, one of the challengs is that this results in a LOT of database queries and could slow the UI down. I would propose that this process run each night as part of the server service - and actually update DB fields - this way it can be reported and filtered against (as opposed to a real time query each time you load the tab).
Ping me offline if you need more details, I could send you a screenshot of what I'm thinking about.
I think this could be massively useful to all MSP's!