Connect · BAMF Developer Platform
CRM Tags & Qualification
How Connect classifies leads, applies CRM tags, and keeps warm-lead, cold-lead, and needs-response queues accurate.
Connect should expose one normalized qualification language across API, MCP, the client portal, and BAMF-managed automations.
Fit and temperature should stay distinct: a cold lead can fit ICP before replying, while a warm lead is a replied fit with active engagement.
On this page
- Load the lead with context
- Choose fit and temperature separately
- Write normalized tags
Agent discovery
Related documentation
- BAMF Developer Docs - Build creator workflows with the BAMF REST API, Product MCP, playbooks, local agent kits, and agent-discoverable docs.
- Connect Overview - BAMF Developer Docs - Public overview of the Connect CRM, outreach ops, MCP, browser skills, and client-portal surface.
- Client Portal Integration - BAMF Developer Docs - How the bamf.com client portal should expose Connect docs, API keys, MCP setup, and shared queue language as one developer surface.
- Connect API - BAMF Developer Docs - Campaign, lead, conversation, tagging, and qualification endpoints for the Connect CRM surface.
- Connect API Contract - BAMF Developer Docs - How Connect keeps a clean api.bamf.ai contract, stable resource naming, and clear product-facing endpoints.
- Campaign Stats & Queues - BAMF Developer Docs - Branded BAMF metrics, queue health, and campaign scoreboard endpoints for connection rate, reply rate, warm-lead flow, and operator visibility.