# First Team Plan

Published: 2026-03-24
Updated: 2026-03-24
Source: https://docs.oppy.pro/n/first-team-plan

---

![First Team branded ActiveCampaign + Oppy + Follow Up Boss Simple Sync View](https://res.cloudinary.com/kw/image/upload/v1774374704/comms-api/production/07b2801d-80ae-45cf-ace9-1b272a30384c/0feb0243-c5a9-4dbf-beb1-dbec46796dd3/oppy_1774374704_0.jpg)

## First Team + Oppy High-Level Sync Architecture

### Overview
This flow keeps **ActiveCampaign** and **Follow Up Boss (FUB)** aligned by using **Oppy** as the orchestration and sync layer on both sides of the integration.

At a high level:

1. **ActiveCampaign** holds the originating contact, campaign context, and can calculate metrics like **time to close**.
2. **Oppy** sits between **ActiveCampaign** and **Follow Up Boss**, handling identity matching, field normalization, routing, and sync logic in both directions.
3. On the **first sync from ActiveCampaign**, Oppy can assign an initial lead score before pushing or mapping the contact into **Follow Up Boss**.
4. **Follow Up Boss** becomes the system of record for recruiting pipeline progress through milestones like **appointment set** and **appointment met**.
5. Using **Oppy automation rules**, Oppy can re-score the lead when **appointment_set** or **appointment_met** tags are added in FUB.
6. Oppy can then enrich the record with **historical production data** from the last 12 months and sync the right values back into **ActiveCampaign**.
7. From that point forward, both systems stay aligned on the fields that matter for segmentation, reporting, lifecycle automation, and score-based routing.

### High-Level Data Flow

```mermaid
flowchart LR
    AC[ActiveCampaign\nLead + campaign context\nTime-to-close calc] <--> O1[Oppy\nIdentity matching + scoring\nRouting + sync logic]
    O1 <--> FUB[Follow Up Boss\nRecruiting workflow + tags\nappointment_set / appointment_met]
    O1 --> AC2[ActiveCampaign\nEnriched contact + automation-ready fields]
```

### Core Sync Logic

- **Source in:** ActiveCampaign provides the contact, campaign context, and initial qualification signal.
- **Bidirectional orchestration:** Oppy sits between ActiveCampaign and FUB on both sides, not just at intake.
- **Initial scoring:** On the first sync from ActiveCampaign, Oppy can assign an initial lead score.
- **Pipeline tracking in FUB:** FUB tracks the recruiting milestones and ownership context.
- **Automation rule trigger:** When **appointment_set** or **appointment_met** tags are added in FUB, **Oppy automation rules** can trigger a re-score and sync event.
- **Enrichment step:** Oppy attaches the last **12 months of sales volume** and role context from the FUB side.
- **Sync back to AC:** Oppy finds the matching ActiveCampaign contact and writes back the updated fields for segmentation, reporting, nurture logic, and score-based automation.

### Key Fields to Keep in Sync

#### Contact / ownership context
- Recruiter
- Team leader
- Community office
- Role: **agent / broker / team leader**
- Lead source

#### Funnel status
- Appointment set
- Appointment met
- SQL-style milestone readiness
- Current workflow / stage status

#### Performance + reporting
- Conversion percentage
- Last 12 months sales volume
- Lead value / production context
- **Time to close** (calculated in ActiveCampaign)

### Automation Rules for Scoring + Sync
Oppy can use automation rules to keep scoring and sync behavior event-driven instead of manual.

Recommended triggers:
- **Initial sync from ActiveCampaign** → create/update contact in FUB, assign baseline score, write first mapped fields
- **FUB tag added: appointment_set** → re-score lead, update lifecycle stage, sync key values back to ActiveCampaign
- **FUB tag added: appointment_met** → re-score lead again, enrich with stronger qualification context, sync back to ActiveCampaign
- **Production data available / refreshed** → write 12-month sales metrics back to the matching ActiveCampaign contact

Helpful docs:
- [Oppy docs](https://app.oppy.pro/docs)
- [Automation rules](https://app.oppy.pro/docs)

### Recommended System-of-Record Split

- **ActiveCampaign:** campaign source, nurture logic, segmentation, downstream marketing automation, and time-to-close calculation
- **Follow Up Boss:** recruiting workflow progression, appointment status, team / office ownership, production context
- **Oppy:** identity matching, field mapping, sync rules, automation-rule triggers, lead scoring, and automated follow-up orchestration

### Practical Outcome

This gives First Team one closed-loop workflow:
**ActiveCampaign ↔ Oppy ↔ Follow Up Boss**
with Oppy also syncing enriched state and scoring back into ActiveCampaign.

That means recruiting activity can be managed in FUB while marketing, segmentation, lifecycle automation, and score-based routing stay accurate in ActiveCampaign.

---

## Detailed Diagram

![First Team + Oppy + Follow Up Boss Detailed Sync Architecture](https://res.cloudinary.com/kw/image/upload/v1774371914/comms-api/production/07b2801d-80ae-45cf-ace9-1b272a30384c/0feb0243-c5a9-4dbf-beb1-dbec46796dd3/oppy_1774371914_0.jpg)