AI agent team guide
AI Sales Agents for Stalled Deals: Decide What Happens Next
A deal-level advance, pause or close decision brief with owner and next checkpoint

A stalled deal needs a decision, not another generic follow-up. Use an AI sales team to compare the last accepted next step with the latest evidence, identify the unresolved dependency and prepare a relevant option. Sometimes the right outcome is a useful conversation. Sometimes it is an honest pause or a corrected forecast assumption.
Sales Pipeline Analyst identifies the exception, Closer prepares the next-action brief, Mutual Action Planner checks commitments and Researcher verifies context that could change the conversation. The workflow does not infer customer intent from silence or keep an opportunity alive by inventing a close date.
Build your four-agent team
| Agent template | Its job on the team | Bring to its setup | Reviewable return | Team |
|---|---|---|---|---|
Sales Pipeline AnalystLead agent | Explain why the opportunity needs review. | Authorized pipeline snapshot, stage definitions and prior accepted next steps. | A source-linked exception brief separating risk from missing updates. | Add to team |
CloserSupporting agent | Prepare a useful next-action option. | The accepted exception brief, relationship history and actual offer. | A proposed conversation, pause or follow-through action for owner review. | Add to team |
Mutual Action PlannerSupporting agent | Check the shared action path. | Documented customer commitments, dependencies and actual owners. | A reconciled draft showing agreed, proposed and unresolved steps. | Add to team |
ResearcherSupporting agent | Verify relevant current context. | Permitted sources and a specific question about the opportunity. | A short dated fact pack without guessed buying intent. | Add to team |
Set up your team in Finta
- Add each template individually. Use the Add to team action for each named coworker, review the import setup and complete its Getting Started skill.
- Give each role the right context. State the shared objective, then supply the authorized documents, notes or exports that role needs. Do not assume an unconnected system is available.
- Review the handoff. Accept or correct one return before giving its evidence and open questions to the next coworker. Importing four templates does not itself run a bulk team.
- Make recurrence deliberate. Complete a useful manual pass first. Review any supported routine and enable it only when the scope, inputs and permissions are right.
Prepare the evidence
- The current opportunity snapshot and the source of stage and date fields.
- The last actual customer commitment and any subsequent response.
- Known dependencies and owners who can confirm them.
- The seller’s approved options and a named forecast or disposition owner.
Run the workflow
1. Define the exception from the record
Name what changed or remains unresolved. An old last-contact date can justify review, but it does not by itself explain why a customer has not responded. Separate an overdue agreed action from a seller’s hoped-for milestone.
2. Reconcile commitments before writing another email
Mutual Action Planner checks who accepted each next step and whether the prerequisite exists. Closer should not ask for a meeting merely because the opportunity is old. Identify the decision the customer can usefully make now.
3. Check relevant context, not imagined urgency
Researcher can verify a public development or supplied note. Do not turn it into a claim about internal budgets, deadlines or intent. If no new evidence exists, a clear permission-to-pause question can be more appropriate than manufactured urgency.
4. Let the owner choose the disposition
Prepare options such as clarify a dependency, propose a scoped next conversation, pause or close the internal opportunity. The authorized owner decides and makes supported record changes. Keep forecast corrections separate from customer communication.
A fictional stalled-deal decision register
This invented example contains no real prospect, expected revenue or forecast recommendation.
| Evidence | Useful interpretation | Proposed decision |
|---|---|---|
| A seller proposed a technical session; the customer did not confirm it. | The session is proposed, not overdue customer work. | Ask whether it is relevant before rescheduling it. |
| A customer requested a security answer that remains incomplete. | There is a real unresolved prerequisite. | Assign an internal answer owner before asking for a purchase decision. |
| The expected close date passed without a new source. | The forecast assumption needs review. | Ask the authorized owner to reassess the date separately. |
| No response follows a relevant reviewed message. | Intent is still unknown. | Consider a respectful pause rather than repeated urgency claims. |
The desk improves pipeline integrity when it helps a person make a defensible decision. More follow-up drafts alone do not establish progress.
Copy the team brief
Review [one opportunity or bounded exception cohort] at [cutoff].
Pipeline Analyst: explain the exception from actual records.
Mutual Action Planner: separate accepted commitments from seller proposals and missing dependencies.
Researcher: verify only relevant current context.
Closer: prepare a useful next conversation, clarification or pause option.
Return evidence, unresolved prerequisite, proposed disposition, owner and draft if useful.
Do not infer intent from silence, change stages or forecasts, send messages or manufacture urgency.Review the return
- The brief identifies a real decision rather than simply an old record.
- Customer commitments and seller proposals are clearly separated.
- Only authorized people accept disposition, forecast changes or communication.
Questions before you start
Does no reply mean the deal is lost?
No. Silence is incomplete evidence. It can justify a bounded follow-up or internal review, but it does not establish the customer’s reason or final decision.
Should AI move the close date?
This workflow prepares the evidence for a forecast owner to review. A new date should have a defensible basis rather than be rolled forward to keep the pipeline looking current.
Sources and next steps
This playbook uses the current published Finta marketplace packages linked in the team table. Open each profile to review its instructions, context, Skills and any routines before importing.