# Update REsimpli lead statuses and notes after a calling session

> After a REsimpli calling block, an agent moves each seller to the right status, logs the offer in a note and sets call-back tasks, one lead at a time.

Source: https://cotlet.dev/integrations/resimpli-api-mcp-server/update-lead-status

A two-hour block on the Triple-Line Dialer leaves a stack of sellers in the old status: one accepted your number, two want a call next week, a few will never sell. The calls are done, but every lead still has to be opened, moved and annotated before the pipeline view tells the truth.

Cotlet does it in your own REsimpli account with list\_pipelines, list\_leads, get\_lead, update\_lead\_status, add\_lead\_note and create\_task, called by your AI agent, an n8n workflow or a script.

[Request access](https://cotlet.dev/app/signup?app=resimpli) [All REsimpli tools](https://cotlet.dev/integrations/resimpli-api-mcp-server)

Hosted · nothing to install or maintain

Official options

## Can REsimpli do this on its own?

REsimpli says status changes cannot currently be made through its Open API or Zapier, and the Open API cannot add notes or tasks to an existing lead (checked 12 Oct 2026). Inside the app, an Activity Trigger automation on Outgoing Call Outcome can run Change Pipeline Status from the outcome the caller logs. That automation only sees the outcome picked from the list: it does not carry the offer price, the seller's words or a call-back date into the lead, and an outcome logged wrong or not at all means the lead stays where it was.

By hand

## How you do it in REsimpli today

1. Open the lead in REsimpli, click its current status and pick the new one, or drag the card onto the status in the pipeline view.
2. For a move into another pipeline, click the pen icon on the lead and pick the pipeline and status in the Pipeline Status section at the bottom of the edit window.
3. Write what the seller said and the price you offered in a note on the lead. The REsimpli 6.0 Offers section (offeror, date, price, format such as cash or subject-to) is a separate entry on top of that.
4. For sellers who asked to talk later, add a call-back task on the lead with a due time and the person who will call.
5. REsimpli's bulk Change Status in List view moves a filtered group in one go, but it does not fire Lead Status Change automations, so teams that rely on those automations still move each lead by hand after every calling block.

With an agent

## How to update REsimpli lead statuses and notes after a calling session

Prompt

```
Go through the REsimpli leads I called today. Move the accepted offers to Under Contract with the price in a note, move "call me next week" sellers to Follow Up with a call-back task for Sam, and list the ones that should go to Dead Leads so I can pick the reason.
```

1. 01  
### Map your words to your statuses  
Status names differ in every account, so the agent reads list\_pipelines first and matches "Under Contract" or "Follow Up" to real IDs. If you name a status that does not exist, it stops and shows you the closest ones instead of guessing.
2. 02  
### Collect today's calls  
The agent filters list\_leads by the statuses you dialed from, then opens each lead with get\_lead and keeps only those with a call logged today. Your call notes, a pasted call sheet or the notes your caller typed decide where each seller goes.
3. 03  
### Move one lead at a time  
Each seller gets its own update\_lead\_status call, the way you would click Change Status on the lead, instead of a bulk move. A lead that a teammate already moved since the call is left alone and reported, so the agent never drags a deal backwards.
4. 04  
### Write the note before anyone asks  
add\_lead\_note records the offer amount, the format (cash, seller financing, subject-to) and the seller's reason in one line. For "call me next week" sellers, create\_task sets the call-back for the day they named, assigned to the caller you choose, with your time zone on the due time.
5. 05  
### Leave Dead Leads to you  
REsimpli requires a dead reason and asks whether to clear the lead's tasks when a lead goes to Dead Leads. The agent has no field for that reason, so it lists those sellers with what they said and lets you move them yourself.

### What you get back

Example data

```
Calls on 12 Oct 2026: 14 leads with a logged call, 6 needed a change.
12 Oak St (Dana Whitfield): Contact Made to Under Contract. Note: "Accepted $142,000 cash, close in 21 days."
88 Birch Ave (Luis Moreno): Contact Made to Follow Up. Task for Sam Rivera, 19 Oct 10:00.
415 Pine Rd (Carol Hughes): Contact Made to Follow Up. Task for Sam Rivera, 20 Oct 14:00.
7 Elm Ct: already moved to Appointment Set by Jordan at 15:40, left as is.
For Dead Leads (pick a reason): 230 Maple Dr ("no motivation to sell"), 19 Cedar Ln ("needs too much work").
```

### Other ways to ask

- Every weekday at 18:00, update the statuses of the leads called today and send me the Dead Leads list.
- Only the Probate pipeline: move every seller who agreed to an appointment to Appointment Set and add a note with the date.
- Here is my call sheet for 88 Birch Ave, 415 Pine Rd and 12 Oak St. Update the three leads and set the call-backs for Jordan instead of Sam.

Before you automate it

## What REsimpli allows, and what to know first

- REsimpli fires Lead Status Change automations on status changes made by hand or by another automation, but not on bulk status changes or imports.
- Every REsimpli pipeline starts with New Lead and Under Contract, and Under Contract can be neither renamed nor removed; an account holds up to 20 pipelines with up to 20 stages each.
- Moving a REsimpli lead to Dead Leads requires a reason, records it in the activity log, and asks whether to clear the lead's tasks.
- REsimpli keeps running a lead's automations after it is marked dead unless you build a Lead Status Change automation on Dead Lead with a Stop other automations step.
- REsimpli's Outgoing Call Outcome trigger reacts to the outcome logged on the call, not the call itself, and the status change shows up about a minute later.

update\_lead\_status, add\_lead\_note and create\_task change only your own REsimpli data and reach no one else, so they run without asking first.

Sources: [REsimpli Help: Move a lead based on the call result](https://help.resimpli.com/en/articles/17269197-how-to-move-a-lead-to-a-different-status-based-on-the-call-result-in-resimpli) · [REsimpli Help: Understanding automation triggers](https://help.resimpli.com/en/articles/16762612-understanding-automation-triggers-in-resimpli) · [REsimpli Help: Leads and Pipelines FAQ](https://help.resimpli.com/en/articles/16165515-leads-and-pipelines) · [REsimpli Help: Stop automations when a lead is moved to Dead Lead](https://help.resimpli.com/en/articles/17120003-how-to-stop-automations-when-a-lead-is-moved-to-dead-lead-in-resimpli)

REST

## Call update\_lead\_status from a script

curl

```
curl https://cotlet.dev/api/v1/resimpli/update_lead_status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lead_id":"66f1c2a9e4b0a1d3c8f20417","status_id":"64a0d5b2c91e7f0012ab33c6"}'
```

Example response

```
{
"lead_id": "66f1c2a9e4b0a1d3c8f20417",
"property_address": "12 Oak St, Columbus, OH 43215",
"pipeline": "Acquisitions",
"status": "Under Contract",
"previous_status": "Contact Made",
"updated_at": "2026-10-11T14:32:05-04:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is resimpli\_update\_lead\_status. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/resimpli-api-mcp-server#automations)

Tools

## REsimpli tools this automation uses

__Cotlet REsimpli tools used to update REsimpli lead statuses and notes after a calling session__
| Tool | Parameters |
| -------------------- | --------------------------------------------------- |
| list\_pipelines | none |
| list\_leads | search, pipeline\_id, status\_ids, tag, page, limit |
| get\_lead | lead\_id |
| update\_lead\_status | lead\_id, status\_id, pipeline\_id |
| add\_lead\_note | lead\_id, text |
| create\_task | lead\_id, title, due\_at, assignee\_id |

[All 15 REsimpli tools with descriptions](https://cotlet.dev/integrations/resimpli-api-mcp-server#tools)

## Frequently asked questions

### Does the agent fill in the Offers section of the lead?

No. REsimpli offers record the offeror, date, price and format, and Cotlet has no tool for them yet. The agent writes the offer into a note, and you can copy it into Offers when you send the contract.

### Will my status-change automations still run?

REsimpli fires Lead Status Change automations on single changes made by hand and skips bulk changes. The agent moves leads one at a time, and its report names every lead it moved so you can check the automation enrollment of any of them.

## More REsimpli automations

- [Reactivate REsimpli dead leads with a drip campaign](https://cotlet.dev/integrations/resimpli-api-mcp-server/reactivate-dead-leads-with-a-drip)
- [REsimpli API and MCP server: every tool](https://cotlet.dev/integrations/resimpli-api-mcp-server)
- [All use cases](https://cotlet.dev/use-cases)

## Give your agent access to REsimpli.

Free 7-day trial with 5,000 credits, no card needed. Cotlet is independent and not affiliated with REsimpli.

[Request access](https://cotlet.dev/app/signup?app=resimpli)