Feedback
Recent updates
Community

Have something to suggest?

Tell us how we could make plannr more useful to you.

In Progress

Review Logs

A few have noticed that circles don’t have review dates right now and I just wanted to get ahead of the curve and share some info on what we’re working on and when we’re planning on releasing it. The team here are working on a new thing called “Review logs” and this new functionality will expand what you can currently hold in Plannr on a client’s review dates. This feature will be built for clients, and circles at the same time. Firstly, review logs will allow you to hold a history of every review you’ve ever completed for a client and won’t be limited to next and previous like Plannr currently. Each review log entry will allow you to hold: The date of the review The type of review (whether it was in-person, or remote) Notes The online meeting link (this will be displayed on the client portal, too) Timelines This is being worked on right now, and we’re planning on launching either today or tomorrow! This might not go out in time with the new portal this evening, but will definitely be there before the weekend. What happens to my existing data? We’ll automatically make history log records for your next and previous review dates when we put this live and this will also create records for circles if we’ve migrated joint clients to circles for you, too. Basically, there’s nothing for you to do when we put this live other than make use of the new functionality!

Gareth (G) Thompson 18 days ago

2

Automation enhancements

[Taken from Plannr Community threads - James Rolfe BMSG - posted by Abi on James’ behalf] When you are looking at Automations, could some thought be put into access permission: Not sure about others, but personally, I would like to see a Firm level setting allowing us to select which advisors (members) can create new Automations (and indeed workflows). I would also like to be able to choose which Automations an advisor can see and execute. In simple terms, it would be any they created themselves (if they had permission to do so) and any Firm level ones they have been given access to. Also a setting to determine whether an Automation or a Workflow can be run manually or not - So advisors may need ‘access’ to an automation because it runs automatically when they create a client, for example, but we don’t want them to subsequently be able to run that manually. As we build out, we are using more and more Automations and are now having to name with advisor names on the front, the list is long and advisors are sometimes triggering the wrong ones etc…. If you send a Form request via an automation, you have to select a person who is ‘sending that form’. We have automations that are created centrally for all advisors to use. The problem is that when an advisor triggers that automation, the notification that the form has been completed goes back to the person listed in the Automation - not to the person that triggered it. So one person is getting all of the notifications from all forms sent by all advisors. There is no option for it to be sent by the person triggering the automation (as far as I can see) and no way to tell it to send the notification to the person triggering the automation either. The only solution I can see is to create a separate copy of the automation for every advisor and, if we update that centrally, to update every copy. Am I missing something - is there a better way to do this? I think the issue with the Notify Block is you can only notify people an automation has been triggered or a document/form sent - you cannot notify them when the event actually completes (form completed / document signed) I have now discovered 2 issues. The Form Request can only be set to send the notification the form has been completed to a specific person - really need to be able to select ‘Assigned Adviser’ or ‘Person Triggering Automation’ as options there. There is a similar problem with document signing - all notifications the document has been signed seem to be sent back to whoever created the automation rather than to the assigned advisor or the person that triggered it. Ideally, we want a set of ‘Firm Approved’ automations and they would send notifications to the assigned advisors etc. In a perfect world, we do not want advisors to be able to create automations for themselves as this leads to a number of issues - Automation, we feel, should be a Firm Level access to create them and then allocate which advisors can access them.

James Rolfe 18 days ago

Automation to use review dates

Review Dates It would be a real improvement if we could allow a client's next review date, and possible also the previous review date, to update automatically. We currently have 'Annual Review' workflows that are automated within 'Annual Review' cases, however our final step in the process is to manually update the previous and next review dates onto next year. If a step in the automation could be 'when Annual Review case is complete, move previous review date to today's date' and 'when Annual Review case is complete, move next review date to 365 days from today's date, or something similar, this would take out this manual step which, at the moment, is leaving in a chance of human error and future annual reviews, which are an FCA requirement, being missed.

Mike Cound 12 days ago