Schedule

This Schedule is incorporated into and forms part of the FernNola Limited Master Terms of Service (the "Master Terms"). Capitalised terms used but not defined in this Schedule have the meaning given in the Master Terms.

If there is any inconsistency between the Master Terms and this Schedule, this Schedule prevails for the App named below.

You must hold an active account on each of the above services to install and use this App.

This App reads from and writes to the Marketplace and Fergus as set out below. The App does not store complete customer records. It stores the Sync Metadata listed in section 4.3 and retains diagnostic logs for 30 days. Full retention details are in the Fergus CRM Integration Privacy Policy.

4.1 Reads

• From the Marketplace: opportunities, contacts linked to opportunities, pipeline and stage configuration, account identifiers, calendar appointments and calendar user data, inbound and outbound messages (email, SMS, WhatsApp) with attachments, custom field values, contact notes.
• From Fergus: quotes, estimates, jobs (including job phases, hold/archive state, and completion status), job customer linkage, calendar events (titles, times, assigned users, notes, recurrence rules), enquiries and enquiry statuses, customers (names, contact details, addresses), customer invoices (for opportunity value sync), users (for calendar user mapping).

4.2 Writes

• To Fergus: new quote, estimate, or charge-up jobs created when a Marketplace opportunity enters a configured pipeline stage; new enquiries from configured pipeline stages (with status tracking through contacted, rejected, and converted states); calendar events synced from the Marketplace (including updates and deletions); notes synced from Marketplace contacts; notes and file attachments extracted from inbound and outbound messages (email, SMS, WhatsApp).
• To the Marketplace: opportunity stage transitions when a linked Fergus quote or estimate is published, sent, accepted, or rejected, when a job is scheduled, work-completed, or invoiced, or when a job is placed on hold, archived, resumed, or un-archived; new opportunities created from Fergus-originated jobs; calendar events synced from Fergus (appointments on matched-user personal calendars, block slots on a shared calendar for unmatched users); opportunity custom field updates; opportunity monetary value updates (from quote totals and invoice totals); opportunity name updates (from configurable naming templates); contact lifecycle tags reflecting Fergus job state; contact notes synced from Fergus job and customer notes; contact field updates from Fergus customer data (names, phone numbers, addresses).

4.3 Stored Sync Metadata

The App stores the following Sync Metadata to operate:

• Marketplace opportunity ID to Fergus job ID mappings and watched-job tracking records
• Pipeline and stage configuration choices, including stage-to-action rules and quote outcome actions
• Last-sync timestamps, polling cursors, and tick counters
• Audit log entries describing each sync event (timestamp, opportunity, stage, action taken, result, Fergus job ID)
• Calendar event mappings (Fergus ↔ Marketplace event ID pairs, content hashes, origin tracking, and sync timestamps)
• Calendar user mappings (Fergus user ↔ Marketplace user, matched by email, with per-user calendar IDs)
• Calendar sync configuration and run telemetry (per-location settings, per-run operational metrics)
• Message sync records (message ID, contact reference, channel type, processing status, linked Fergus entity, attachment metadata)
• Note sync mappings (cross-system note ID pairs, content hashes, sync direction)
• Custom field mapping configuration (field IDs, names, mapping direction, action context, execution order)
• Contact-to-customer maps and customer sync skip lists (for incremental discovery)
• Backfill opportunity records (pre-existing opportunities awaiting user decision)
• App version and feature-availability tracking records
• App status event audit trail (token state changes, connection events)
• Notification queue records

4.4 Sub-processors specific to this App

This App uses third-party infrastructure providers for application hosting, database hosting, and related operational services. The specific providers used may change from time to time. A current list of sub-processors is maintained at /legal/subprocessors and is also available on request from support@fernnola.com.

These notices supplement and particularise the generic trademark provision in clause 8 of the Master Terms.

• Pipeline stage actions. Marketplace pipeline stage transitions trigger Fergus job, quote, estimate, enquiry, or charge-up creation in near-real-time via webhook. Configurable per stage.
• Quote and estimate outcomes. Fergus quote and estimate lifecycle events (published, sent, accepted, rejected) are polled on a configurable cadence (default: every minute) and written back as Marketplace opportunity stage transitions.
• Job phase and completion tracking. Job phase statuses (scheduled, work-completed, invoiced) are polled on the same cadence and trigger corresponding Marketplace stage moves. On job completion, invoice totals are synced to the opportunity value.
• Enquiry lifecycle. Enquiry status changes (contacted, rejected, converted to job) are polled and trigger configurable Marketplace stage moves. Enquiry-to-job promotion is automatic when configured.
• Job hold, archive, and resume. Hold, archive, resume, and un-archive events are detected and trigger configurable Marketplace stage moves.
• Job sync (Fergus to Marketplace). Jobs created directly in Fergus (outside the Marketplace) are detected and synced as new Marketplace opportunities in a configurable pipeline and stage.
• Calendar sync. Fergus calendar events sync to the Marketplace on a configurable cadence (default: every minute). Marketplace appointments sync to Fergus on the same cadence. When inbound sync is first enabled, existing appointments from the past 30 days are backfilled. Reconciliation checks run every 5 minutes.
• Customer sync. Fergus customers are incrementally discovered and matched to Marketplace contacts by email or phone. Customer field updates (names, phone numbers, addresses) are pushed to matched contacts.
• Note sync. Job and customer notes are synced bidirectionally between Fergus and the Marketplace, with content-hash tracking to detect edits and prevent duplicates.
• Message sync. Inbound messages (email, SMS, WhatsApp) with attachments are processed as they arrive via webhook and uploaded to the linked Fergus job. Outbound messages are synced as Fergus notes. Messages that cannot be auto-linked are queued for manual resolution.
• Custom field mappings. User-configurable field-to-field translations between Marketplace opportunity fields and Fergus job fields, scoped to specific action contexts and directions.
• Lifecycle tags. Persistent and lifecycle tags are applied to Marketplace contacts to reflect Fergus job state (e.g. quote sent, accepted, work scheduled, invoiced, on hold).
• Rate limits. The App is subject to the Marketplace and Fergus API rate limits. During high-volume periods, sync operations may be queued or deferred to the next polling cycle.
• Outages. Marketplace and Fergus outages will pause sync. Operations are retried automatically; no manual action is required for transient outages.