Gravity Forms
+ Entry SLA Tracker

Give every Gravity Forms entry a response deadline and never let one sit unanswered again. The Gravity Forms Entry SLA Tracker add-on puts a target on each form — respond within so many hours or days — and works out, the moment an entry is submitted, exactly when it is due. From then on the entry carries its deadline everywhere you work: a colour-coded Deadline column in the entry list shows On track, Due soon, Overdue or Met at a glance, and an auditable note records when the clock started.

The clock can count real elapsed time, or it can count your business hours only. Set your opening and closing hours and the days you are open, and the add-on counts the deadline inside that window, skipping evenings, weekends and the days you are closed, all in your site timezone and correct across daylight-saving changes. A "due soon" threshold flags entries that are at risk before they breach, so your team can act in time.

Escalation keeps everyone honest. Bind a notification to the "Entry SLA: due soon" and "Entry SLA: overdue" events and the add-on e-mails them on an hourly scan — once for each level, never a flood. When an entry is handled, one click on Mark resolved (on the entry, or in bulk) stops the clock and records who closed it; reopen it just as easily. Different work can have a different target with optional priority overrides from a field you choose, and an {entry_due_date} merge tag drops the deadline straight into your confirmations and notifications. It is GravityForms-first: there is no third-party service to sign up for, no API key, and the add-on makes no outside HTTP calls at all.

When an entry is submitted to a form with the SLA turned on, the add-on records the submission time and works out the due moment from your target. With the business-hours clock on, it adds the hours only inside your open window on the days you are open, skipping everything else, in the site timezone and correct across daylight-saving changes; with it off, it simply adds the elapsed time. The due timestamp and the rule are stored with the entry, and an auditable "Deadline set" note is added. In the entry list the Deadline column shows the due date and a status worked out live: On track, Due soon once your threshold of the target has passed, Overdue once the due moment is reached, or Met once the entry is resolved. An hourly background scan looks at each form with escalation on and fires the "Entry SLA: due soon" and "Entry SLA: overdue" notification events for entries that have crossed those points, each level once per entry. Mark resolved writes a resolved time that stops the clock (reopening clears it), and the {entry_due_date} and {entry_sla_status} merge tags resolve from the stored deadline. The add-on contacts no external service and makes no outside HTTP request.