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. No primary copies of Customer Data are retained beyond what is needed to complete in-flight sync operations and short retention windows for diagnostic logging.

4.1 Reads

• From the Marketplace: opportunities, contacts linked to opportunities, pipeline and stage configuration, account identifiers, calendar appointments, inbound messages (email, SMS, WhatsApp) with attachments, custom field values.
• From Fergus: quotes, estimates, jobs, job status, job customer linkage, calendar events (titles, times, assigned users, notes), enquiries, enquiry statuses, customer invoices (for opportunity value sync).

4.2 Writes

• To Fergus: new quote, estimate, or charge-up jobs created when a Marketplace opportunity enters a configured pipeline stage; calendar events synced from the Marketplace; notes and file attachments extracted from inbound messages; new enquiries from configured pipeline stages.
• To the Marketplace: opportunity stage transitions when a linked Fergus quote or estimate is published, sent, accepted, or rejected, or when a job is scheduled, work-completed, or invoiced; calendar events synced from Fergus; opportunity custom field updates.

4.3 Stored Sync Metadata

The App stores the following Sync Metadata to operate:

• Marketplace opportunity ID to Fergus job ID mappings
• Pipeline and stage configuration choices
• Stage action and outcome rule configuration
• Last-sync timestamps and polling cursors
• Audit log entries describing each sync event (timestamp, opportunity, stage, action taken, result, Fergus job ID)
• Calendar event mappings (Fergus ↔ Marketplace event ID pairs and sync timestamps)
• Calendar user mappings (Fergus user ↔ Marketplace user, matched by email)
• Message sync records (message ID, contact reference, email content, attachment metadata, processing status, linked Fergus entity)
• Custom field mapping configuration (field IDs, names, mapping direction)

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 in the Fergus CRM Integration Privacy Policy 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.

• Sync cadence. Marketplace pipeline stage transitions trigger Fergus job creation in near-real-time via webhook. Fergus job lifecycle events are polled every 5 minutes; you should expect Marketplace opportunity stage updates within that window.
• Rate limits. The App is subject to the Marketplace and Fergus API rate limits. During high-volume periods sync operations may be queued.
• Outages. Marketplace and Fergus outages will pause sync. Operations are retried automatically; no manual action is required for transient outages.
• Calendar sync cadence. Outbound Fergus calendar events sync to the Marketplace every 5 minutes. Inbound Marketplace appointments sync to Fergus every 5 minutes. When inbound sync is first enabled, existing appointments from the past 30 days are backfilled.
• Message sync. Inbound messages with attachments are processed as they arrive via webhook. Files are uploaded to the linked Fergus job; messages that cannot be auto-linked are queued for manual resolution.