Sender Name to replace field [field-id] values

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!

There was a similar request filed earlier where I believe you misinterpreted the original request - Real sender name [an option to set manually] - #8 by Helga


1 Like

@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 :frowning:

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!

I really want this feature, too - it makes things so much easier to handle for the person managing form responses.


Hello there and welcome aboard @user13114 :wave:

We agree that it would be a nice enhancement. We’ll have this idea in mind, and I’ll make sure to update you here in case of any progress.

A huge thank you for pointing us in this direction :slightly_smiling_face:

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!

1 Like

Hey there and welcome to the Community @DNS13_Webservices :wave:

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 :pensive:

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 :slightly_smiling_face:

Once we receive any news regarding this feature, we’ll promptly inform you here.

Thank you so much for your interest and help!