Citrus CRM Automations Specification

This article documents the expected HubSpot automations for ^[1], compiled from past Fathom call recordings. The spec format follows a Trigger → Action pattern as established during the ^[2].

Status: In progress — Ben is compiling this list from past Fathoms. Audit with Mark scheduled for Mon/Tue the week of the Thursday Miriam call.

Purpose

Chris previously owned the HubSpot automation build for Citrus. Ownership has transferred to Ben. This spec serves as the canonical reference for:

• What automations were scoped and promised to the client (Miriam)
• Which are complete vs. incomplete
• What remains to be built before or after the Thursday client call

Spec Format

Each automation should be documented in the following format:

Trigger → Action

Example:

A contact submits the intake form → Contact is enrolled in the onboarding sequence and assigned to the sales owner for their region.

Automations List

⚠️ This section is a placeholder. Ben is actively pulling automation specs from past Fathom recordings and ClickUp tasks. Items should be added here as they are identified.

Audit Notes

To be completed during the Mon/Tue review session with Mark.

• Done: (list automations confirmed complete)
• In Progress: (list automations partially built)
• Not Started: (list automations not yet touched)
• Blocked: (list anything requiring access, decisions, or client input)

Access & Prerequisites

• Ben currently has viewer-only access to the Citrus HubSpot account
• Build access must be secured before any automation work can proceed
• Mark to advise on access request process if needed

Key Contacts

Related

• ^[3]
• ^[4]
• ^[5]