Follow Up Boss for AI agents

Follow Up Boss is a CRM built for real estate teams to centralize leads and manage follow-up across calls, texts, and email. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

CRMOAuth 2.0MCP + RESTfollowupboss.com
AUDIT LOG · FOLLOW UP BOSSPOLICY: acme-support
09:41:07 · claude · u_8f2read
follow_up_boss.list_calls
List Calls✓ allowed · 212ms
09:41:08 · claude · u_8f2read
follow_up_boss.get_me
Get Me✓ allowed · 164ms
09:41:09 · claude · u_8f2write
follow_up_boss.create_call
Create Call✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
follow_up_boss.delete_deal
Delete Deal✕ blocked · policy: deny
EVERY FOLLOW UP BOSS CALL, ON THE RECORD
01 · USE CASES

What agents do in Follow Up Boss.

01

Create a new lead

Create a person record when a new lead comes in from a listing site or referral.

02

Schedule a follow-up task

Create a task reminding an agent to follow up with a lead after a set number of days.

03

Confirm before deleting a deal

Require approval before deleting a deal, since it removes its full pipeline and stage history.

02 · ACTIONS

111 Follow Up Boss actions, graded by risk.

Every Follow Up Boss action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

53

Look things up. Allowed by default.

  • follow_up_boss.get_me
    Get Me
  • follow_up_boss.get_call
    Get Call
  • follow_up_boss.get_deal
    Get Deal
  • follow_up_boss.get_task
    Get Task
  • follow_up_boss.get_user
    Get User
  • follow_up_boss.get_event
    Get Event
  • follow_up_boss.get_ponds
    Get Ponds
  • follow_up_boss.get_stage
    Get Stage
  • follow_up_boss.get_teams
    Get Team
  • follow_up_boss.get_groups
    Get Group
  • follow_up_boss.get_person
    Get Person
  • follow_up_boss.list_calls
    List Calls
  • follow_up_boss.list_deals
    List Deals
  • follow_up_boss.list_notes
    List Notes
  • follow_up_boss.list_ponds
    List Ponds
  • follow_up_boss.list_tasks
    List Tasks
+ 37 MORE

write

42

Create and change things. Allow, or ask the user first.

  • follow_up_boss.create_call
    Create Call
  • follow_up_boss.create_note
    Create Note
  • follow_up_boss.create_task
    Create Task
  • follow_up_boss.update_note
    Update Note
  • follow_up_boss.update_task
    Update Task
  • follow_up_boss.create_deals
    Create Deal
  • follow_up_boss.create_ponds
    Create Ponds
  • follow_up_boss.create_stage
    Create Stage
  • follow_up_boss.create_teams
    Create Team
  • follow_up_boss.update_calls
    Update Call
  • follow_up_boss.update_deals
    Update Deal
  • follow_up_boss.update_ponds
    Update Ponds
  • follow_up_boss.update_teams
    Update Team
  • follow_up_boss.create_events
    Create Events
  • follow_up_boss.create_groups
    Create Group
  • follow_up_boss.create_person
    Create Person
+ 26 MORE

destructive

16

Delete, cancel or archive. Ask first, or deny outright.

  • follow_up_boss.delete_deal
    Delete Deal
  • follow_up_boss.delete_pond
    Delete Pond
  • follow_up_boss.delete_task
    Delete Task
  • follow_up_boss.delete_stage
    Delete Stage
  • follow_up_boss.delete_teams
    Delete Team
  • follow_up_boss.delete_groups
    Delete Group
  • follow_up_boss.delete_pipeline
    Delete Pipeline
  • follow_up_boss.delete_appointment
    Delete Appointment
  • follow_up_boss.delete_custom_field
    Delete Custom Field
  • follow_up_boss.delete_appointment_type
    Delete Appointment Type
  • follow_up_boss.delete_deal_custom_field
    Delete Deal Custom Field
  • follow_up_boss.delete_people_relationship
    Delete People Relationship
  • follow_up_boss.delete_appointment_outcomes
    Delete Appointment Outcome
  • follow_up_boss.delete_text_message_template
    Delete text message template
  • follow_up_boss.merge_template
    Merge Template
  • follow_up_boss.merge_text_message_template
    Merge Text Message Template
03 · HOW IT WORKS

Follow Up Boss in three steps.

  1. 01Your users connect Follow Up BossThey sign in to Follow Up Boss on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create Call” can wait for the user, and “delete Deal” can be denied outright.
  3. 03Any agent can actYour agent calls Follow Up Boss through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('follow_up_boss', {
  read: 'allow',
  write: 'ask',        // create_call
  destructive: 'deny',  // delete_deal
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Follow Up Boss connects.

Users sign in to Follow Up Boss on Arc0 Connect and approve the scopes you request. Build with Arc0’s Follow Up Boss OAuth app, or bring your own so the Follow Up Boss consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

The same Follow Up Boss connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key · OAuth 2.0
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Follow Up Boss from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Follow Up Boss and Arc0, answered.

Q01

Can I use Follow Up Boss with Claude, ChatGPT or Cursor?

Yes. Connect Follow Up Boss to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Follow Up Boss actions you allow.

Q02

How do users connect Follow Up Boss?

Users sign in to Follow Up Boss on Arc0 Connect and approve the scopes you request. Build with Arc0’s Follow Up Boss OAuth app, or bring your own so the Follow Up Boss consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

Q03

Which Follow Up Boss actions can my agent take?

111 in total: 53 read, 42 write and 16 destructive, such as “create Call”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Follow Up Boss?

Yes. Actions like “delete Deal” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Follow Up Boss too?

Yes. The same Follow Up Boss connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Follow Up Boss into your agent.

Your users connect Follow Up Boss once, under your brand. Your agent gets 111 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan