Increase character limit when emailing to Timeline
None
Is there a way to increase the character limit when emailing to TImeline? Or a different alternative to the solution of encountering the limit? I don't like the idea of miles long email chains being logged, but how else can Email to Timeline be used if the chain is long?
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.
I agree with this ask. This is a major ask from our team right now to move more workflows into GS.
We will very soon make the change to truncate characters > 30K and log the email to Timeline.
I had a user who raised this issue as well today. Would be really great to see a fix for it.
Hey team,
This came up for me today as well. Do we have any ETA when this will be released?
Hello Team,
Hoping for an update on the plan to truncate the emails as well. Our team is running into the limit issue as well. Many times there are large paragraphs in our client’s signatures surround privacy policies to stay incompliance with federal and international standards in our space. That adds very quickly to the character limit.
Thank you!
We have not been able to get to it because of other priorities (you would see a lot of new functionalities with Oct release). I will keep you posted once we are able to pick it up.
Hi all, this would also be very helpful to us! We have members on our team who are waiting to log activities until the entire interaction is complete so this would be a helpful update.
Hi Team,
This is a very hot topic at our company too! We just launched Gainsight and our users are struggling to adopt logging their emails to the timeline because of the number of bounce backs they receive for character limits w/ long threads.
Any update regarding timing for this feature would be super helpful!
Thanks!
Allowing for all characters in an email to be sent through the bcc function would be greatly appreciated. The goal of Gainsight is to help us become more efficient and this bcc function definitely helps when able to use it.
Thank You!
If there was a way to only log the most recent email response (vs. the entire thread each time) that would solve the problem, and it would be more accurate from a Timeline standpoint anyway.
Adding another vote to truncate email strings that exceed the limit instead of rejecting them. Our CSM’s run into this frequently, and it is frustrating. Thank you!
I came to give this same feedback but it looks like this has potentially been in the works for about a year. I would love to see emails truncated rather than rejected. Each of our CSM’s manage a book of business between 200-800 customers. When an email is rejected for length and we have to manually shorten it and then forward it to the timeline that extra time really adds up. It is especially frustrating on an email chain with a customer that has already been rejected and you know each new email is going to result in a manual add. Any updates on this since@soumitrasahu posted 7 months ago?
Hello team! This continues to impact our CSMs and present a point of frustration. CSMs presently have to comb through rejected entries and manually shorten their messages several times a day, which is not scalable and discourages the adoption of Gainsight Assist/Timeline. Thank you in advance for the consideration!
Hi Team, Another vote on this from our team as well. A CSM reached again regarding this and we would like something to be done about it.
I did want to mention that a similar thread is happening here on the community. It may be wise to continue to upvote that post to keep the Upvotes condense and increase visibility to the Enhancement.
All the votes from this idea have been transferred.
Thank you@ebell … I merged this idea to the one you cited.