01
Shared farm-wide team chat
Every active member of the farm can post to and read a shared channel, keeping team-wide coordination visible to everyone who needs it.
Team Communication
Coordination that lives next to the records it’s about.
Boma gives every farm a shared team chat, private direct messages between members, and a direct support channel to the Boma team, so coordination does not scatter into a separate messaging app disconnected from the work.
Farm-wide channel
Every active member sees the same shared team conversation.
Direct messages
Private one-on-one conversations between specific team members.
Built-in support
A direct channel to Boma support without leaving the app.
Team Communication
Farm Chat
Team-wide and direct messages, together
A shared farm channel keeps the whole team aligned, while direct messages support one-on-one coordination without leaving the platform.
Product screenshot placeholder
What This Feature Does
In plain terms
Team Communication keeps day-to-day coordination inside the same system as the records it’s actually about, instead of splitting across a separate group chat app. Every farm has a shared team channel visible to all active members, so an announcement, a question about an animal, or a heads-up about a schedule change reaches the whole team in one place.
For conversations that do not need the whole team, direct messages let two members coordinate privately without leaving the platform — a manager checking in with a specific worker, or a worker asking a vet a quick follow-up question, without cluttering the shared channel.
On top of internal coordination, every farm has a support conversation with the Boma team directly inside the app. A question about the platform, a billing issue, or a request for help does not require finding a separate email address — it becomes a tracked conversation an admin can respond to.
Key Capabilities
What you actually get
Each capability below is available today inside Boma, not a roadmap promise. Together they form the working core of this feature.
02
Private direct messages
Team members can message each other one-on-one for conversations that do not need to go to the whole farm.
03
Direct line to Boma support
Every farm has a support conversation with the Boma team built into the app, tracked with an open or closed status.
04
Connected to notifications
Relevant activity across the farm — not just messages — surfaces through the same notification system members already check.
05
Admin-side support inbox
Support conversations from any farm land in a dedicated inbox for the platform team, so nothing gets lost in a shared email inbox.
06
Membership-based access
Only active members of a farm can see and participate in that farm’s team chat, keeping conversations scoped to the right people.
Why It Matters
The operational cost this feature actually removes
When farm coordination happens in a separate chat app, it disconnects from the records it is actually about. A question about an animal gets asked in a group chat that has no idea what animal records exist, and the answer, once given, is not attached to anything — it just scrolls away.
Keeping communication inside Boma means coordination and records live in the same context. It also means the farm is not dependent on a third-party app’s availability, privacy practices, or notification settings for something as basic as talking to the platform they run their operation on.
Coordination stays connected to the work
Conversations happen in the same place as the records they reference, rather than a disconnected app.
No dependency on a third-party chat tool
The farm is not relying on an outside app’s reliability or privacy practices for basic coordination.
Support requests are tracked, not lost
Questions to the Boma team become a real conversation with status, not an email that might go unanswered.
Communication scoped to the right people
Farm chat is only visible to active members, avoiding the sprawl of an open group chat with former staff still in it.
Use Cases By Role
How each person on the farm actually uses this
Boma is built around real farm roles. Here is how this feature shows up differently depending on who is signed in.
Owner
Sends a farm-wide update
An owner posts a schedule change or an announcement to the shared team channel, reaching every active member without a separate group text.
Manager
Coordinates privately with one worker
A manager sends a direct message to a specific worker about an assignment, keeping the conversation out of the shared channel where it is not relevant to everyone else.
Worker
Asks a quick question without leaving the app
A worker with a question about a task posts to the team channel or messages a manager directly, without switching to a separate messaging app.
Vet
Responds to a farm’s question between visits
A vet added to the farm can answer a quick question through direct message without needing to schedule a call for something minor.
Admin
Responds to a support conversation from the inbox
A platform admin sees a new support message from a farm in the admin inbox, replies directly, and can mark the conversation resolved once the issue is handled.
How It Works
Step by step, in practice
Communication inside Boma follows a simple structure depending on who needs to see it.
- 1
A message is written
A team member composes a message to the shared farm channel, a specific colleague, or Boma support.
- 2
It reaches the right audience
Farm-wide messages reach every active member; direct messages stay private between the two participants.
- 3
Notifications surface new activity
Relevant participants are notified of new messages through the same system used for other farm alerts.
- 4
Support conversations get a response
Messages sent to Boma support land in the admin inbox, where a platform admin can reply directly.
- 5
Conversations remain available for reference
Past messages stay accessible, so context from a prior conversation is not lost once it scrolls out of view.
Data & Control
Who can see it, who can change it, and who is accountable for it
Farm team chat and direct messages are scoped entirely to the farm and the individuals involved — a farm’s team channel is not visible to any other tenant, and a direct message is only visible to its two participants and, where relevant, platform admins for support purposes.
Support conversations sit in a distinct space from internal farm chat: a farm’s support thread with Boma is visible to that farm’s members and to platform admins, but never to other farms, keeping platform-level support separate from a farm’s private internal coordination.
Farm-scoped team chat
A farm’s shared channel is only visible to that farm’s active members.
Private direct messages
Direct messages are visible only to the two participants involved.
Separate support channel
Support conversations with Boma are distinct from internal farm chat and visible to platform admins.
Membership-based access
Losing farm membership removes access to that farm’s team chat going forward.
Business Outcomes
What changes operationally once this is in place
These are the practical shifts farms describe once the feature is part of daily use, not a marketing estimate.
Coordination stays in context
Conversations happen alongside the records they concern, not in a disconnected app.
Support requests get tracked
Questions to the Boma team become a real, followable conversation instead of an easily lost email.
Less coordination overhead
One place to talk to the team removes the friction of managing a separate chat app.
Cleaner handoffs
Direct messages and team chat stay available for reference instead of vanishing into a scroll history elsewhere.
Questions
Common questions about this feature
Specific answers for teams evaluating whether this part of Boma fits how the farm actually runs.
Can workers see direct messages between other team members?
No. Direct messages are private to the two participants involved. Only the shared farm team channel is visible to all active members.
Is the support conversation with Boma visible to other farms?
No. Each farm’s support conversation is private to that farm’s members and platform admins, never visible to other tenants.
What happens to team chat access when someone leaves the farm?
Once a member’s access to the farm is removed, they lose visibility into that farm’s team chat and direct messages going forward.
Do we get notified of new messages, or do we have to check manually?
New activity surfaces through Boma’s notification system, so relevant team members are alerted rather than needing to check the chat proactively.
Can a vet who is not a full-time team member use direct messages?
Yes, as long as they are added as a farm member with an appropriate role, they can participate in direct messages and the shared team channel for the duration of their involvement.
Related Features
Works alongside the rest of the platform
Ready To Try It
Keep farm coordination where the work actually happens.
Start free and bring your team’s day-to-day communication into the same system as your records.