Upfirst is an AI receptionist that connects to Follow Up Boss in two ways: through Custom Actions (live API calls during a call, using an FUB API key) and through Zapier (writes to FUB after the call ends). Inbound calls turn into recognized leads or fresh People records in the right pipeline without anyone re-typing details from a voicemail.

Does Upfirst integrate with Follow Up Boss?

Yes. Two options:

• Custom Actions let your receptionist hit Follow Up Boss live during a call. Look up a Person by phone, check their stage, log a note, create a new lead, all in real time.
• Zapier takes a completed call and writes it into Follow Up Boss afterward.

FUB's API key setup is one click for a broker or admin. Paste the key into Upfirst and every inbound call can read from and write to your database.

What Follow Up Boss is

Follow Up Boss is the CRM real estate agents and teams use to handle lead follow-up. It pulls leads from Zillow, Realtor.com, IDX sites, and other sources, assigns them to agents, runs action plans, and keeps every text, email, and call against the right Person record.

The inbound call is usually the highest-intent moment in a real estate funnel. A returning buyer calling back is a hot lead. Missing or fumbling that call loses the deal. The integration makes sure every call lands on the right Person and the agent is in the loop.

What Upfirst can do with Follow Up Boss

Greet returning leads by name on the first ring

When a call comes in, Upfirst hits GET /v1/people?phones=#{{caller_id}}. If FUB has the Person, the receptionist opens by first name and can reference their assigned agent, stage, source, or last activity. Net-new numbers go through your standard intake flow.

Pull lead history or assigned agent during the call

Mid-call, the receptionist can confirm the caller's email or address, find the matching Person in FUB, and reference whatever you want: action plan, recent property views, pipeline stage, assigned agent. "What's my agent's name?" gets answered without a hold.

Drop new leads into Follow Up Boss when the call ends

For a net-new caller, Upfirst posts a POST /v1/events when the call wraps. (The events endpoint is FUB's recommended path for new leads.) The event becomes a Person, the source is set, the call summary and transcript drop in as a note, and FUB's assigned-agent rules take over. A round-robin team gets the same lead routing they'd get from a Zillow inquiry.

Match call urgency to FUB action plans

Upfirst can pull anything from the call: lead intent (buyer, seller, renter, financing), urgency, timeframe, custom fields. Use those signals to tag the lead, push them onto a specific action plan, or set the stage. "Ready to buy in 30 days" gets a different cadence than "still browsing."

Follow Up Boss API calls Upfirst can make

• GET /v1/people filtered by phones, emails, name, or custom fields
• POST /v1/events to create a lead through FUB's standard intake path
• POST /v1/people for direct Person creation
• PUT /v1/people/:id to update stage, source, tags, or custom fields
• POST /v1/notes with the call summary and transcript
• POST /v1/calls to log the call as an activity

Setting up the Follow Up Boss integration

Custom Actions

1. In Follow Up Boss, go to Admin > API and generate an API key. A broker key sees the whole account; an agent key only sees that agent's contacts. Pick what fits.
2. In Upfirst, go to Agent > Custom actions and add a new action.
3. Pick when it runs: When call starts for the phone-number Person lookup, During call for email or name searches, or After call for creating events or notes.
4. Set up the request. FUB uses HTTP Basic auth (the API key is the username, no password). For a People lookup, GET https://api.followupboss.com/v1/people?phones=#{{caller_id}} with Authorization: Basic followed by the base64-encoded YOUR_API_KEY:.
5. Pick which fields the receptionist gets back (first name, stage, assigned agent, source). Test it against a known number. Save.

Zapier

1. Create a Zap. Trigger: Upfirst > Call Completed.
2. Pick a Follow Up Boss action: Create Lead (Event), Update Person, Add Note.
3. Map the call fields to FUB fields. Source matters most, since it drives FUB's source-based routing.
4. Add filters so only the right calls create leads (booking, valuation requests) and existing-client calls just log a note.
5. Test with a real call. Turn the Zap on.

A typical real estate setup: Person lookup on call start, stage update mid-call when the caller signals intent, event creation on call end. FUB's routing logic handles the rest.