Branding your CRM
Sometimes inspiring trust means shielding your team from too many technical details.
They just need to believe — with good reason — that their systems are sound and will help them in their work.
I have a couple of clients who take this axiom pretty seriously, even to the point of not naming the underlying CRM software.
To their staff, it’s not “CiviCRM”, it’s just “the CRM” or “our CRM”.
I won’t say that you must do this, but I do agree that it removes needless technical detail from the list of things that compete for your staff users’ attention.
That’s a good thing. It allow them to remain focused on things that matter.
It’s not so hard to do, either:
Decide on a name your CRM. You can call it simply “CRM”, or come up with something unique to your organization like “XYZ Association CRM”.
Be consistent in referring to your CRM by this name: in emails, in conversation, in training.
Use CiviCRM’s own “Word Replacments” feature to replace the word “CiviCRM” with your own CRM name; this replacement will be applied everywhere within CiviCRM, so even CiviCRM will refer to itself by the name you’ve chosen for it.
Edit labels for CMS menus that link to CiviCRM, so that they refer to your chosen CRM name instead.
It’s a small step you can take to help your staff users be less concerned about tools, so they can be more focused on outcomes for your mission.
All the best,
A.