In Claude and ChatGPT
Run your account from Claude or ChatGPT.
TL;DR
Connect LeadMove to Claude or ChatGPT and ask about last night, onboard a buyer from an insertion order, or fix what failed, in your own words. Every change comes back as a card in the conversation: you read what would change, then press Apply or say yes, and every applied change can be undone for seven days. The connection has the permissions of your own role, revoked in one click, and it is included on every plan from $149/mo.
From $149/mo · no setup fee · 14-day free trial · live in 15 minutes.
The work that never made it into a screen
Most of running a distribution business is small, repetitive and hard to automate: reading last night’s failures to find out whether it was one endpoint or five, turning an insertion order into a buyer with the right caps and the right territories, chasing the one field that made forty leads invalid. Each of those is ten minutes of clicking through screens you already know. Connecting the assistant you already use to your account turns them into a sentence, and turns the result into a card you read and approve before anything happens.
What you can ask for
Plain questions work, and six workflows ship with the connection for the recurring jobs. The first two kinds only read. The last two end in a change you approve.
Ask what happened
Reading questions, answered from your own records rather than a guess: the routing trace of a lead, the buyers close to their cap, what changed on a pipeline last week. Nothing is modified, so there is nothing to approve.
Set things up from what you already have
Paste an insertion order, or attach the PDF. The assistant reads out the table it extracted, asks only for what the order does not say, and comes back with one card holding the buyer, its delivery endpoint and a rule per territory. One yes creates all of it, paused, so you check before anything goes live.
Fix what went wrong
The morning repair job, grouped by cause rather than by status: the endpoint that errored, the buyer that filled up, the leads nobody had a rule for. Each group gets its own card, so approving the retries does not also approve the reassignments.
The card, in Claude and in ChatGPT
Every proposed change arrives as a LeadMove card in the conversation: what would change, who it affects, and how long you have to undo it. Press Apply, Discard or, once applied, Undo right on the card, or just say yes. A whole setup is one card with one button. Open the conversation again next week and each card shows what became of it. Claude Code and other clients show the same preview as text.
Four things that stay true, whatever you ask
The assistant never charges a card, never refunds money, never deletes anything and never touches your credentials. That is by construction rather than by instruction: no tool exists for any of it, at any permission level.
Preview: you see it before it happens
Asking for a change does not make it. What comes back is a card: what would change, what else it would affect, what it warns about, and whether it can be undone. A rule preview replays your last 30 days of real leads against it, so you know what it would have matched before you switch it on. The card goes stale after ten minutes, and if somebody edits the same thing in between, the change is refused and you get a fresh preview instead.
Undo: seven days to take it back
Every applied change is undoable for seven days, from the card or from the activity log in the app. Nothing is deleted to undo something: values are put back, new things are archived or switched off, and a ledger entry is compensated by an opposite one. What it creates arrives switched off: a buyer paused, an endpoint disabled, a rule off and flagged for review.
Permissions: the same as your role
Four permissions you tick on purpose when you connect: read, change configuration, act on leads, record buyer payments. A connection can never do what the person behind it could not do by hand, the role is re-read on every request, and permissions can be removed from a connection but never added to one. Revoking a connection is one click in Settings.
Audit: everything it did is on the record
Every change lands in the activity log under the name of the connection, so you can filter by it and read a session end to end. Each connection also shows its own recent calls: the tool used, whether it worked, how long it took. Moving where a buyer receives leads emails every owner the moment it happens, with the diff and an undo link.
How to connect
- 1
In LeadMove, open Settings, then Developers, then Connect an assistant, and pick where you use it: Claude, ChatGPT, Claude Code, Cursor or another tool. Each path shows only what it needs.
- 2
Claude: the dialog gives you the link to paste into Claude’s connectors and walks you through the sign in. You tick the permissions on a LeadMove screen that names the application asking and the account it will act as.
- 3
ChatGPT: the same link, added as a custom connector. Until LeadMove is listed in the ChatGPT app directory, you allow custom connectors in your ChatGPT settings first; the LeadMove screen shows the steps.
- 4
Claude Code: one command to copy, then /mcp and sign in. Cursor and other MCP clients use the same server URL; a server or a script with no browser uses a key instead.
- 5
Name the connection after where it runs, "Claude on my laptop", because that name is what you read later in Settings and in the activity log. Read access alone covers most questions.
What it reaches
Territory routing
Ask for a buyer with three states and a zip list and read the rules it proposes before they are live.
Switching platforms
Paste an export from your old platform and get the buyers, prices and rules back as one card to check.
What it can and cannot do
The four permissions, the things that are always off, the limits, and every way to switch it back off.
Data sent to a connected assistant
What leaves your account, what is masked, and how to stop it in one switch.
Included on every plan, from $149/mo. There is no add-on, no tier to reach, and connections do not count against your lead quota.
Running your account from Claude or ChatGPT, FAQ
Is it included in my plan?
Yes, on every plan, starting at $149/mo. Every LeadMove feature is on every plan and this one is no different: what changes between plans is your lead, buyer and pipeline quota. There is no add-on to buy and no tier to reach.
Does it count against my quota?
No. Your lead quota counts leads, and a connection is not a lead. Questions through Claude or ChatGPT are not rationed against the in-app allowance of 500 questions a month either. A connection has its own ceilings, there to stop a runaway loop rather than to ration you: 120 requests a minute and 200 changes a day, with reading never affected. Past a limit it says so and when it resets.
What does the assistant see?
Whatever answers the question you asked, from your organization only. That includes lead contact details when you ask about a lead, which is why the consent screen says so before you connect. A member-level connection always sees contact details masked, and you can force masking on any connection from its page.
How do I switch it off?
Four ways, from broadest to narrowest. Settings, Developers, Assistant access holds one switch per permission covering every connection at once, which is the fastest stop. Below that you can suspend a single connection, revoke it permanently, or untick one permission and leave the rest working. A revoked connection stops on its next request.
Does it work with anything other than Claude and ChatGPT?
Yes. LeadMove speaks the Model Context Protocol, so any MCP client connects the same way: Claude Code, Cursor, or a script you write yourself. Claude Code has a plugin with the six workflows as slash commands, and a script sends a key as a bearer token. Clients that do not draw cards show the same preview as text.
Can it do something I did not approve?
No. A change is two steps: the assistant asks LeadMove what would happen and shows you the card, then you approve and LeadMove rechecks everything and applies it. The token behind a card is worth nothing on its own, expires in ten minutes, and works once. Reading is the only thing that happens without a step from you.
Who in my team can connect one?
Anyone with a seat, up to what their role allows. A member connects with read access and masked contact details. An admin can also grant configuration changes and lead actions. Recording a buyer payment is owner only. If someone is demoted, their connection narrows on its next request; if they leave the workspace, it suspends itself.
What happens if it gets something wrong?
You see it on the card, before it happens, which is the whole point of the card. If something did land and you want it back, undo it for seven days from the card or from the activity log. Past seven days the route is making the opposite change, which the assistant will do for you.
Connect Claude or ChatGPT to your account today.
Self-serve, on every plan. Full access free for 14 days, no charge until day 15, cancel in one click.