Beacon
How to use Beacon
Beacon turns a monday.com board into a real SLA tracker. It counts your service targets down in your team's actual working hours, shows a live status and countdown on every item, and notifies the right people before a deadline slips. This guide walks you through setup, then explains how the engine behaves day to day.
On this page
Before you start
- You need an active monday.com account and permission to add apps to it.
- Pick the board you want to track — typically a support, help-desk or ticketing board that already has a Priority status column and a Status column (e.g. New / Working on it / Waiting / Done).
- You'll be an admin of that board to configure Beacon; your teammates just work the board as usual.
Setup, step by step
Install Beacon
Install Beacon from the monday.com marketplace. monday will ask you to authorise it — this is the standard OAuth screen listing the permissions Beacon needs to read your priority/status columns and write the SLA status back. Approve it, and you'll land on a short confirmation page. That's it — no account to create, no password.
Open the “SLA Settings” board view
On your board, add a new view and choose Beacon's SLA Settings view (titled Beacon SLA settings). This is Beacon's control panel. At the top you'll see a short getting-started checklist — Map columns, Set business hours, Set priority durations — that tracks your progress. There is no separate wizard; you configure everything from the tabs here. Opening the view automatically connects the board so Beacon starts watching it.
Map your columns (required)
On the Columns tab, tell Beacon which monday columns to use. In a hurry? Click “✨ Set up columns automatically” — Beacon creates any missing SLA columns and maps them for you, reusing your existing Priority and Status columns rather than duplicating them. Otherwise map them by hand:
| Column | Required | Role |
|---|---|---|
| Priority | Yes | Read — the status column whose labels drive SLA durations. |
| Status | Yes | Read — the status column that drives pause / resolution. |
| SLA | Yes | Write — where Beacon writes the SLA state (On Track, At Risk…). |
| Deadline | Yes | Write — the date column where Beacon writes the breach deadline. |
| Assignee | Optional | Read — a People column used to route the first (60%) notification. |
| Escalation | Optional | Read — a People column used to route the escalation (80%). |
Click Save. The “Map columns” checklist item turns green.
Set your business hours
On the Business hours tab, define when the clock is allowed to tick — this is what makes Beacon fair:
- Time zone — deadlines are computed in this zone.
- Working days — check the days that count (e.g. Mon–Fri).
-
Business hours — an opening and closing time. Set
closing to
00:00for “end of day” (midnight). - Working calendar — click dates to add holidays (exceptional closures) or exceptional openings for one-off days.
A ticket raised Friday at 6pm won't burn its SLA over the weekend — the clock resumes Monday morning.
Set priority durations
On the Priority durations tab, give each label of your Priority column a target — the time before its SLA breaches — in days / hours / minutes. One day equals however many business hours your calendar defines, so targets always mean working time. Leave a priority blank to fall back to the Default target at the bottom, which also covers items that have no priority set.
One target per priority. Beacon tracks a single breach deadline per priority label (not separate response and resolution clocks). Pick the target that matters most to your team — usually time-to-resolution.
Choose pause & resolution statuses
On the Pause & resolution tab, tell Beacon what each label of your Status column means. For every status pick one of:
- Keeps running — normal working status, clock ticks.
- Pauses the clock — a temporary freeze (e.g. “Waiting on customer”). The clock resumes when the status changes back.
- Resolves (stops) — a terminal status (e.g. “Done”). The clock stops for good and the SLA is marked Met.
Beacon suggests sensible defaults from your status names — review them and Save to confirm.
Set up escalation & the daily digest
On the Escalation tab:
- Board escalation recipients — the people notified at the 80% escalation when an item has no per-item Escalation column set. Think team leads or the on-call rota.
- Daily digest — optionally pick an hour to send each assignee one consolidated summary of their at-risk and breached items, in the board's time zone. It's off by default.
Per-item routing (the Assignee and Escalation People columns from step 3) always takes priority over these board-level fallbacks.
Watch it work
Set a Priority on any item and Beacon starts its first SLA. From then on:
- the item's SLA and Deadline columns fill in and update live;
- the SLA Health board view (Beacon SLA Health) gives you a live dashboard of every item — status, countdown and progress bar — sortable by priority, state or time left;
- the SLA Countdown item view (Beacon SLA) shows a single item's countdown, progress bar and full event history (thresholds crossed, pauses, breach, resolution).
Understanding SLA states
Beacon writes one of these plain, colour-coded states to each tracked item:
| State | Meaning |
|---|---|
| On Track | Comfortably within target. |
| At Risk | Passed 60% of the target — the assignee has been notified. |
| Critical | Passed 80% — escalation recipients have been notified. |
| Breached | The deadline passed — assignee and escalation both alerted, and an update is posted on the item as a record. |
| Met | Resolved within target — the clock stopped on a resolution status. |
| On Hold | The clock is paused on a pause status; it resumes when the status changes. |
How escalation timing works
Beacon measures elapsed working time against each item's target and acts at three thresholds — all counted in your business hours:
- 60% → At Risk: the assignee is notified (via the Assignee column, or the person who triggered the clock).
- 80% → Critical: the escalation is notified (per-item Escalation column → board recipients → assignee).
- 100% → Breached: both are alerted and a breach update is posted on the item.
Plans & limits
You can start free and upgrade any time from the Plan tab. Paid plans are billed per seat through monday's own billing.
| Plan | SLAs tracked | What's included |
|---|---|---|
| Free | Up to 25, on 1 board | Core SLA tracking with the native SLA status column. |
| Starter | Unlimited | Everything in Free, plus the custom business-hours calendar, pause & resume, and routed escalation. |
| Pro | Unlimited | Everything in Starter, plus the daily digest, the SLA Health board view, the SLA Countdown item view, and monthly reporting. |
Good to know. The Plan tab shows your usage (“SLAs tracked”) and, on the Free plan, a banner once you reach the 25-SLA limit — new SLAs beyond the limit aren't tracked until you upgrade.
Works in your language
Beacon is available in 15 languages — English, Français, Español, Deutsch, Italiano, Português, Nederlands, Polski, Українська, Ελληνικά, Svenska, Dansk, Norsk, Slovenščina and 中文. Set the language per board on the Language tab; it applies to the board, item and settings views and to the notifications and digest Beacon sends your team. English is the default.
FAQ & support
An SLA didn't start — why?
A clock starts when an item gets a Priority. Check that your Priority and Status columns are mapped (Columns tab) and that the item's priority has a duration (Priority durations tab).
The clock isn't counting down.
Beacon only ticks during business hours. Outside your working days/hours, or while the item sits on a pause status, the clock is frozen by design.
Notifications went to the wrong person.
Routing follows the per-item Assignee/Escalation People columns first, then the board-level recipients on the Escalation tab. Check both.
Can I change the calendar later?
Yes — edit the Business hours tab any time. Open clocks recompute against the updated calendar.
Need a hand? Email support@zolvus.dev — we aim to reply within two business days. See also our Privacy Policy and Terms of Service.