Email Examples

To: David Kendriks

Cc: team@teamdev.com


Subject: Single Sign-on Feature: Questions


Hi David,


There are a couple of things I’d like to discuss about the Single Sign-on feature (SSO).

At the moment, the feature works well only in Chrome, and there are errors in other browsers, such as IE, Firefox, and Safari.


If you want, we can rewrite the SSO feature completely to make it work in other browsers as well. That will take approximately 50 hours, so we might have to postpone some of the other tasks of lower priority.


At the moment ~90% of our customers are using Chrome, so another option would be to implement a workaround. Those on IE, Firefox and Safari would use the legacy authentication for now. We can always come back to SSO issues in the following sprints, if that’s still important.


Could you please let me know which way you’d prefer?


Thanks,

Kevin



*******



To: John Johnson

Cc: team@teamdev.com


Subject: Projects 2.0 is Coming Soon!


Good morning John,


It’s Mary here from TeamDev.


I’m writing to tell you that we’re releasing Projects 2.0 this week, and I thought it might be useful for your team.


Here’s the link: https://projects.tm.


If you have any questions, please let me know.


Thank you and have a great day!


Mary




*******



To: Sarah Bennet

Cc: team@teamdev.com


Subject: Unison Integration Issues Addressed


Hi Sarah,


Thank you for reporting the Unison integration issues. Just wanted to let you know that all the reported issues are now resolved. The production servers have already been updated with the latest version of the app.


Please let me know if the Unison integration tests still fail for you. If that is the case, it would be helpful to have a bit more details on the dataset used for testing.


Thank you,


Andrew




*******



To: Liz Eaton

Cc: team@teamdev.com


Subject: Status Report Dec 6


Hi Liz,


Here’s my status report.


Yesterday I took care of the ErrorPage bug. I made some fixes after Andrew reviewed my code and ran the tests. No issues were found.


Today I’ve been working on the Timeline feature. I’m almost done with it, I think I need around 2 more hours to finish testing it. I’ll ask Donald to review my code and make the necessary changes.

After that, I’m planning to move on to resolving the Field Array issue. I think it’ll take approximately 8 hours.


I don’t have any blockers at the moment.


Thanks,


Robin



*******



To: Ethan Layton

Cc: team@teamdev.com


Subject: ItemPicker: Questions


Hello Ethan,


We’ve discovered an issue in the ItemPicker functionality on the Networks page. It seems that it doesn’t save the user’s choice after clicking the “OK” button.


We can see two ways to solve this.

We could postpone refreshing the page until the user’s choice has been recorded, or we could go deeper and find out what went wrong in the feature itself.


The first solution is pretty fast, but we might run into more troubles in the future. The second option will take up to three days, but it’s much more reliable.


Please let me know which option you would like to go with.


Thanks,


Jane


*******



To: Leah Murphy

Cc: team@teamdev.com



Subject: Follow-up on Projects Evaluation


Hi Leah,


During our phone call, I didn’t quite get your point about the evaluation process. Would you like to extend the evaluation?


If there’s anything I can help you with, feel free to email or call me at 555-55-555-55.


Have a great day,


Axel



*******


To: Jean Collins

Cc: team@teamdev.com


Subject: New Sprint Meeting


Hi Jean,


I’m glad to let you know that we’ve completed all the tasks in the sprint. All the changes have been deployed onto the server and are ready for your review.


Could we have a meeting later today to discuss our plans for the next sprint?

Would 5 pm (GMT+2) work for you?


Please let me know what time would be convenient.


Thanks,


Leon




*******



To: Martha Kingsman

Cc: team@teamdev.com


Subject: Working Schedule over the Holidays


Hi Martha,


Thank you for clearing up the matter with our schedule during the holidays. Alex and Kevin are going to take the first week off, if that’s OK with you. Their first working day will be Jan 9.


Just in case, I’ve attached a calendar of our working schedule during the holidays.


It’s been great working with you this past year.

Our team wishes you a Merry Christmas!


Paul


Attachment: Calendar.pdf  



*******



To: Ellen DeGeneres

Cc: team@teamdev.com


Subject: Meeting Follow-up


Hi Ellen,


Thank you for joining our meeting. It was really helpful and cleared up a lot of questions we’d had.


Here’s the link you requested during our meeting: https://projects.tm  


Please let me know what you think.


If you need any further information, feel free to contact me.


Best wishes,


Austin


*******



Bad email

Good email

To: kevin@company.com,

alice@anothercompany.com


Subject:


Hi, Kkevin,


Thtank you for your feedbak.


If you will go to our helpDesk you will find, actually you can search there, and read what to do in this situation like your.


For example, you can change the settings in your profile and then it will start working, anyway there’s more info on the help desk. I attached a screenshot of what it should look like.


If you will have another problems after this, let me now and i will tell our team and we will create solution.


thanks,

bye!



To: kevin@company.com



Subject: Solving your Account Issues


Hi Kevin,


Thank you for your feedback.


In order for your account to start working properly, you need to change your settings a bit. I’ve attached a screenshot to walk you through the process.


In addition, I would recommend checking out our Help Desk for more details: https://OurHelpDesk.com


Please let us know if the problem persists.


Have a great day,


Anjela


Attachment: screenshot-configuration.png  




*******



<Status email (sent on Friday)>


Hi Tiffany,


Please let me update you on the sprint status.


I have completed the improvements planned. The most important feature is the grouping of incoming tasks by the filter value. It allows us to process the related tasks in a single thread instead of random distribution across threads. It is implemented in a lock-free fashion.


I have also performed some benchmarks. The time taken to process the target dataset has been drastically reduced. The application is now 3x faster.


My changes are now deployed onto the staging server. Feel free to start the acceptance testing.


As discussed earlier, in scope of the next sprint I am planning to continue working on performance improvements as follows:


  • measure 25K to 100K tasks per request processing within the current implementation strategy and against the Map-Reduce-based version;

  • define the recommended settings for Unison desktop client applications and the best strategy for the request decomposition.


These tasks will take me up to 32 hours to implement.


Please let me know if you have more tasks in High priority. I will then include those to the next sprint as well.


Thank you and have a nice weekend!


Vasiliy.




*******



<Reply in scope of an email conversation>


Hi Tiffany,


Thank you for your effort on reporting the Unison integration issues.


Just wanted to let you know that all the reported issues are now resolved. The production servers have already been updated with the latest version of the app.


Please let me know if Unison integration tests still fail for you. In which case I am going to need a bit more details on the dataset used for testing.


Thanks!


Vasiliy.



*******





Comments