How to Integrate AI Into Follow Up Boss (Operator Playbook)

Most real estate brokerages already run Follow Up Boss. It has 60,000+ agents on it, a clean REST API, and webhooks that fire on every lead event. The problem is not that agents lack a platform. The problem is that agents are still doing the work the platform should be doing: triaging leads, writing follow-up sequences, updating deal stages, drafting listing descriptions, and manually coordinating with lenders and title.

AI integration removes the coordination drag without replacing Follow Up Boss. This post walks through the exact four-step process AiiACo uses to bolt an AI operational layer on top of an existing Follow Up Boss deployment.

Step 1: Map the current Follow Up Boss workflow

Before calling a single API endpoint, audit every touchpoint in the existing CRM. The questions to answer:

• Where do inbound leads enter Follow Up Boss (Zillow, Realtor.com, IDX sites, open house scans, referral imports)?
• What percentage of leads get triaged within the first 5 minutes? (If you do not know, the answer is probably under 30 percent.)
• What is the average number of follow-up touches per lead, and are they triggered manually or via action plans?
• Which stages in the Follow Up Boss pipeline are updated by agents vs by admins vs by nobody?
• What custom fields already exist, and which ones have been abandoned?

The output is a map of where manual work currently lives. Most brokerages running Follow Up Boss discover that 60 to 70 percent of agent time on the platform goes to activities that have clear AI automation patterns. That is the speed to lead problem in action: agents are doing coordination work instead of relationship work.

Step 2: Authenticate against the Follow Up Boss API

Follow Up Boss exposes a REST API at https://api.followupboss.com/v1/. Authentication is HTTP Basic with the API key as the username and an empty password. Get the key from Settings, then API in the Follow Up Boss admin panel. The account owner must generate the key.

Once authenticated, test against the /people endpoint with a GET request to confirm access. The response returns paginated contacts with all custom fields, stages, and tags. If the API returns 401, the key is either wrong or has been rotated. If it returns 403, the account owner has not enabled API access at the subscription tier (Pro plan or above required for webhooks and custom fields).

Scopes for an AI integration

AiiACo integrations typically need read and write access to people (contacts), events (webhook targets), notes (for agent handoffs), and custom fields (for AI scores and tags). Follow Up Boss does not expose granular scopes; a single API key gets full account access. This means the API key must be stored in a secrets manager, never committed to a repo, and rotated every 90 days.

Step 3: Wire AI capabilities to webhook events

Follow Up Boss supports webhooks for these event types: peopleCreated, peopleUpdated, peopleDeleted, notesCreated, tasksCreated, dealsCreated, dealsUpdated, and communicationsCreated. Subscribe via the API by POSTing to /webhooks with the event type and the destination URL.

Inbound lead scoring on peopleCreated

Every new lead fires a peopleCreated webhook. Route it to an AI scoring endpoint that evaluates intent signals (source, message body, property search history from the IDX integration), budget indicators (price range), timeline (move date, rental expiry), and fit (geography, property type). Write the score back to Follow Up Boss via a custom field called ai_lead_score plus a tag like ai-scored-high, ai-scored-medium, or ai-scored-low. Agents see the score in the normal contact view without opening a new tool.

Multi-touch nurture on stage change

When an agent moves a lead from New to Contacted, fire an AI sequence generator that drafts 5 personalized follow-up messages over a 21-day window. Push each message to Follow Up Boss as a scheduled task assigned to the agent, with the draft in the task note. The agent reviews and sends, or approves auto-send for vetted templates. The agent stays in control but saves 45 minutes per lead on the coordination work.

Listing content on note events

When an agent adds a note with the trigger phrase "new listing", fire a listing content generator that pulls the MLS data and drafts a description, neighborhood summary, and buyer pitch copy. Push the output back as a new note with a draft-ai-listing tag. Listing agents review and publish. Every AI-generated listing description runs through a Fair Housing Act compliance filter before the agent sees it.

Pipeline intelligence on dealsUpdated

Every deal stage change fires a dealsUpdated webhook. Feed this into a pipeline intelligence model that computes deal velocity, at-risk probability, and next-best-action per opportunity. Surface the output via custom fields on the deal (ai_close_probability, ai_next_action, ai_risk_flag) so the broker of record sees the data in the standard Follow Up Boss reports without a separate dashboard.

Step 4: Deploy without replacing Follow Up Boss

Everything above runs as a separate service (n8n workflow, custom middleware, or hosted Python app) that talks to Follow Up Boss over the API. No data migration. No replacement. Agents continue logging in to the same URL and seeing the same interface. What changes is that the coordination work happens automatically in the background.

Typical deployment timeline for a 40-agent brokerage: first operational module (lead scoring and basic follow-up automation) ships in 3 to 5 weeks. Full four-capability rollout takes 8 to 12 weeks. AiiACo owns every phase of the build including the Follow Up Boss API wiring, model tuning, agent training session, and month-by-month performance review.

Operators who wire this layer typically see 30 to 70 percent faster triage workflows and a 2 to 3x conversion lift on first-response leads, directional based on AiiACo engagement observations. The conversion lift is highest in markets where competing agents are slow responders. The full framework for why speed to lead matters and how it connects to the broader AI revenue system is covered in our pillar posts.

Frequently Asked Questions

Can I integrate AI into Follow Up Boss without replacing it?

Yes. AiiACo integrates AI directly into Follow Up Boss via the official REST API. Lead scoring, automated follow-up sequences, listing content generation, and pipeline intelligence all run on top of Follow Up Boss. Agents continue using the same CRM interface. No data migration. No plan change beyond Pro tier if API access is not already enabled.

How long does the integration take for a mid-size brokerage?

For a 40-agent brokerage on Follow Up Boss Pro, the first operational module (lead scoring and basic follow-up automation) ships in 3 to 5 weeks. Full rollout of four capabilities (scoring, sequences, listing content, pipeline intelligence) takes 8 to 12 weeks.

What about Fair Housing Act compliance for AI-generated listings?

Every AI-generated listing description and outbound message is filtered through an FHA compliance layer before the agent sees it. The filter flags discriminatory language patterns, steering violations, and prohibited terminology. AiiACo includes this layer in every real estate engagement.

Do I need a higher Follow Up Boss plan?

Only if your brokerage is not already on Follow Up Boss Pro. Pro tier includes API access, webhooks, and custom fields. The Growth plan does not expose webhooks and will not support the full integration. Upgrading from Growth to Pro costs roughly $200 more per user per year as of April 2026.

What is the difference between AI integration and buying an AI SDR tool?

An AI SDR tool is a point product that handles one step of the pipeline (usually first-touch outreach). AI integration is a four-capability layer that handles scoring, sequencing, content generation, and pipeline intelligence as one coordinated system on top of Follow Up Boss. The difference is that integration compounds because every capability informs every other capability. A tool does its one thing in isolation.