Summary

• Thumbtack: Demo mode and sample reports let you run Thumbtack in test mode and save reports as samples for prospects.

• Payments: Guardian batch filtering, fee-aware refunds and voids, and more reliable refund processing improve how you manage and review payments.

• Scheduling and reports: Max square footage is enforced for online booking, flat-rate modifiers support piece pay, repair lists support view links and filtering, and required report types can be soft-deleted.

• Images in Emails: Images can now be added into email templates and linked to specific URLs you’d like to redirect clients/agents to.

New Features

Thumbtack Demo Mode and Sample Report

• What changed: You can run Thumbtack in a demo/test mode and save existing reports as sample reports for sharing with prospects.

  https://www.attik.ai/settings/sample-reports

  

• Before: Thumbtack ran only in live mode; there was no way to mark or reuse a report as a sample.

• Now: Test mode is available for Thumbtack, and you can save a report as a sample and list samples for your company. Sample reports are handled so they don't trigger inspection checks.

• Why it matters: Demos and sales conversations can use real-looking sample reports without affecting live inspections or quotes.

New Spectora Job Flow For Stand Alone

• What changed: In preparation for transition to Attik standalone, a minimal Spectora integration will create jobs in Spectora with address, inspector, and report templates only, and stores the Spectora job ID on the inspection.

• Before: Spectora job creation required full service matching and a heavy payload.

• Now: When you create a job in Attik standalone the integration will create a Spectora job with just the essentials. Templates are driven from Attik, and the Spectora job ID is saved on the inspection for later sync and linking. Cancelled inspections can trigger cancellation of the linked Spectora job.

• Why it matters: Standalone and lighter integrations can go live without full service parity, and Attik stays in control of which report templates are used.

Attik/Spectora Condition in Action Flows

• What changed: Action flows can run only for jobs created in Attik or only for jobs created in Spectora, using a new condition based on job creation source.

• Before: Flows could not be limited by where the job came from (Attik vs Spectora).

• Now: When building a flow, you can add a condition on job creation type (Attik or Spectora) so communications and automations target the right segment.

• Why it matters: You can tailor messages and automations for one source without affecting the other.

Flat Rate as Modifier Type

• What changed: Modifiers can now add a "flat rate" component that feeds into inspector pay, so piece pay can vary by job attributes (e.g. square footage, equipment count, units) instead of only by price.

• Before: Modifiers affected cost, time, equipment, and admin only; flat rate pay came from service or inspector settings, not from modifiers.

• Now: In service settings you can choose "flat rate" as a modifier add type. That modifier contribution is used in payroll so inspector pay reflects piece-rate rules (e.g. per sq ft, per unit).

• Why it matters: Companies that pay by piece or by job attributes can align pay with their rules without workarounds.

Email Image Block Clickable Links

• What changed: Image blocks can now be added in email templates and can be turned into clickable links, with URL validation so only valid links are used.

• Before: Image blocks in emails were not supported.

• Now: You can assign a URL to an image block so recipients can click through; invalid URLs are caught so emails stay correct.

• Why it matters: Marketing and follow-up emails can use clickable images for clearer calls to action.

Improvements

Contact Stats Role-Level Performance Breakdown

• What changed: Contact and performance stats now break down by role, so you can see how each role (e.g. customer, point of contact) is performing.

• Before: Stats were aggregated without role-level detail.

• Now: You get a role-level performance breakdown in the contact stats aggregation.

• Why it matters: You can evaluate and improve performance by role and tailor follow-up by contact type.

Soft-Delete for Required Report Types

• What changed: When you remove a required report type, it is now soft-deleted (marked inactive) instead of permanently deleted.

• Before: Deleting a required report type removed it entirely, which could break references in services and reports.

• Now: "Delete" sets the type to inactive so it no longer appears in active lists but remains in the system for history and references.

• Why it matters: You can retire report types safely without losing links to existing reports or services.

Repair List Status Filtering

• What changed: On the Repair Lists page, you can now filter repair lists by status (e.g. pending, complete) and view them in smaller, manageable pages instead of one long list. When you need to know how many items you have, you can show a total count.

• Before: Long repair lists were hard to scan, and you couldn't narrow the list by status—so you had to scroll through everything to find what you needed.

• Now: Filter by status to see only the repairs you care about, and move through the list page by page. You can optionally see the total number of items so you know how many repairs match your filter.

• Why it matters: You spend less time scrolling and searching. You can work with large repair lists without slowing down and stay focused on the statuses that matter to you.

Repair List View Link Sharing and Repair-Addendum Role

• What changed: You can send a view link for a repair list to selected contacts and extra email addresses. A new "repair-addendum" contact job role is available.

• Before: There was no built-in way to send a view link for a repair list, and the repair-addendum role did not exist.

• Now: A "send view link" action sends a link to the repair list to chosen contacts and emails. The repair-addendum role can be assigned where needed so that agents can create repair addendums in the same place they can create repair lists.

• Why it matters: Sharing repair lists with customers and addendum signers is simpler and role assignment is clearer.

Attik Standalone Scheduler Permission

• What changed: A new permission option was added for scheduling Attik standalone jobs (beta Attik scheduler).

• Before: Scheduler access was not controlled by a dedicated permission.

• Now: Permissions data includes a "beta Attik scheduler" option so you can control who can use the Attik scheduling feature.

• Why it matters: You can roll out or restrict the scheduler by role or user.

Recurrence Settings for Monthly Events

• What changed: The issue with the monthly recurring events not saving has been resolved..

• Before: Monthly recurrence could only be saved for a set calendar date every month.

• Now: Monthly recurrence allows for a set day of the week and a set week of the month variables to be saved.

• Why it matters: Recurring monthly jobs and schedules behave reliably across the app.

Guardian Refund/Void and Batch Improvements

• What changed: Guardian payment batches can be filtered by payment type and date range; refund and void logic is fee-aware and more reliable; and batch details come from your data instead of external calls where possible.

• Before: Batch listing was less flexible; refunds and voids didn't consistently account for fees; some batch data depended on external APIs.

• Now: You can filter batches by type and date. Refunds and voids respect settlement status and fees. Queued refunds are processed automatically when transactions become refundable or voidable. Batch details are derived from stored data for speed and reliability.

• Why it matters: Payment and batch reconciliation are easier and refunds match what you expect.

Bug Fixes

Max Sq Ft Online

• What changed: When a property's square footage is over your "Max Sq Ft Online" limit, the online scheduler no longer allows the customer to pick a time slot or complete the booking; they are directed to contact you for a custom quote.

• Before: Users could sometimes get past the "contact for custom quote" message (e.g. via the summary bar or Next) and still schedule, which could lead to incorrect pricing or bookings over the limit.

• Now: The max square footage check is enforced so that over-limit properties cannot reach the scheduling step in a way that allows slot selection or booking. Backend validation can reject requests that exceed the limit.

• Why it matters: Online bookings stay within your size policy and avoid misquoted or invalid appointments.

Spectora Calendar Hold Block Updates

• What changed: Updates to your Spectora calendar hold block data now finish correctly every time.

• Before: In some cases, those updates could stop partway through, so calendar hold block data in Spectora didn’t always match what you have in Attik.

• Now: Updates run to completion, so your Spectora calendar hold blocks stay in sync with Attik.

• Why it matters: You can rely on Spectora showing the same calendar hold block information as Attik, without manual checks or fix-ups.

Spectora Event Sync Guard Fix

• What changed: When you sync a Spectora job, the system now syncs the related calendar events as well, instead of sometimes skipping them.

• Before: In some cases, event sync was skipped even when a Spectora sync was requested, so Spectora-linked events didn’t always update when the job did.

• Now: Syncing a Spectora job triggers event sync as expected. Only events that aren’t tied to Spectora are skipped, so your calendar stays in line with your Spectora jobs.

• Why it matters: You can trust that events linked to Spectora jobs will update when you sync, so your schedule stays accurate without extra steps.