"Current User" tokens for Email Assist

Adding my 2 cents here as well:

Currently one recommendation is to map tokens based on the CS Task Owner fields.

Then best practice would be to take ownership of the email assist task before sending the email. If you are the owner and you have tokens based on the CS Task Owner fields, then your information will be tokenized in the email template when sending. The benefit of this is audit trails and process management. You shouldn’t be completing a task that is not assigned to you. It makes it more difficult to do auditing/reporting on CTAs and Tasks. Additionally, following this process allows you to get the “logged in user” or “current user” fields and have them passed into the template via the tokens.

There are a few disadvantages to this method as well:

• For example, in SFDC Edition, the lookups to user don’t pull back as much information as desired (basically User ID, User Email, and User Name).
• Additionally, in both SFDC and NXT Editions, you cannot add default mappings for CS Task and CTA fields from the Email Templates UI. You can do so when mapping the tokens in the playbook (good), and you can map them manually via an ad-hoc email assist task (not so good - the effort to add a mapping manually is more than just deleting the token and writing in the desired value)

I think the current workaround of using tokens from CS Task → Owner is sufficient for now (especially in NXT where all user fields are accessible). Allowing Logged In User details to be passed brings certain advantages (multiple users servicing accounts) and disadvantages (audit trails, users with different roles on different accounts - Company User and Relationship User would be needed, adding to complexity) as well, but after thinking about it, CS Task → Owner makes the most sense to me.

Open to thoughts from others.

I like the workaround of using the cs task owner fields but we’re missing title and phone number, to be able to create a full signature of name, title, phone and email address.

GS, please tell us if we will get "Current User" tokens for Email Assist soon? It seems like it was added to the roadmap 3 years ago.

Thanks!
Lyne

Hello All,
Have plans to introduce signature itself as one of the fields. For now “Current User”  can be pulled in as mentioned above by @jnunes .

Pitching in another request for this idea, and wondering if there is an update on ETA?

Any update on this one? 

Checking in on this one too, any updates? Lots of QOL easy wins like this are out there.

Yes please!

@gunjanm and @heather_hansen, we recently participated in a quick virtual call with Gainsight where this was one of the topics, right? Who were we talking with?

@matthew_lind it was @ssamarth I believe in a VCAM for Dynamic Email Signatures.