How to Use In-App Messaging in Agiloop

Created by Matthew Chartier, Modified on Wed, 1 Jul at 8:18 PM by Matthew Chartier

Agiloop includes a built-in messaging feature that lets your project team communicate directly within the platform, keeping conversations connected to the work at hand. Instead of switching between external tools, you can discuss features, share updates, and coordinate with teammates without ever leaving your project.


What Messaging Is For


In-app messaging is designed for team communication within a specific project. It is ideal for:


  • Discussing feature requirements or priorities with your team
  • Sharing quick updates about build progress or blockers
  • Asking questions tied to specific project decisions
  • Keeping a record of team conversations alongside your feature work


Only members of a project team can see and participate in that project's messages, so conversations stay relevant and secure.


Who Can See Messages


Messages are visible to all members of the project team, regardless of their role (owner, admin, maintainer, or member). If someone is not a member of the project, they will not have access to its messages. To add someone to the project team, invite them via email or a team invite link from your project settings.


Opening the Messages Panel


The messages panel is accessible from the header area of the application. Look for the messaging icon in the header — if you have unread messages, a badge showing the unread count will appear on the icon.


  1. Click the messaging icon in the header.
  2. The messages panel will open, displaying your existing message threads for the current project.
  3. Threads with unread messages are indicated so you can quickly see what needs your attention.


Note: The unread count badge updates in real time, so you will always have an up-to-date view of new activity.


Creating a New Message Thread


To start a new conversation with your team:


  1. Open the messages panel by clicking the messaging icon in the header.
  2. Look for the option to create a new thread (typically a compose or new message button within the panel).
  3. Give your thread a subject or title to help teammates identify the topic at a glance.
  4. Type your opening message in the text field.
  5. Send the message to create the thread and notify your project team members.


Organizing conversations into threads keeps discussions focused and easy to follow, especially as your team grows.


Sending Messages


Once you are inside a message thread, sending a reply is straightforward:


  1. Click into the message input field at the bottom of the thread.
  2. Type your message.
  3. Press Enter or click the send button to post your message to the thread.


All project team members will be able to see your message when they next open the messages panel.


Viewing Message History


All threads and their full message history are stored and accessible from the messages panel. To review past conversations:


  1. Open the messages panel from the header.
  2. Browse the list of threads — each entry shows the thread subject and a preview of the most recent message.
  3. Click on a thread to open it and scroll through the full conversation history.


There is no need to worry about losing context — previous messages remain available so new team members or anyone catching up can review the full discussion.


Marking Messages as Read


When you open a thread and view its messages, Agiloop tracks your read status so the unread badge stays accurate. To clear your unread indicators:


  • Open the messages panel and click into any thread that shows unread messages.
  • Reading through the messages in a thread marks them as read for your account.
  • Once all threads have been viewed, the unread count badge on the header icon will clear.


Note: Read status is tracked per user, so marking messages as read on your account does not affect what your teammates see as unread.


Tips for Effective Team Messaging


  • Use descriptive thread titles so teammates can find relevant conversations quickly without opening each one.
  • Keep threads focused on a single topic or feature to avoid long, hard-to-follow discussions.
  • Invite team members first — if a colleague is not yet on the project team, they will not receive messages until they are added via project settings.
  • Check the messages panel regularly — the unread badge in the header makes it easy to see when there is new activity, but it is a good habit to check in when starting your work session.

Related Articles:


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article