In custom perspectives, you can select ‘Group and sort: Entire Projects’. Then all the parent actions of the actions returned by the perspective will be shown. Everything inside each project is displayed in the original project order.
In customer perspectives that slice through your projects and apply a sort order, with ‘Group and sort: Individual Actions’, you don’t have the context of the parent actions. You have three pieces of information to work with: the name of the action, the name of its project, and its tags. I recommend making sure each action is sufficiently described by these 3 pieces of information.
So in your example you could add ‘…about X project meeting’ to each action name, or add a ‘X project meeting’ tag, but the most obvious change to me is to restructure your projects to make use of the project hierarchy. ‘Arrange a project meeting about X’ is a well-defined outcome and so could be made its own Project. This project name would be displayed next to each ‘Call Person…’ action in “slicing” perspectives.