Aaron Wittman, the facility is in all tasks as soon as the task is created and generates as an option in the comment area, whereby if you dont click the email option, it just saves as a comment, if you choose the mail option it gives you an interface similar, to what your email facility provides. Emails received can also generate a task with the ability to respond via the reply button.

As a scenario.

Ideally I would set up Outlook Exchange with transport rules that forward emails with particular email addresses, to generate tasks. Automations fill the client name, contact email & phone # fields as tasks are created regenerated or an email generates a task. The email interface uses these contact details as suggested email addresses to send the email to. I would also have saved email templates that can be triggered within the task. The whole email conversation happens within the task. Add to that, as clients dont always respond to the correct email, the ability to merge tasks so that the errant email is now in the the original task.

As a backup, copies of all emails flow via outlook. Always good to have 2 versions. I would also quote the task number on every email so you can be specific with referencing emails to clients.

Thanks Jacquie Mitchell on the sent directly to, is the use case to be able add the email onto an existing task that has been created? as an additional information for this? We do have work planned for non client consoles to be able to be emailed without an account, which will share more on this as we the design phase is completed.