Follow Up Boss (FUB) Integration

Overview

The Super Portal maintains a two-way sync with Follow Up Boss. FUB is the primary CRM for agent-client relationships, and the SP extends it with property search, CMA, tours, and transaction management.

Sync Behavior

FUB to Super Portal:

• New contacts created in FUB are synced to the SP automatically.
• Contact fields synced: name, email, phone, tags, agent assignment, collaborators.
• When a contact is deleted in FUB, they are also removed from the SP (with handling for delayed sync).
• Duplicate clients in FUB are handled via the Events API to prevent data conflicts.

Super Portal to FUB:

• Activity from the SP (property views, search interactions, CMA views) is logged to FUB as activity entries.
• Emails sent from the SP are synced to FUB for the contact record.
• The "Send Properties" feature sends the property list to both the client and records it in FUB.

FUB Widget (Embedded App)

The SP is embedded within FUB via a widget that appears on client records. Key behaviors:

• The widget loads the client's SP page based on the FUB contact match.
• Collaborators assigned in FUB receive access to the client's SP page.
• If a collaborator does not have SP access, this is a known issue that has been resolved -- collaborators now sync correctly.
• If the embedded app encounters a trashed or invalid user, it displays a descriptive error message rather than a generic error.

Phone Number Collection

When a client accesses the SP via any link and does not have a phone number set in FUB, the portal displays a prompt requesting their phone number. This prompt:

• Appears once per session (not repeatedly on every page load).
• Can be dismissed by the client.
• Updates the phone number in both the SP and FUB when provided.

Source Tracking

Leads created via SP public forms are tagged with specific FUB sources for accurate attribution:

Sync Edge Cases

Bad phone numbers or emails: The SP validates phone numbers and email addresses during sync. Invalid data is flagged rather than silently dropped.

Multiple primary tags: When FUB sends multiple primary tags for a contact, the SP handles them without conflict.

Agent reassignment: If a client's agent is changed in FUB, the SP reflects this change. The system includes safeguards to prevent unintended reassignment by automated processes.

Team-Based FUB Configuration

Teams with their own FUB instance have separate branding and configuration for:

• CMA public links
• Search public links
• Email templates and signatures

FUB API Rate Limiting

The FUB API occasionally returns HTTP 429 (rate limit). The SP implements a retry mechanism using a delayed queue for FUB API requests. If a 429 is received, the request is re-queued with a delay. This prevents data loss from rate-limited API calls.

Sync Fields

Currently synced: name, email, phone, tags, agent assignment, collaborators, activity events, property views.

Planned additions: Background and Notes fields (bi-directional sync confirmed as feasible).

Not synced: Custom fields (e.g., SN_event for birthdays/anniversaries). These will be addressed by the Database Wizard feature.