Glossary

CRM and MCP glossary

Short, plain definitions of the terms you'll actually run into using agentlyleads or connecting it to an AI assistant. Each one is a definition, not a pitch, though a few link to the feature page that implements it.

Terms

Twenty terms, alphabetical, two or three sentences each.

Booking link: A Calendly-style scheduling page for one person and one meeting type, at a URL like /book/<workspace>/<user>/<type>. It shows only the times that are genuinely free, once buffers, minimum notice, existing meetings and the host’s connected calendar are all accounted for. See booking links.
Buffer: A gap of time a booking rule holds open before or after a meeting, so a call that runs long doesn't leave the next visitor booking straight into it. Buffers are set per meeting type, in the host's own timezone.
CRM: Customer relationship management software: one place to track the people and companies you sell to, the deals in progress, and the notes, tasks and messages that make up the relationship, rather than spreading it across a spreadsheet and an inbox.
Custom field: A field a workspace adds to an entity, contacts, leads, deals, and so on, beyond the ones the CRM ships with, such as a preferred packaging size or a purchase order number. Each one has a type (text, number, checkbox, a dropdown of options) that new values are checked against.
Deal stage: The step a deal currently sits at inside a pipeline, such as Qualified, Proposal sent or Closed won. You define the stages for your own pipeline; the CRM doesn't impose a fixed sales process on you.
Engagement score: A number out of 100 the AI agent brief calculates from a contact's whole communication history, meant as a quick read on how warm the relationship currently is. It comes with a recommended next action and a draft reply, not just the number on its own.
Hard bounce vs soft bounce: A hard bounce is a permanent delivery failure, an SMTP 5.x.x code, usually meaning the address doesn't exist, and it suppresses that address from future sends. A soft bounce is a 4.x.x, a temporary problem like a full mailbox, and it doesn't suppress anything because the address may well accept the next message.
ICS invitation: The .ics file attached to a meeting confirmation email that lets Gmail, Outlook or any calendar app add the event automatically. Rescheduling the same booking reuses its identity and bumps a sequence number, so the calendar app updates the existing event instead of adding a second one.
Lead vs contact: A lead is someone you haven't yet qualified as a real prospect; a contact is a person you're tracking as an established relationship, usually because a lead was converted. Converting a lead can also create the company and deal that go with it, so the history doesn't start over.
MCP (Model Context Protocol): An open standard for how an AI assistant calls a piece of software’s tools directly, search a contact, draft a reply, log a note, instead of you copying that software’s data into a chat window by hand. Read more in what is an MCP connector.
MCP connector: A live implementation of MCP for one product. agentlyleads runs its connector at /api/mcp, exposing the CRM as tools Claude and ChatGPT can call over OAuth 2.1: open reads, confirmation-gated writes, no delete tools. See the connector.
Minimum notice: How far in advance someone has to book a meeting on a booking link, for example 24 hours. It stops a booking landing on your calendar for ten minutes from now, when you're not looking at it.
OAuth 2.1: The login flow behind "continue with Google"-style connections. You sign in on your own login screen and approve access; the app receives a scoped, revocable token rather than your password, so you can cut off access without changing how you sign in yourself.
Pipeline: The ordered set of deal stages a deal moves through from open to closed, usually shown as a board you drag deals across as they progress. A workspace can run more than one pipeline for different kinds of deals.
Round-robin assignment: A workflow automation action that spreads new records across a team in rotation, one to each rep in turn, instead of everything landing on whoever happens to be watching the inbox.
Saved view: A filtered and sorted list of records, contacts, deals, whatever, that you save and come back to, rather than rebuilding the same filters every time you want to see, say, deals over $10,000 with no activity in two weeks.
Shared inbox: One queue for a team's email, rather than a separate mailbox per person. Assignment, open/closed state, snoozing and internal comments are shared across the team looking at it, so a thread's status means the same thing to everyone.
Structured output: An AI response constrained to a defined shape, a set schema of fields, rather than free-form text a program then has to guess how to parse. It's what lets an AI agent brief return a summary, a score and a next action as fields code can reliably read, instead of a paragraph you'd have to re-parse.
Webhook: A URL another system calls automatically the moment something happens, a new lead created, a deal closed, so software can react to events as they occur instead of repeatedly checking back to see if anything changed.
Workspace: The tenant boundary in a multi-tenant CRM: one company's data, isolated from every other company using the same install. Every record belongs to exactly one workspace, and that isolation is enforced on every read and write, not just in the interface.