New features
Link cases and opportunities
We have introduced the ability to link multiple cases with an opportunity, both from a case in the case overview screen and from the opportunity overview screen. This was a hotly-requested feature; there is a requirement for a relationship between follow-on cases and an opportunity, for example after-care cases or managing the delivery of a good or service via the cases area off the back of a sale.
The opportunity has a new grid area that lists the linked cases and shows their statuses.
Send and receive images & attachments from cases
We have implemented the ability to send and receive attachments within the case emails area, and implemented the ability to receive any images attached in the body of an email that has been sent to the cases area. This will be useful for providing customer service, for example in sending pictures of faults or documents to sign off.
Case API Upload documents
We have implemented a new API method to the BuddyCRM cases API to allow the upload of multiple documents to a specific case ID. This would allow an integrated 3rd party application to send documents to a case in BuddyCRM.
Quality of life improvements
Cases – high volume of custom fields
We have optimised the cases area to support creating and loading cases where a case template has a high volume (over 200) of custom fields added, so that it performs much quicker.
Bug fixes
Marketing – tracking
We have fixed an issue that could occur where data on the tracking of marketing campaigns (for example opens and clicks) were not updated in the marketing screen. This data will now be correctly reflected within the system.
Cases – email replies
We have fixed a bug that could occur where when a customer replies to an email sent via a case, the reply could create a brand new case rather than going into the same case thread. Emails sent back to a case will now be correctly appended to the relevant case, as long as the subject line of the email is the same.
Cases – ‘assigned to’ mandatory warning
An issue could occur where the application didn’t warn the user if ‘Assigned To’ field hadn’t been completed on a case. The field will now show in red, consistent with the other mandatory fields.