"Current User" tokens for Email Assist
None
I have a request from the client to be able to send out Email Assist emails using the "Current User" strategy which can be see in reports, etc. Essentially what they want is to be able to create a template with a "logged in user" token that grabs the current uses "ID" and then looks up to the fields on the user table.
FYI: A key requirement here (which is in another feature request) is to be able to pull the field "phone" off the user table which doesn't appear to currently be possible.
FYI: A key requirement here (which is in another feature request) is to be able to pull the field "phone" off the user table which doesn't appear to currently be possible.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Thanks,
Nitisha
If you'r looking for getting Phone number of the Account Manger assigned to Account, you can still get it now by creating a Formula field on Account to get phone number of Account Manager and map that in Email Assist.
Regards,
Hitesh
The workaround with the custom field on the CTA is interesting but our templates will also be used in advanced outreach (which won't have a CTA)
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:
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,@jnunes .
Have plans to introduce signature itself as one of the fields. For now “Current User” can be pulled in as mentioned above by
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!
What is the latest on this? Critical component for our user adoption. We’re going to be forced to start exploring other tools if this is not on the immediate roadmap.
Checking for updates and upvotes +1