Grayson Lievens
My feedback
8 results found
-
72 votes
We see a lot of value in this request and our team is gathering feedback and additional use cases regarding this suggestion.
Please add your comments and support this suggestion so we can prioritize it accordingly. What metadata would you use and what file name format/naming convention you use today?
An error occurred while saving the comment Grayson Lievens
supported this idea
·
-
15 votes
Thank you for your suggestion. We currently don’t have any plans to update the current email notifications flow, but will return to this suggestion later in the year. Please stay tuned!
An error occurred while saving the comment Grayson Lievens
commented
Please add this feature. I get 100+ emails a day currently. Every time a new case gets created in our business a new folder is created and with the salesforce integration it auto collabs the current user to that folder which in turn sends me as the admin an email that they accepted a collaboration invite. It is tremendously annoying. Its also built in a way that I cannot filter these emails out of my gmail inbox. I have literally tried at least 20 different filters and none of them keep the emails out of my inbox. please give us the option to turn this off.
Grayson Lievens
supported this idea
·
-
43 votesGrayson Lievens
supported this idea
·
-
26 votesGrayson Lievens
supported this idea
·
-
3 votesGrayson Lievens
supported this idea
·
-
14 votesGrayson Lievens
supported this idea
·
-
4 votesGrayson Lievens
supported this idea
·
-
15 votes
An error occurred while saving the comment Grayson Lievens
commented
Yes please. This is often the first email we send to our clients regarding Box and we have to warn them that they will get an email that is from us but doesn't look like it is. Really quite a bother.
Grayson Lievens
supported this idea
·
Great news to hear this is being looked into. Our specific use case is pretty simple. we send out things like EZ pay forms that will have customers payment info and a signature, the form we use is called EZ Pay Form. It would be great if we could have the name of the signee getting appended on the back of the form once its signed. Like we send the "EZ Pay From" and it comes back signed as "EZ Pay Form - John Doe" Or we also have an ID called EFIN that all our customers have. It would be great if that number could be appended into the name as well as the name if they have to type it in during the Esign.
Basically, if there was just some way to construct a naming template into the Esign templates we create using the fields that we put on the template that would be great. That way if we have a form we send out for signatures often all signed docs coming from that form could come in a uniform fashion. Like a section that says "Naming convention for Signed forms" and in it we can write out what we want to forms to come back named like. For example if we add a text field on a box sign template that text field is now available for us to use in that new section. And in that section there is a list of default relative values we could use like signed date or user who sent the form. And we could write them out in the section something like this.
EZ Pay Form - {{{Signee 1 Name}}} ({{{EFIN}}}) - {{{Date Signed}}}
So in this example everything in the triple squiggle brackets would be the relative fields like who signed the document or a text field called EFIN and then a default relative value like the date they signed it. In that you could also allow any metadata thats already on these docs to be accessible from this section.