@GreggH8509 Great, thank you--would be very helpful!

Hi George,

If you are looking for automated email templates with this feature, there is a workaround that you can use to get to a similar end result. Create a transient task for each desired "flavor" of email that you want to send out and use whatever triggers you want to control under what conditions each transient task fires. Each transient task can have its own notifications set up, so you could have two different transient tasks that trigger when a Pay Issue Fee task dockets--one for small entity and one for large entity (bonus--you can include language in the small entity version reminding the client to inform you if they are no longer small entity).

But that only works if you are automatically sending these emails out, so maybe not a good fit for what you are wanting to do.

Hi Ann,

Thank you for your feedback. We have added this to our list of future projects. We will let you know when this has been added. Thanks.

@GeorgeJ4336
This happens for us frequently as well. Our work around is to forward the email to the appropriate AppColl email address (ex. xxxxm123@intake.appcoll.com). I generally just put "for the file" in the email message, but this way it is saved to the matter, the documents are saved separately AND the message appears in the conversation tab.

If you select an assignee for a contact (in the contact details page) and the assignee has an address, it will automatically copy over to the contact's address. Please note, this will not overwrite any existing contact address information. It will only populate the assign address if the contact address is blank.

We have spoken with engineering to link the assignee address to the contact address, such that changing the assignee address will automatically update the contact address.

We will update this post when this has been completed.

Hi George,

Thank you for the suggestion. We have recorded this with engineering and will let you know when this has been completed.

Hi Richard,

Thank you for the suggestion. We will have recorded this with engineering and will let you know when this has been implemented.

Hi George. Thank you for the suggestion. We will have recorded this with engineering and will let you know when this has been implemented.

Thank you for the suggestion. We will take this under consideration.

Hi Mark,

Thank you for the suggestion. We have recorded this as a new feature request. We will let you know when this will be implemented.

Hi Mark,

Thank you for the suggestion. We have recorded this as a new feature request. We will let you know when this will be implemented.

Hi Christian,

Currently, the solutions you mentioned are the only ways of doing so. However, we are working on a solution. We will certainly make this known once it's done.

@AppCollS2261 That's great--I would, however, make sure that:

a) The update only happens to tasks that have the same role as the task owner (for example, if you change the attorney for several matters, you'd only want to update the tasks for those matters that had the previous attorney as the owner--you wouldn't want to make the new attorney, for example, the owner of tasks owned by the paralegals for the matter).

b) The update only happens to "open" tasks--the "owner" of closed tasks is a historical record of which person handled that closed task. It shouldn't be changed (or, at the least, make it an option that you have to opt into in order to bulk-update the owner of closed-out tasks).

Looking forward to this.

Best,
Christian

Hi CHristian,

This is a good idea. We will look into this the next time we revise the UI.

Hi Christian,

This has been added to our development schedule. We will let you know when this has been done.

@KimG5166 Does the "Same as above" residency checkbox solve your issue for inventors? It should allow you to put in a secondary residency address. fa0fabb3-7d76-4233-a4d5-4f49da803261-image.png

@ChristianS9906 That takes care of one part. The UI is always a large part of any project. We also have to notify account admins when sync changes have been made so that they can review the changes. Other side effects that I haven't predicted have to be considered as well.

@AnnM9156 That is correct--it is just a field that records data regarding the application. You can, however, customize triggering for tasks based on the value in that field. I took a look at our docket, and our 3-month non-final OA response deadline has two flavors--one that is called "Respond to Non-Final Office Action - 3-month deadline" and the other that is called "Respond to Non-Final Office Action - 3-month deadline (Track One)." The "track one" version triggers when a non-final OA is received in a case that has Track One status specified, and the non-track one version triggers when a non-final OA is received in a case that does not have Track One status specified. Our 4-month OA deadline triggers when either of the 3-month deadlines closes as "missed."