Hooray – we’re listed on AppSource!

We’re delighted to announce that Sales In-a-Box has been listed on Microsoft’s AppSource. You can now download a trial directly from AppSource and assess whether the simplicity of Sales In-a-Box will allow you to quickly deliver the benefits of Microsoft Dynamics 365 for Sales.

You’ll need an environment to deploy into, but after that it is only a matter of clicking on Free Trial and the deploy will start. A few short minutes later, you’ll have Sales In-a-Box with a set of demonstrative sample data. Not long after that, we’ll reach out to you to discuss how it’s going and what your thoughts about the software are.

 

Continue reading

News years resolutions for your CRM

In the spirit of new year’s resolutions, we thought we’d share our own targets for our Customer relationship management (CRM) software. All too often, systems (and the associated processes) have stagnated since they were deployed. Over time this results in reduced sales effectiveness and, ultimately, undermining why you have a CRM system in the first place.

View the entire post, written by David, on UK Business Forums.

Designing for a happy birthday

In celebration of our first “official” day designing and developing software for Recursyv, we turn our attention to the birthday controls within Dynamics CRM. Getting to know customers and being responsive to them on a personal level¬†is one of the drivers of implementing a CRM system. In this light, it’s frustrating that¬†the storing and use of birth dates is so poorly handled.

Let me illustrate with the birthday selector on the contact form.

2016-11-17-birthday-selector-with-border

It’s a standard date control. You’d think there’d be no problem there, but in practice it means that either you need to know the contact’s birth year or your data is inaccurate. One is unlikely, the other is inelegant. Neither¬†make for great design. In practice, the pragmatic approach is just to ignore birth year in the data set, but¬†it seems that¬†in a mature software system, it shouldn’t be necessary to use workarounds for such basic features.

Our design ambition for the In-a-Box product set is that it should be intuitive and easy-to-use. Inelegant workarounds don’t fit into this mindset. Consequently, our current thinking¬†for the In-a-Box product set is to create custom fields for birthday (day of the month, i.e. 1 – 31) and birth month. This will at least enforce¬†that data held on system is robust (i.e. accurate). It will require¬†some changes to views but that’s straightforward enough. In practice, the data¬†should be used to drive dynamic marketing lists and that is easily achievable with data structured like this.