A library of opinionated defaults for a typical MSP. Add whichever packs are useful - on a brand new install or on one that has been running for years.
Adding never overwrites or deletes anything. Anything already present under the same name is skipped, so a pack can be added again later to pick up entries you removed by mistake, and adding twice never produces duplicates. Everything added is editable and deletable afterwards like any other record. Ticket templates, canned responses, vendor templates, document templates and license templates added from an earlier version can be brought up to this one with Update - that one does replace what they hold.
| Content | In library | Already here | Will be added | |
|---|---|---|---|---|
|
Add first, or these come in without them. |
Nothing to add
|
Ticket templates bring their task lists, what they ask for and their request forms with them - the request forms come in turned off, ready to turn on in each template's Client portal tab. Canned responses come in shared, offered to every agent on the ticket categories they are for. Document templates come with what they ask for and how often their documents are reviewed - who should have each is yours to set. License templates come with their vendor - added from the vendor templates when it isn't here - and are sold as the products of the same name once those are here; who should have each is yours to set too. Products are filed under income categories and priced as starting points only - hardware and resold licensing come in at zero because they are quoted per deal.
A fictional book of business for demos, training and screenshots - clients with the people, equipment, documentation, credentials, tickets and billing a typical MSP would be carrying for them. Each one arrives with an onboarding project, an onboarding ticket per asset, response targets, racked infrastructure, a documented switch port map, IP addresses and a supplier list. Managed, co-managed, break fix and hosting only clients are all represented, most of them paid up to date and a few of them not. Your own side of the business is generated too - bank accounts, suppliers, operating costs, recurring expenses, transfers, catalogue lines for the things you sell, closure days, monthly budgets, and a working diary of team meetings, maintenance windows and the unbilled running around that never gets logged against a client. Everything is spread across the last two years and dated relative to today, so the dashboard, ticket queue, aging, profit and loss and every other report have real history behind them rather than one flat month.
This is sample data, not configuration. Nothing in it is labelled as demo data - the clients, tags and references all read as real, which is the point. Removal matches the client names in the library, so renaming a demo client stops it being removable. Contacts use addresses on the reserved .example domain, which cannot receive mail, and the agreements are created with email notification switched off. Anything shared - accounts, suppliers, response targets, tax rates, catalogue lines and calendars - is matched on more than its name, so records this install already had are never touched, and the company side of the books is always built against accounts this page created rather than yours.
Add the Categories and Tags packs above first, or the tickets, invoices and tags come in bare.
demo client(s) are here: