Automatic email *reply to message thread* feature
Page: 1
Recent posts in this topic
Pro
Can you implement this useful feature?
When customers get an email notification that a message has been posted...
they can automatically post directly to the thread by just replying to that particular email. This is done by altering the source of the email to fit into an activecollab mechanism that posts back to the thread.
That way, the recipient doesn't reply directly to the admin email address but replies to the thread. There is then proper tracking of the messages going back and forth (which is the whole purpose of a message thread).
Basecamp and Elance have implemented this on their message services.
For example, in Basecamp, when someone posts a message
1) I receive a message not from the admin or project leader's direct email but from a source
"THEIR COMPANY NAME[U2391206P12500687-reply@theirbasecampdomainame.com]"
2) In the message content the first line actually says, "--- Reply ABOVE THIS LINE to post a comment to the project ---"
3) I can then automatically reply to the email and be sure that it posts to the thread directly, instead of logging in and posting.
Logging in and posting isn't a big deal for me but my customers have many times hit the reply button (because it is the convenient thing to do) and emailed me directly --- cutting out the whole purpose of tracking the message thread. I could copy and paste a message reply manually myself each time but it is so time consuming when there are multiple message involved. There is so much you can pester or remind them to keep posting to the message board but when someone is paying you money to do a project -- being rude or pestering is the last thing you want to do.
Doing it this way keeps it dummy free and leaves room for laziness (if they feel it is too much for them to login to reply each time).
When customers get an email notification that a message has been posted...
they can automatically post directly to the thread by just replying to that particular email. This is done by altering the source of the email to fit into an activecollab mechanism that posts back to the thread.
That way, the recipient doesn't reply directly to the admin email address but replies to the thread. There is then proper tracking of the messages going back and forth (which is the whole purpose of a message thread).
Basecamp and Elance have implemented this on their message services.
For example, in Basecamp, when someone posts a message
1) I receive a message not from the admin or project leader's direct email but from a source
"THEIR COMPANY NAME[U2391206P12500687-reply@theirbasecampdomainame.com]"
2) In the message content the first line actually says, "--- Reply ABOVE THIS LINE to post a comment to the project ---"
3) I can then automatically reply to the email and be sure that it posts to the thread directly, instead of logging in and posting.
Logging in and posting isn't a big deal for me but my customers have many times hit the reply button (because it is the convenient thing to do) and emailed me directly --- cutting out the whole purpose of tracking the message thread. I could copy and paste a message reply manually myself each time but it is so time consuming when there are multiple message involved. There is so much you can pester or remind them to keep posting to the message board but when someone is paying you money to do a project -- being rude or pestering is the last thing you want to do.
Doing it this way keeps it dummy free and leaves room for laziness (if they feel it is too much for them to login to reply each time).
Staff
Ilija Studen
on Apr 7. 2008. 6:46 am
This is a killer feature, but with it's own set of problems that need to be well though out. We'll definitely play with this, but I cannot provide any details or promise you anything at this point.
activeCollab team member | LinkedIn
Pro
cbtrussell
on Apr 7. 2008. 11:57 am
+1000
This would be a huge help for those clients/participants who refuse to do anything outside of email, as all conversations could be initiated on the site, and continue to be documented in aC even if the user never logs in. I've actually considered having one of our developers implement this as a plugin given the potential value to our process.
The next logical step would be to have aC function as a team/group mailbox, as TeamWorkLive has done. But one thing at a time, I don't want to overwhelm you Ilija ;)
Brandon
This would be a huge help for those clients/participants who refuse to do anything outside of email, as all conversations could be initiated on the site, and continue to be documented in aC even if the user never logs in. I've actually considered having one of our developers implement this as a plugin given the potential value to our process.
The next logical step would be to have aC function as a team/group mailbox, as TeamWorkLive has done. But one thing at a time, I don't want to overwhelm you Ilija ;)
Brandon
Pro
+1, "with caution."
One problem with this I noted on BaseCamp this week is that it does not give the person replying any control/vision of to whom the reply is sent (at least in the basecamp implementation).
At the very least this tends to netiquette violations (I received 30 or so messages about something that had little to do with me). I don't want my clients in the same situation.
At the worst it can lead to serious breaches of confidentiality or information control (From the BaseCamp owner's client, I received several messages which contained proprietary info, even though I have close relations with the sender's "competitors").
Also not a boat I want my clients in-- it should always be clear on the send side, to whom a business communication is sent.
One problem with this I noted on BaseCamp this week is that it does not give the person replying any control/vision of to whom the reply is sent (at least in the basecamp implementation).
At the very least this tends to netiquette violations (I received 30 or so messages about something that had little to do with me). I don't want my clients in the same situation.
At the worst it can lead to serious breaches of confidentiality or information control (From the BaseCamp owner's client, I received several messages which contained proprietary info, even though I have close relations with the sender's "competitors").
Also not a boat I want my clients in-- it should always be clear on the send side, to whom a business communication is sent.
