Currently, the email subject and sender name for chat history notifications are fixed. It would be incredibly helpful if both could be customized—especially the subject line.
This would make it much easier to quickly identify incoming chat histories in the inbox, especially when managing multiple websites or clients.
Thank you for considering this!
Manuel, could you share an example where the current fixed fields:
From: notifications@forms.elfsightmail.com
Subject: AI Chatbot: New Chat Transcript
don’t work for you?
For us, it’s been simple to create reliable email filters based on these two fields since they never change.
The transcript emails also include the Chat Page URL, which could be used to filter by web page if you happen to run multiple AI chatbots on your site—though that seems like a rare scenario.
It would be helpful to understand why additional flexibility might outweigh the benefits of this fixed, predictable format.
I also wonder if customization could introduce risks—such as lost transcripts—whenever subject lines or sender names are changed and filtering rules aren’t updated.
Thank you for your reply and the explanation.
Let me share a bit more context on why customizable subject lines and sender names would be valuable for us:
Email Subject – Readability & Workflow Integration
I organize all system-generated emails using naming conventions with suffixes like [TASK]....., [REQUEST]...., etc. For chatbot transcripts, I would use [NEW LEAD].
This helps me quickly scan my inbox—even after days away—and spot the important messages without opening every email.
A fixed subject like “New Transcript” gets buried easily, especially if multiple systems send similar-looking messages.
Sender Name
While keeping the “@elfsight.com” domain is fine, being able to label the sender as “AI Chatbot – Website X” would give immediate context in the inbox.
This is especially useful when running multiple bots across different websites and having all transcripts sent to a central address.
If you have several AI chatbots on different pages but use the same recipient email, custom subject lines help distinguish between sources quickly—without needing to open or filter based on the page URL.
Currently, it seems only one recipient email can be set.
It would be great if multiple addresses were supported (e.g. separated by commas or semicolons), so teams or departments can be notified simultaneously without workarounds.
Hi there and welcome to the Community, @Manuel_Paeth 
Many thanks for such a detailed comment!
Glad to say that this idea is already on the Wishlist and you can upvote it here 
- Ai chatbot Chat History to Email (white label)