"Share to Outlook" to include Chat sender's name in "from" field

%3CLINGO-SUB%20id%3D%22lingo-sub-1272066%22%20slang%3D%22en-US%22%3E%22Share%20to%20Outlook%22%20to%20include%20Chat%20sender's%20name%20in%20%22from%22%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272066%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20recently%20implemented%20TEAMS%20for%20our%20company%20of%20150%20who%20are%20now%20working%20from%20home.%20We%20of%20the%20IT%20support%20group%20are%20finding%20that%20people%20are%20contacting%20us%20through%20TEAMS%20rather%20than%20going%20through%20our%20%22normal%22%20channel%20of%20sending%20an%20email%20to%20our%20tech%20support%20mailbox.%26nbsp%3B%20%26nbsp%3BWe'd%20like%20to%20be%20able%20to%20take%20a%20TEAMS%20chat%20message%20and%20forward%20it%20to%20to%20the%20tech%20support%20email%20address.%26nbsp%3B%20Now%20when%20you%20%22share%20to%20outlook%22%2C%26nbsp%3B%20the%20address%20is%20always%20our%20own%20(not%20the%20person%20seeking%20help).%26nbsp%3B%20Is%20there%20a%20way%20to%20extract%20the%20user's%20account%20information%20to%20put%20into%20the%20%22from%22%20field%3F%26nbsp%3B%20%26nbsp%3Bbefore%20sending%20the%20email%3F%20Thinking%20of%20maybe%20a%20Powershell%20script%20or%20PowerApp%20that%20would%20do%20this%20for%20us.%26nbsp%3B%20Thanks.%26nbsp%3B%20---%20L%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1272066%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EChat%20Microsoft%20Teams%20Developer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272343%22%20slang%3D%22en-US%22%3ERe%3A%20%22Share%20to%20Outlook%22%20to%20include%20Chat%20sender's%20name%20in%20%22from%22%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272343%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F604771%22%20target%3D%22_blank%22%3E%40lkeyes%3C%2FA%3E%26nbsp%3B-%20What%20you're%20asking%20for%20cannot%20and%20should%20not%20be%20supported.%20That%20would%20let%20you%20send%20an%20email%20on%20behalf%20of%20someone%20else%2C%20even%20external%20from%20your%20org!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20I'm%20interpreting%20the%20scenario%20correctly%2C%20it%20sounds%20like%20you%20need%20that%20user's%20email%20address%20included%20in%20the%20content%20you%20send%20to%20the%20support%20alias%2C%20so%20they%20can%20then%20reach%20back%20out%20to%20the%20right%20person.%20One%20simple%20way%20to%20accomplish%20this%20would%20be%20to%20hover%20on%20the%20profile%20of%20the%20user%2C%20copy%20their%20email%20address%2C%20and%20include%20that%20in%20the%20body%20of%20the%20email%20you%20send.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272409%22%20slang%3D%22en-US%22%3ERe%3A%20%22Share%20to%20Outlook%22%20to%20include%20Chat%20sender's%20name%20in%20%22from%22%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272409%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27881%22%20target%3D%22_blank%22%3E%40Kyle%20Blevens%3C%2FA%3E%26nbsp%3B%20Well%2CI%20agree%20in%20principal.%26nbsp%3B%20%26nbsp%3BThe%20reason%20we'd%20change%20the%20email%20sender%20is%20that%20the%20the%20support%20desk%20software%20relies%20on%20the%20sender's%20address%20to%20correctly%20label%20and%20prioritize%20the%20support%20tickets%20that%20are%20created%20via%20email.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20would%20by%20no%20means%20be%20a%20publicly%20available%20function%2C%20but%20only%20for%20our%20support%20techs%20to%20be%20able%20to%20forward%20emails%20that%20they%20have%20received%20from%20our%20staff%2C%20which%20we%20are%20trying%20to%20encourage%20to%20send%20directly%20to%20the%20support%20queue.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIts%20an%20interesting%20%22problem%22%20that%20has%20come%20up%20with%20our%20implementation%20of%20TEAMS%20(for%20all%20of%20two%20weeks%20old%20now).%26nbsp%3B%20%26nbsp%3BNow%2C%20staff%20will%20start%20a%20chat%20with%20%22their%22%20trusted%20support%20tech%20rather%20than%20throw%20their%20questions%20into%20the%20common%20queue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPer%20your%20suggestion%20of%20the%20cut%20and%20paste%20of%20the%20address%2C%20we're%20trying%20that%20that%20now.%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20even%20if%20we%20couldn't%20do%20the%20sender's%20address%20fix%20up%2C%20it%20would%20be%20nice%20to%20have%20a%20button%20that%20they%20could%20push%20that%20would%20automate%20the%20sending...%20via%20a%20script%20or%20program%20that%20extract%20the%20chat%20contents%20and%20then%20send%20to%20the%20support%20desk%20queue%20email.%26nbsp%3B%20%26nbsp%3B---%20L%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272771%22%20slang%3D%22en-US%22%3ERe%3A%20%22Share%20to%20Outlook%22%20to%20include%20Chat%20sender's%20name%20in%20%22from%22%20field%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272771%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F604771%22%20target%3D%22_blank%22%3E%40lkeyes%3C%2FA%3E%26nbsp%3BAhh%20I%20see%2C%20that's%20helpful%20context.%20Tricky%20to%20solve.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20don't%20know%20the%20content%20or%20sensitivity%20in%20what%20kind%20of%20support%20questions%20are%20being%20fielded%2C%20but%20another%20great%20option%20could%20be%20to%20set%20up%20a%20particular%20team%20with%20one%20or%20more%20channels%20for%20different%20support%20topics%2C%20and%20establish%20that%20as%20a%20place%20to%20reach%20out.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20support%20folks%20can%20adjust%20their%20notification%20settings%20for%20the%20channels%20so%20they%20get%20a%20notification%20for%20each%20new%20post%20to%20make%20sure%20they%20don't%20miss%20them.%20Or%20figure%20out%20a%20triage%20process%20and%20then%20the%20right%20individuals%20can%20be%26nbsp%3B%40mentioned%20as%20needed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20suggestion%20obviously%20doesn't%20address%20getting%20these%20into%20your%20support%20tool%2C%20but%20that%20may%20be%20feasible%20as%20well%20by%20building%20a%20Teams%20app%20or%20bot!%20And%20it%20lets%20the%20folks%20who%20clearly%20prefer%20reaching%20out%20via%20Teams%20do%20so%20in%20a%20more%20centralized%20and%20managed%20way.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We have recently implemented TEAMS for our company of 150 who are now working from home. We of the IT support group are finding that people are contacting us through TEAMS rather than going through our "normal" channel of sending an email to our tech support mailbox.   We'd like to be able to take a TEAMS chat message and forward it to to the tech support email address.  Now when you "share to outlook",  the address is always our own (not the person seeking help).  Is there a way to extract the user's account information to put into the "from" field?   before sending the email? Thinking of maybe a Powershell script or PowerApp that would do this for us.  Thanks.  --- L 

3 Replies
Highlighted

Hi @lkeyes - What you're asking for cannot and should not be supported. That would let you send an email on behalf of someone else, even external from your org!

 

If I'm interpreting the scenario correctly, it sounds like you need that user's email address included in the content you send to the support alias, so they can then reach back out to the right person. One simple way to accomplish this would be to hover on the profile of the user, copy their email address, and include that in the body of the email you send.

 

Highlighted

@Kyle Blevens  Well,I agree in principal.   The reason we'd change the email sender is that the the support desk software relies on the sender's address to correctly label and prioritize the support tickets that are created via email.  

 

This would by no means be a publicly available function, but only for our support techs to be able to forward emails that they have received from our staff, which we are trying to encourage to send directly to the support queue. 

Its an interesting "problem" that has come up with our implementation of TEAMS (for all of two weeks old now).   Now, staff will start a chat with "their" trusted support tech rather than throw their questions into the common queue.  

 

Per your suggestion of the cut and paste of the address, we're trying that that now.
 

And even if we couldn't do the sender's address fix up, it would be nice to have a button that they could push that would automate the sending... via a script or program that extract the chat contents and then send to the support desk queue email.   --- L 


   

Highlighted

@lkeyes Ahh I see, that's helpful context. Tricky to solve.

 

I don't know the content or sensitivity in what kind of support questions are being fielded, but another great option could be to set up a particular team with one or more channels for different support topics, and establish that as a place to reach out.

 

The support folks can adjust their notification settings for the channels so they get a notification for each new post to make sure they don't miss them. Or figure out a triage process and then the right individuals can be @mentioned as needed.

 

This suggestion obviously doesn't address getting these into your support tool, but that may be feasible as well by building a Teams app or bot! And it lets the folks who clearly prefer reaching out via Teams do so in a more centralized and managed way.