Attik Update - AI-powered Report Help, Agreement Template Updates & Calendar Scheduling Improvements

March 13th, 2026

AI-powered report help is now available directly inside supported report views.
Calendar scheduling got a broader set of upgrades, including recurring-event controls and stronger visibility improvements.
Agreement workflows now split more cleanly between required initials and smarter template behavior.
Teams can manage payment setup, sample reports, and bundle discount display with clearer settings controls.
Workorder, quote, and report workflows picked up several meaningful quality-of-life updates.

What changed: Supported report views now include AI Agent Assist, giving agents in-context help while reviewing a report.
Before: Agents had to interpret report details on their own or switch between the report and outside notes to explain findings and next steps.
Now: Agents can open AI Agent Assist, ask questions about the report, and launch help directly from report sections and supported defect views.

Why it matters: This makes report walkthroughs faster and gives agents more confidence when explaining findings to clients.

What changed: New calendar settings options give teams more control over how calendar information is displayed and managed.
Before: Teams had fewer settings-based ways to tailor the calendar experience to their scheduling preferences.
Now: Calendar-related visibility and scheduling controls are available through dedicated settings options.

Why it matters: This makes the calendar easier to tune to each team's workflow instead of relying on one default experience.

What changed: The calendar now supports broader recurring-event management and cleaner event editing behavior.
Before: Recurring event changes were more limited, and teams had fewer ways to manage event-series updates cleanly.
Now: Teams can work with recurring events more cleanly and use improved edit and delete options for event series. Durations can now be changed from the calendar by clicking and dragging a block.

Why it matters: Scheduling changes are easier to manage without as many workarounds in the day-to-day event flow.

What changed: Agreement templates can now require initials before a client signs.
Before: Teams could require a signature, but had fewer ways to make clients actively acknowledge specific sections inside the agreement.
Now: Templates can include initials requirements so clients must complete those fields before signing.

Why it matters: This gives teams a clearer way to capture acknowledgment for important sections without relying on a single final signature alone.

What changed: The Payment Settings experience is now available with setup areas for Guardian Payments and Pay at Close.
Before: Payment settings were not available in the same usable way for teams trying to manage payment configuration.
Now: Teams can access Payment Settings, review Guardian Payments, and configure Pay at Close from the settings area.
Why it matters: Payment configuration is easier to find and manage in one place.

What changed: Teams can now manage Sample Reports more intentionally from settings.
Before: Example-report workflows were more limited for teams trying to maintain polished reports for sharing and demonstration.
Now: Teams can search for eligible reports, add them as samples, and manage that sample-report list from one place. Sample reports also anonymize the data from the selected inspection.

Why it matters: This makes it easier to keep useful example reports ready for training, sales, and implementation conversations.

What changed: Agreement templates now support Primary Only behavior and templates that do not lock reports.
Before: Agreement behavior was less flexible when multiple services were on a job, and teams had fewer controls over which agreements should affect report access.
Now: Teams can configure some agreements to apply only to the primary service and allow others to exist without locking report access.

Why it matters: This reduces unnecessary signing friction and gives teams more control over how agreements behave in real-world service combinations.

What changed: Email templates can now be marked with Enable manual send.
Before: One-off email send pickers could surface templates that were not meant for manual sending.
Now: Teams can turn manual sending on only for the templates that should appear in activity and worklist email pickers.

Why it matters: This keeps manual send lists cleaner and helps staff choose the right template faster.

What changed: The Show bundle discount vs primary fee setting now lives in Scheduling Settings.
Before: Bundle discount display behavior was less clearly managed and not centralized in the scheduling settings area.
Now: Teams can control whether bundle discounts are shown against the primary fee from a dedicated settings toggle.

Why it matters: This gives companies clearer control over how bundled pricing is displayed in the places their team uses most.

What changed: Report and quote-related presentation picked up improvements across PDF export, report headers, and related user-facing cleanup.
Before: Export and presentation flows had more rough edges across some report and quote experiences.
Now: Teams benefit from cleaner export behavior and better report presentation in supported areas.
Why it matters: This improves the polish of customer-facing outputs and internal review workflows.

What changed: Required reports no longer force a Spectora template to stay attached once one has been selected.
Before: After choosing a Spectora template on a required report, teams could get stuck without a clean way to remove it.
Now: Teams can unset the Spectora template when a required report should no longer be tied to one.
Why it matters: This prevents configuration dead ends and makes required report setup more flexible.

What changed: Payment-related totals were corrected in batch and related views.
Before: Refunded payment totals and related rollups could display misleading values.
Now: Payment totals use the corrected values from the backend calculations.
Why it matters: Teams can trust what they are seeing when reviewing payment and batch information.

What changed: The send-quote popup in Online Scheduler no longer shows a Draft label where it created confusion.
Before: The popup included draft wording that did not fit the intended send flow.
Now: The popup is cleaner and more aligned with the actual action being taken.
Why it matters: This removes friction at a point where users are trying to send quickly and confidently.

What changed: Service update behavior was corrected so settings changes are more reliably reflected.
Before: Updating a service could fail to fully populate or reflect the expected information.
Now: Service update flows are more dependable.
Why it matters: This reduces confusion when teams are editing service configuration.