In the Contact Form app email template, the field ids get replaced with values in Subject and Message but not replaced in the Sender Name - see the screenshot below. Anyparticular reason why Sender Name is not treated like all other parameters when parsing it for [field-id]? When these are sent it is essential to have the sender’s info in that field so the help desk system handles the incoming case correctly. Is this something you could make work? TIA!
@Serge1 thanks a lot for leaving your request and for all the details!
I’m really sorry that it’s not obvious, but at the moment there is no option to add field id to the Sender Name
I know that the dev team were discussing this very opportunity, and this request was taken under further consideration. Unfortunately, I don’t have more concrete info for the moment, but I’ll make sure to keep you updated on the progress in this thread.
Regarding the previous Relased topic, I must explain that it refers to the previuos version of the widget when there was no option to change the Sender Name, and all the submissions were sent from ‘Elfsight Courier’. I’ve adjusted the title so that it’s not that confusing.
Thanks a lot for your help, we’re always happy to hear from you!
Hi, can you give an indication when this will be up? I see this request is from 1.5 year ago and it is a quite important feature for multiple clients already. Hope its up soon, thanks!
Much as I’d love to share an update, unfortunately, we can’t provide the ETA for this feature at the moment. I am really sorry
I do understand your concerns and agree that this feature is really important. However, the prioritization of requests is influenced by two main criteria: complexity and the number of votes.
At the moment, we have many higher-priority requests that our developers are actively working on. You can check it here
Once we receive any news regarding this feature, we’ll promptly inform you here.
Hello everyone, do we have any advance with this topic? I am really disapointed that so fine and almost perfect Contact form is lacking so simple feature. Moreover when I paid year subscription and found this glitch. I understand your priorities but changing this is about rewriting one line in the code to read text from the variable of field.
Thank you and hopefully you will change your approach with this case.
Thanks so much for taking the time to share your thoughts with us. We really appreciate it!
Right now, we don’t have any updates on this feature — I’m really sorry about that. I completely understand why this would be helpful, and I agree that automatically pulling the name from the submitted form into the Sender field would make things a lot easier.
We realize that some improvements may seem simple from the outside, but in reality, things are often more complex. Also, our devs prioritize requests based on how many votes they receive. This helps them focus on what the community needs most.
However, we’re hopeful this idea gains more traction, and once there’s any news, we’ll be sure to update you here
After a thorough investigation and testing, we’re sorry to inform you that we won’t be able to implement this idea.
What are the reasons?
The Sender Name isn’t just a signature — it’s part of the email subject line that spam filters analyze. If the sender’s name changes from one email to the next, it can cause a few issues:
Frequent changes in the sender name with the same IP address are a common red flag for bulk spam. Providers like Gmail, Outlook, and others are trained to detect these patterns.
We can’t control what users enter in the form fields. Even with the “Elfsight -” prefix, someone could write something like “Elfsight - URGENT: Your account suspended,” and the email would be sent with that name from our domain.
This could lead to our IP being blacklisted, which would affect all Form users, not just one.
For these reasons, the Sender Name must currently be a fixed string that the widget owner can set in the settings.
We hope this clears up the reasoning behind the decision, and we truly appreciate your understanding
