One way is that you use a separate table. Add the messages to this table in the trigger, for example:
INSERT INTO Messages (...) VALUES (.., 'Something from the trigger')
And after the operation is done, read the contents of the table from the client.
However, based on your example you should not create a design like this to get confirmations from client. The basic rules of ACID is that conversations with the user go like this:
1. Validity checks, possible questions
2. start transaction
3. execute dml operations
4. commit/rollback
5. inform the user
So there's no conversation, never, with the user while the transaction is active. If this golden rule is broken, you'll end up to serious locking based problems.