![](/s/cache/58/16/58166247e5d4537e57e5f7c8fcc58c63.png)
+3
Under review
Are we giving too much information in our notifications?
When we do alerts through the notifier on the NOW apps, we find that frequently there is not enough space in the headline, and the full summary frequently gives enough information that there is little incentive to click through.
What if ... instead, we eliminated the summary field in the alerts and allowed the headlines to wrap? That way users would see the full headline and we wouldn't have to rewrite them for the alerts.
![Image 472](/s/attachments/10530/1/0/bdabe0bc8d92e518cee04c787a5b516b.jpg)
Customer support service by UserEcho
This would indeed solve the problem with the wrapping headlines. I am a bit nervous about this because in terms of the interface, it would be a bit confusing to the reporter / admin user. They would need to know that in this specific case, the headline was the message and the message wasn't used. If they wanted to re-write the headline to be more specific, they would need to know that the headline wasn't the headline, but the headline was the message.
In the "code" it is sending the "title" and the "message." The title is optional. But, I would feel uneasy making the "message" the title in just this one case, if that makes sense.
In addition, it is possible that Apple could change the display of the message in the future, and the fact that we've changed the meaning of "title" and "message" could backfire.
That being said, I agree with the premise of your post. I will talk to our dev team to see if they have any ideas on how we can communicate this clearly.