Short answer
A notification setup for a print farm has to answer three questions: which events matter, who needs to know, and which channel gets there fastest. Errors and finished prints should reach a phone at once; informational events belong in the in-app feed. In AMENT Hive the in-app feed, phone notifications and a Discord or Slack channel work today; Telegram and WhatsApp need setup, and e-mail is not switched on yet. Operators use the Shop floor screen on their phones, and the workshop TV shows a live printer board.
Key takeaways
- Sending every event to everyone ends with nobody reading alerts; split them by severity and by role.
- In Hive the in-app feed, phone notifications and Discord/Slack work; Telegram and WhatsApp need bot setup, and e-mail waits for the Resend setup.
- You can ask the farm questions from Telegram and WhatsApp, but approvals happen only in the Hive app.
- The Shop floor screen lives on the operator's phone: plate cleared, done (good count), failed (reason) in one tap.
- The TV wallboard shows printer status only; no orders, customers or settings, and it cannot change anything.
Why does information get lost in a print farm?
As a farm grows, the most expensive loss is usually not a breakdown but a waiting printer. A print that finishes at 2 am keeps the printer busy until someone clears the plate in the morning. A part that comes loose in the afternoon makes spaghetti for two hours before anyone notices. The information existed; it just did not reach the right person.
The opposite is a problem too. Every printer's app sends its own alerts, screenshots circulate in the team's WhatsApp group, and after a while everyone mutes their phone. Alert fatigue is more dangerous than no alerts at all, because a real failure gets lost in the noise.
- Waiting printers: a finished print goes unnoticed, the plate is not cleared, the next job does not start.
- Failures noticed late: filament and machine hours are wasted and due dates slip.
- Scattered channels: each brand has its own app, and nobody knows who has seen what.
- Noise: unimportant alerts drown out the important ones.
The answer is not more alerts but better-routed ones: the right event, to the right person, on the right channel, plus one shared screen where everyone sees the same picture. Below we cover the general principles first, then how Hive sets this up.
Which event should go to whom, and on which channel?
A good setup splits events by severity and makes sure each role gets only what concerns its own work straight away. The table below is a starting point; adapt it to your shifts.
| Event | Severity | Who needs to know | Suggested channel |
|---|---|---|---|
| Printer error, paused with an error | Error | Operator, production manager | Phone notification, Telegram |
| Camera saw a suspicious print | Error | Everyone on the floor | Phone notification |
| Print finished, plate needs clearing | Info | Operator on shift | Phone notification, Shop floor screen, TV |
| Connector went offline | Warning | Owner, technician | Phone notification, team channel |
| Filament running low | Warning | Owner, production manager | In-app, team channel |
| Maintenance due | Warning | Technician | Phone notification |
| Order changed in the store | Warning | Production manager | In-app |
| Slicing finished | Info | Whoever prepared the file | In-app |
Two rules help. First, only errors justify waking someone at night; the rest can be read in the morning. Second, the team channel (Discord or Slack) is for events everyone should see but nobody owns alone, such as a Connector going offline.
How to avoid alert fatigue
- One event, one fast channel: sending the same alert to phone, Telegram and the team channel is three times the noise; pick one fast channel per event for each person.
- Leave information in the feed: events like "slicing finished" should not pull anyone to their phone; let them sit in the in-app feed.
- Name an owner: decide who takes a Connector alert that lands in the team channel, or everyone will assume someone else is looking.
- Review once a month: look at the alert types you dismiss without reading; either switch them off or raise their severity threshold.
Notification channels in AMENT Hive
AMENT Hive writes every event to the notification feed inside the app first; the bell always shows everything. External channels only decide what leaves Hive. Here is where each channel stands:
| Channel | Status | How to turn it on |
|---|---|---|
| In-app feed | Live | Nothing to set up; the bell icon. |
| Phone and browser notifications | Live | Turn on for the device in Settings → Notifications. On iPhone, first add Hive to the Home Screen from Safari (iOS 16.4 or later). |
| Discord / Slack team channel | Live | The farm owner pastes an incoming webhook address. |
| Telegram | Needs setup | Once Hive's Telegram bot is set up, via Connect Telegram. |
| Needs setup | Once a WhatsApp Business account is set up, with your number and a 6-digit code. | |
| Not switched on yet | Will open once the e-mail sending service (Resend) is set up. |
Phone notifications do not need a separate store app: Hive runs as a web app you can install on your phone, complete with a bottom tab bar. App Store and Google Play apps are on the way; the iOS app has been written but not yet submitted, and the Android app is being built.
Per-person preferences
In Settings → Notifications each person chooses which event types reach them on which channel, and from which severity up. Quiet hours can be set: during that window phone, Telegram and WhatsApp messages are held back, and errors can still come through if you want. That is how an operator gets night-time errors while the owner gets only the essentials, instead of one setting for the whole team.
Asking the farm from Telegram and WhatsApp
Once you link Telegram or WhatsApp, the same chat is not only for alerts but for questions too. Type "Is B6 done?", "Any printer with an error?" or "Which prints run overnight?" and Hive's assistant answers with your role in the farm and the farm's real data.
When a draft comes back, such as a print proposal or a plate layout, the chat does not ask you to approve it. An Open in Hive button appears under the message; every approval, including upload and start, happens only in the Hive app. The only buttons you will see in the chat are quick replies.
- Your role applies: the chat works with the farm role of the person who linked the number or account.
- No customer names: chat channels hide customer names too.
- Budget: questions count against the farm's monthly AI budget, the same as the in-app assistant.
- WhatsApp's 24-hour rule: Hive can reply freely within 24 hours of your last message; outside that window it can only send approved alert templates, so by default only warnings and errors go out.
You can also reach the same data from an external AI app such as Claude; we cover that in connecting Claude to your print farm.
The Shop floor screen for operators
Notifications tell you something happened; the Shop floor screen tells you what to do. Operators land on it as soon as they sign in to Hive. It is designed for a phone: one card per printer, sorted by urgency, with a summary at the top such as "3 printers need you now".
Each card shows what is on the plate and what is next. Three taps cover most of an operator's work:
- 1
Plate cleared
When a print finishes the card says "Print finished, clear the build plate". The operator clears it and taps Plate cleared; Hive will not start a new print on that printer until the plate is confirmed clear.
- 2
Done (good units)
When the printer reports the end, the card asks "How many came out good?". The operator enters the good count; anything short is planned again.
- 3
Failed (reason)
If the print failed, the operator picks the reason from a list: did not stick, spaghetti, clog, layer shift and others.
Hive never marks a print done by itself; a person confirms what the printer reported. A plate for an order that was cancelled or put on hold in the store shows on the card with a do-not-print warning. We explain how these records turn into a quality report in print failure detection and quality.
The Shop floor screen works hand in hand with shift-aware planning. Hive can place long prints in the evening so they run overnight while nobody is there. When the morning operator opens their phone, the first cards are the prints that finished overnight: "Clear the plate" and "How many came out good?" They know where to start, and the next plates can begin without waiting.
The TV wallboard: one shared picture of the floor
A TV in the workshop lets people see the state of the floor without looking at their phones. In Hive you create a display link on the Displays page, open it in the TV's browser and leave it running.
- What it shows: each printer's state (printing, idle, error, maintenance, offline), progress and time left, a clear-the-plate prompt, upcoming plates and the Connector's status.
- What it does not show: orders, customers, settings. Anyone with the link sees printer status only and cannot change anything.
- Copes with outages: if Hive cannot be reached, the screen keeps showing the last data with a banner.
- Large farms: when printers do not fit on one screen, it pages through them.
- Link management: you can get the link again later with Show link, or make a new link if needed; the old one stops working at once.
In practice a few small details make a difference. Hang the screen on a wall that faces the printers and is visible as you walk in, and do not pick a TV too small to read from across the room. Turn off sleep and screensaver settings on the TV or browser stick, and put the browser in full screen. Agreeing at the start of each shift who gets up when the screen shows an error matters as much as the screen itself.
Team roles: who sees what, and who approves what?
For notifications to work, permissions need to be clear too. Hive has five roles, and each role's permissions are checked on the server, not merely by hiding a button on screen.
| Role | What they do |
|---|---|
| Owner | Everything: team, team channel, camera watch settings, starting prints, remote commands. |
| Production manager | Approves the plan, starts prints, manages filament stock and display links, invites operators and technicians. |
| Operator | Records plate cleared, done and failed on the Shop floor screen; requests uploads to printers. |
| Technician | Manages maintenance tasks and intervals, puts printers into maintenance. |
| Viewer | Reads everything, changes nothing. |
Starting a print is always a separate approval by an owner or production manager, and the AI cannot do it from any channel. We describe how remote pause and stop are protected in remote printer control.
Setting up notifications and screens, step by step
- 1
Invite the team
Invite everyone from Settings → Team with the right role. Until e-mail sending is switched on, copy the invitation link and pass it on yourself.
- 2
Turn on phones
Everyone turns on notifications for their own device in Settings → Notifications and tries Send test notification.
- 3
Choose types and quiet hours
Errors and finished prints for operators, warnings for the owner; quiet hours at night with errors still coming through.
- 4
Connect the team channel
The owner pastes the incoming webhook address from Discord or Slack and sends a test message.
- 5
Set up the workshop TV
Displays → new display; open the link in the TV browser and go full screen.
You can try Hive free for 14 days, no card needed, and we can do the first setup together if you like. See plans and pricing here.
Frequently asked questions
Can a 3D printer send a phone notification when a print finishes?
Many printers' own apps can, but different brands need different apps. AMENT Hive gathers print-finished and error events from all your printers into one phone notification setup; adding Hive to your phone's home screen is enough.
Does Hive send Telegram and WhatsApp notifications?
Yes, but both need setup: Hive's bot for Telegram, and a WhatsApp Business account for WhatsApp. Once set up, each person links their own account and can ask the farm questions in the same chat.
Can I start a print from Telegram?
No. You can ask questions and request a print proposal from Telegram and WhatsApp, but approvals happen only in the Hive app. The chat sends you to the proposal with an Open in Hive link.
Does Hive send e-mail notifications?
Not yet. The e-mail channel has been designed but will open once the e-mail sending service is set up. Today, phone notifications, the in-app feed and a Discord or Slack channel work.
Does the TV wallboard show customer information?
No. The TV screen shows printer status, Connector health and upcoming plates only. It holds no order, customer or settings information, and nothing can be changed from it.