Subject line set is not the subject line displayed | Community
Skip to main content

Subject line set is not the subject line displayed

  • April 16, 2024
  • 10 replies
  • 0 views

Mia12

Hi - We have multiple macros with a subject line written as part of the triggers/actions such as this one.

Set subject > [Subject line we set]

 

When we send out proactive tickets using any of these macros, it doesn't follow the subject line we set in the macro's trigger/actions, instead, it shows the first few sentences of the email body. The same thing happens when we freehand an email and set a subject in the Subject field prior to sending the email.

 

Anyone who can help me figure it out? We've gotten feedback from customers who said our emails are confusing, I think this is the reason why.

 

 

10 replies

Mia12
  • Author
  • April 16, 2024

For context, this is what I was referring to about the triggers/action:

And this is how it looks like when our customers receive our emails:

 


Steve25
  • April 17, 2024

Hi Mia,

Open the events tab within the ticket and look for a trigger that may update the subject line.  You can then either disable or update the trigger to disregard when the macro is used (add a tag with the macro).


Mia12
  • Author
  • April 17, 2024

@steve25 - Thank you. I just checked and saw the trigger so I went in. 

Do you mean I should remove this tag in the Email subject field?


Mia12
  • Author
  • April 17, 2024

I tried to remove the {{ticket.title}} tag and sent an email, the email I received said (No subject) in the subject line.


Steve25
  • April 17, 2024

{{ticket.title}} is the placeholder that pulls the subject line for the ticket. You want to keep that one as it is.  Is there another trigger that fired to update the subject and overwrote that one with the undesired subject? 


  • April 18, 2024

This is an odd issue.

 

I agree with Steve. If a trigger is setting the subject of the ticket, then your notification is sending with ticket title. It should work.

 

I would check the order in your events. Is it a macro or trigger setting the subject? Is that macro or trigger running before the notification is sent? Otherwise it could be that the notification is being sent before the subject is being set.

 

Notification triggers should normally be last in your trigger order, that way all the logic runs on your ticket first. Then people are notified about it.


Brandon12
  • April 22, 2024

Hey Mia,

 

I would suggest opening a support ticket with Zendesk.  I've tested the workflow in my developer account and it is working as intended, so something in your instance must be having an unintended impact.  Let us know here if you get it resolved!

 

Brandon


  • March 6, 2025

I have the same issue - did you found out what was the issue?


  • June 3, 2025

Is the Subject field set to be visible to end users? If not, looks like that may be the cause: https://support.zendesk.com/hc/en-us/articles/4408827535770-The-ticket-title-placeholder-displays-first-comment-instead-of-the-subject

 


Elaine14
  • June 7, 2025
Hi Jamie,
 
Thanks for pointing this out. The reason the Re: [Community Post] Subject line set is not the subject line displayed placeholder shows the first comment instead of the subject is because the Subject field is not visible to end users in the account. When the Subject field is disabled or set so that only agents can edit it, end users won’t see the subject, and the placeholder instead displays the ticket’s first public comment.
 
To resolve this, ensure the Subject field is visible to end users. Also, when a ticket has no public comments, the placeholder will display "Untitled Ticket," so it’s important that the ticket has at least one public comment as well.
 
You can find more details on reactivating the Subject field here: Deactivating and reactivating ticket fields.
 
I hope that helps!