March 6th, 2026

Workorders: You can upload reference files to a work order for inspectors and office staff, and scheduling admins can permanently delete a job when it was created in error.
Contacts and scheduling: The online scheduler treats primary and CC email as the same contact and asks users to confirm which profile they mean, so you avoid duplicate contacts when someone books with an email that appears on multiple profiles.
Quotes and pricing: Quotes can be set to "On Hold" so they stay out of active worklists and close-rate calculations; bundle discount is shown relative to the primary service fee everywhere; and manual equipment count overrides now persist after save.
Reports and activity: Report skins are improved (summary filters, media visibility, buying agent in header, section layout); the inspector balance widget uses short names and adapts to the list; and you can manually send or resend action-flow emails from the work order activity screen with optional recipient and content overrides.
What changed: Office staff and inspectors can attach reference files to a work order (e.g. build facts, permit data) and view them on the work order page and in the mobile app.
Before: Work order attachments were limited to report-related items from Spectora; no way to add internal-only reference files.
Now: A dedicated attachments area on the work order lets you upload, view, and remove files; files are for internal use only; inspectors can open them from the app in the field.

Why it matters: Teams keep all job-related documents in one place without affecting client or agent report access.
What changed: Scheduler looks up contacts by primary or CC email and shows a confirmation step so the user can confirm or choose the right profile instead of creating a duplicate.
Before: Lookup used only primary email, so the same person could get multiple contact records.
Now: Match on primary or CC email; verification step shows first and last name only; user confirms or selects profile; scheduler permissions support CC-email lookup.
Why it matters: Fewer duplicate contacts and clearer identification when a shared email appears on more than one profile.
What changed: Quotes can be marked "On Hold" and are excluded from active worklists and from close-rate and pipeline calculations.
Before: On-hold quotes still appeared as pending and counted in pipeline and close-rate.
Now: Set quote to On Hold from lists and quote bar; on-hold quotes filtered out of default worklists and excluded from close-rate; exports and Reports Hub support the status.

Why it matters: Schedulers focus on quotes that need action; close-rate reflects only pending, accepted, and rejected quotes.
What changed: From the work order activity feed you can manually send or resend an action-flow action (e.g. email or SMS) and, for emails, override recipients or content.
Before: No way to send an action from that screen or resend with different recipients.
Now: Trigger send from activity screen; for email, resend with different recipients or content overrides without re-running the full flow.

Why it matters: Faster follow-up and recovery when a contact changes or an email needs to go to someone else.
What changed: Scheduling admins can permanently delete a job so it is fully removed from the system, not only cancelled.
Before: Jobs could be cancelled but remained in the database and in lists.
Now: Scheduling-admin users see a delete option on the work order; after confirmation, the job is permanently deleted.

Why it matters: Admins can clean up mistaken or duplicate jobs without leaving cancelled records.
What changed: Bundle discount/savings is shown relative to the primary service fee everywhere (scheduler, quote, invoice table, add-on recommendations).
Before: In some places discount was shown relative to add-on pricing, making savings look smaller.
Now: One consistent display value (savings off primary fee) in quote modal, invoice table, scheduler, and client-facing quote.
Why it matters: Clients see the full value of bundling; regions can enable bundles with correct savings messaging.
What changed: Home inspection report skin updated: summary filters, media count/visibility, buying agent in header, section text above photos, less wasted space, wind mitigation and inspector signature aligned with PDF.
Before: Some sections and filters didn’t match PDF or expectations; multi-image visibility and layout varied.
Now: "Summary Items" filters; defect cards show media counts and clearer carousel; buying agent in header; section text above photos; overview hidden for four-point where applicable; wind mitigation and signature sections match PDF.
Why it matters: Regions can use the home inspection report skin without layout or visibility blockers.
What changed: Inspector names show as first name + last initial; widget height adapts to number of inspectors; full name in tooltip.
Before: Full names could overflow; fixed size could feel cramped or wasteful.
Now: Abbreviated names and adaptive height for easier scanning.

Why it matters: Better readability and use of space on calendar and dashboard.
What changed: When Flexfund notifies Attik that a payment has been funded, we now record the funded amount on the payment and when any linked PAC fees are considered funded, so you can see exactly what was funded and when.
Before: Funded amounts and whether a fee had been marked funded were not fully captured, so reporting and reconciliation could be incomplete.
Now: Payment records show the funded amount when Flexfund sends it, and fee records show when they were marked funded. Exports and internal views can use this for accurate payment and fee status.
Why it matters: You get a clearer picture of Flexfund payments and fee funding for reporting and reconciliation, without missing or inconsistent data.
What changed: In the Reports Hub and in data exports that include quotes, quote status filters and labels now match what you see in the app—including the new "On Hold" status—and the "created by" field shows the correct person's name.
Before: Quote filters in exports sometimes didn't support every status or show who created the quote consistently, so reports could be incomplete or misleading.
Now: When you filter or export quotes, status options (including On Hold) and date filters work as expected, and the creator is resolved to a display name so you know who created each quote.
Why it matters: Reports and exports that include quotes are accurate and consistent with the app, so you can trust them for pipeline and team reporting.
What changed: When you create or update a job in Attik, it can sync to HubSpot as a deal. New jobs sync after a short delay; updates sync right away. Contact roles (e.g. client, agent) are sent to HubSpot so the right people appear on the deal.
Before: New jobs might not create or update a HubSpot deal, or the deal might not show the correct contact roles, so your CRM could be out of date or missing context.
Now: New inspections create or update a HubSpot deal with the right timing, and contact roles are mapped to the deal so your sales team sees who's involved without re-entering information.
Why it matters: Your CRM stays in sync with Attik jobs and contact roles, so you don't have to update deals manually and deal records are more useful for follow-up.
What changed: For ProPair instances, we now apply ProPair-specific branding and rules for sample reports and quotes—including how sample report addresses and quote usage are restricted—so demos and samples behave correctly.
Before: Sample reports and quotes did not have ProPair branding or the right restrictions, so they could be used in ways that didn't match the intended use.
Now: ProPair instances show the correct branding, and sample report and quote usage are restricted so they're used only as intended (e.g. demos and samples, not live jobs).

Why it matters: ProPair teams get consistent branding and controlled use of sample reports and quotes, so demos look right and misuse is prevented.
What changed: Manual equipment count override on the work order now persists after save and is restored when reopening the quote.
Before: Price reflected the override but equipment count reverted to modifier value after save.
Now: Backend stores manual-change flag; frontend sends and restores equipment quantities so override is kept after save and reload.
Why it matters: Inspectors get the correct equipment count; inventory and pricing stay consistent.
What changed: We fixed a timing issue that could affect new jobs right after they’re created. Charges and automated follow-ups now apply correctly from the start.
Before: Right after creating a job, charges or automated actions (like emails) could be missing, wrong, or delayed until something was refreshed or updated.
Now: As soon as you create a job, its charges and any workflow steps (e.g. emails, notifications) are set up correctly and run as intended.
Why it matters: You can create a job and trust that pricing and follow-ups are correct immediately, with no need to reopen or re-save the job to fix them.