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.
What agents do in Follow Up Boss.
Create a new lead
Create a person record when a new lead comes in from a listing site or referral.
Schedule a follow-up task
Create a task reminding an agent to follow up with a lead after a set number of days.
Confirm before deleting a deal
Require approval before deleting a deal, since it removes its full pipeline and stage history.
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
53Look things up. Allowed by default.
- follow_up_boss.get_meGet Me
- follow_up_boss.get_callGet Call
- follow_up_boss.get_dealGet Deal
- follow_up_boss.get_taskGet Task
- follow_up_boss.get_userGet User
- follow_up_boss.get_eventGet Event
- follow_up_boss.get_pondsGet Ponds
- follow_up_boss.get_stageGet Stage
- follow_up_boss.get_teamsGet Team
- follow_up_boss.get_groupsGet Group
- follow_up_boss.get_personGet Person
- follow_up_boss.list_callsList Calls
- follow_up_boss.list_dealsList Deals
- follow_up_boss.list_notesList Notes
- follow_up_boss.list_pondsList Ponds
- follow_up_boss.list_tasksList Tasks
write
42Create and change things. Allow, or ask the user first.
- follow_up_boss.create_callCreate Call
- follow_up_boss.create_noteCreate Note
- follow_up_boss.create_taskCreate Task
- follow_up_boss.update_noteUpdate Note
- follow_up_boss.update_taskUpdate Task
- follow_up_boss.create_dealsCreate Deal
- follow_up_boss.create_pondsCreate Ponds
- follow_up_boss.create_stageCreate Stage
- follow_up_boss.create_teamsCreate Team
- follow_up_boss.update_callsUpdate Call
- follow_up_boss.update_dealsUpdate Deal
- follow_up_boss.update_pondsUpdate Ponds
- follow_up_boss.update_teamsUpdate Team
- follow_up_boss.create_eventsCreate Events
- follow_up_boss.create_groupsCreate Group
- follow_up_boss.create_personCreate Person
destructive
16Delete, cancel or archive. Ask first, or deny outright.
- follow_up_boss.delete_dealDelete Deal
- follow_up_boss.delete_pondDelete Pond
- follow_up_boss.delete_taskDelete Task
- follow_up_boss.delete_stageDelete Stage
- follow_up_boss.delete_teamsDelete Team
- follow_up_boss.delete_groupsDelete Group
- follow_up_boss.delete_pipelineDelete Pipeline
- follow_up_boss.delete_appointmentDelete Appointment
- follow_up_boss.delete_custom_fieldDelete Custom Field
- follow_up_boss.delete_appointment_typeDelete Appointment Type
- follow_up_boss.delete_deal_custom_fieldDelete Deal Custom Field
- follow_up_boss.delete_people_relationshipDelete People Relationship
- follow_up_boss.delete_appointment_outcomesDelete Appointment Outcome
- follow_up_boss.delete_text_message_templateDelete text message template
- follow_up_boss.merge_templateMerge Template
- follow_up_boss.merge_text_message_templateMerge Text Message Template
Follow Up Boss in three steps.
- 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.
- 02You set the rulesReads run, writes like “create Call” can wait for the user, and “delete Deal” can be denied outright.
- 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.
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
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
Use Follow Up Boss from any agent.
Follow Up Boss and Arc0, answered.
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.
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.
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.
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.
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.
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