/
/
Move Dynamics 365 Sales deals forward with every change explained
For sales reps and managers who want stage, probability and close date changes sense-checked and recorded, just by asking their AI assistant.
On this page
Connector
Connect Microsoft Dynamics 365 Sales, pick your AI tool and paste the prompt.
The problem
Forecast changes with no reason and numbers that do not add up
Moving an opportunity forward is quick to do and easy to do badly: a close date in the past, a later stage with lower probability or revenue the products do not support. The reason is rarely written down, so nobody knows why the forecast moved.
Without PopdockAI
- Edit the stage, probability and date by hand
- Leave a close date in the past
- Change revenue without checking the products
- Forget to note why it changed
With PopdockAI
- Closed deals are refused
- Close date, probability and revenue are sense checked
- Revenue changes over 25 percent must match the products
- After you confirm, only changed fields are saved with a note
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Apply `{change}` to the opportunity `{opportunity-topic}` (id `{opportunity-id}`), after the user has seen the before and after, and record the reason as a note.
**Step 1: Read the current state**
Call `dynamics-365-sales-get-opportunities` with `topic` = `{opportunity-topic}`. If it matches none or more than one, stop and ask. Note the current `sales-stage`, `probability`, `est-revenue`, `est-close-date`, `rating` and `status`. If the opportunity is not open, stop: closed opportunities are not updated here.
**Step 2: Sense-check the change**
Turn `{change}` into field values for `sales-stage`, `probability`, `estimated-revenue`, `estimated-close-date`, `rating` or `description`. Then check:
* a close date must not be in the past
* probability must be a whole number from 0 to 100, and should rise as the stage advances; flag a later stage with a lower probability
* a revenue change of more than 25% should be checked against `dynamics-365-sales-get-opportunityproducts` (with `opportunity` = the topic); say whether the products support it
**Step 3: Confirm**
Show a before and after table of only the fields that change, plus any warnings from Step 2, and the note text that will record the reason. Ask for one confirmation.
**Step 4: Write**
1. `dynamics-365-sales-update-opportunity` with `id` = `{opportunity-id}` and only the changed fields.
2. `dynamics-365-sales-create-note` with `regarding-id` = `{opportunity-id}`, `title` = "Opportunity updated", and `text` = what changed and why.
**Step 5: Verify**
Call `dynamics-365-sales-get-opportunities` with `topic` again and confirm the new values are stored. Report any field that did not change as expected.
**Rules & Guidelines:**
* No read tool returns a record's GUID. A GUID for an existing record must come from the user: it is the `id=` value in the browser address bar when the record is open in Dynamics 365. Never invent, reuse or guess one.
* Status, stage, priority, rating and type filters take the values listed in each tool's input schema. Pick from that list; never guess a label.
* The only write tools this prompt may call are `dynamics-365-sales-update-opportunity` and `dynamics-365-sales-create-note`, each once, after the confirmation.
* Pass only the fields being changed. Never blank a field the user did not mention.
**Validation:**
* If `{opportunity-id}` is not a GUID, stop and explain where to find it.
* If `{change}` does not map clearly to fields, ask what is meant before changing anything.Who it's for
One answer, three teams that use it
Account executives
Update deals quickly and correctly
Move a deal forward in one message, with any mistakes flagged before saving.
Move the Fabrikam fleet tablets opportunity to Develop at 40 percent, closing 15 December. Here is the record ID.
Sales managers
Know why the forecast moved
Every change gets a note explaining it, so reviews are about the deal, not the data.
Update the Northwind racking opportunity revenue to 52,000 and note that they added a second site.
Revenue operations
Keep the pipeline credible
Past close dates and stage probability mismatches are caught at entry.
Push the close date on the Contoso ERP upgrade opportunity to January 31 and lower probability to 50 percent.
How it works
What PopdockAI does when you ask
You name the opportunity, give its record ID and describe the change, and your AI assistant checks it makes sense. You see the before and after and the note before anything is saved.
01
Ask
You name the opportunity, give its record ID and describe the change.
02
Check
It reads the deal and tests close date, probability and revenue against the products.
03
Confirm
You see a before and after table with warnings and the note text.
04
Update
It saves only the changed fields, adds the note and reads the values back.
What PopdockAI provides
The tools behind the answer
Ready made tools for Microsoft Dynamics 365 Sales and one secure connection to your AI tool. No code, no exports.
microsoft-dynamics-365-sales-get-opportunities
microsoft-dynamics-365-sales-get-opportunityproducts
microsoft-dynamics-365-sales-update-opportunity
microsoft-dynamics-365-sales-create-note
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Forecast changes that are checked and explained
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
