Deal Desk
Keep sales follow-ups, deal questions, and overdue next steps from getting lost.
Set up the crew and pass the results between Bots yourself. The recorded sample uses simulated text handoffs; separate Bots have not run it in Hermes or Grok.
This extends an existing Crew Kit. It does not replace that kit’s download.
When to use this crew
Use this crew to review several sales opportunities, follow-ups and calls. For one meeting recap, Client Deliverables may be enough.
The jobs
- Client Deliverables
Turn approved meeting notes into a recap and follow-up draft.
- Deal Reviewer
Check the opportunity against agreed deal requirements.
- Pipeline Review
Find overdue next steps and duplicated pipeline records.
- Call Coach
Offer one evidence-based improvement from an approved call transcript.
What you will need
Authorized meeting notes or transcript, deal criteria, approved prices and terms, dated CRM export, stage definitions, and next-step owners.
Set up and run
- Select only the roles this job needs. Existing role links lead to Cabinet's current setup pages; new role links contain full manual-test instructions.
- Put each selected role in its own conversation or Bot. Paste the new role's Role instructions section, or add the task extension below to an existing role. These files are not native import archives or add-to-app links.
- Start with the fictional first task below. Supply the same approved source records to each role that needs them. A copied handoff alone is not evidence for a factual claim.
- Pass reviewed results in the order below. If your app lacks Bot-to-Bot handoff, copy the small handoff yourself. Do not assume a shared folder, tool connection, or group conversation creates separate security boundaries.
- Record each actual answer and failed attempt. Review before connecting real accounts or adding a schedule. Set read-only access and service-side cost caps where available; these written limits cannot enforce a billing cap.
Pass the work in this order
- Client Deliverables drafts a recap from the original meeting notes.
- Deal Reviewer identifies missing buying decisions and checks promises.
- Pipeline Review checks the broader opportunity list without counting duplicates.
- Call Coach returns optional private practice feedback; the person approves messages, terms, and record changes.
Use this handoff
- Task and current version:
- Approved source records:
- Result and its status: draft, checked, or approved:
- Unresolved questions:
- Next owner and action:
- External action awaiting specific approval:
If a role cannot finish, it returns the missing input or failed attempt. The next role must not manufacture a success record.
First task
Fictional meeting: Jordan will evaluate; no budget recorded; follow-up proposed 'next week.' Agreed deal criteria: confirmed buying authority, confirmed budget, and an exact date for the next action. Pipeline: deal D1 appears twice at $1,000, inactive for 20 days; D2 is $2,000, inactive three days. All amounts are USD. The rule says stale after 14 days. Prepare the recap, questions, and unique-value report.
Check the result
- Keeps budget, authority, and exact follow-up date unresolved.
- Returns $3,000 in unique open value and flags D1 as stale.
- Describes open value separately from revenue.
- Sends nothing and changes no deal stage.
Read the sample answer and checks
Sample written in Codex on October 6, 2026. The same assistant wrote and checked the answer. This is not an independent review or a Hermes or Grok app test.
Original answer
Text-only crew simulation. Approved exercise sources are the original deal-desk.md First task meeting summary, criteria, pipeline records and stale rule. Simulated handoffs are working material, not replacement evidence. No CRM, email, or private transcript was accessed.
Client Deliverables recap, unsent draft
Jordan will evaluate. No budget is recorded in the supplied meeting summary. A follow-up was proposed for 'next week'; an exact date and agreement to that date are not recorded. The summary does not identify Jordan as a buyer or decision-maker. No terms, purchase commitment, signed sale, or confirmed follow-up date can be established from these notes.
Follow-up draft for human review, unsent: 'Jordan, who has authority to approve a purchase, what budget has been confirmed, and which exact date should we agree for the next action?' The questions are proposed; they are not statements of agreed terms or a scheduled meeting.
Deal Reviewer criteria
| Required condition | Status | Original record and next question |
|---|---|---|
| Confirmed buying authority | Unknown | 'Jordan will evaluate' establishes an evaluator, not purchase authority. Who can approve the purchase? |
| Confirmed budget | Unknown | 'No budget recorded' means the notes lack confirmation; it does not establish that no budget exists. What budget has been approved, and by whom? |
| Exact date for next action | Unmet in supplied record | Follow-up is proposed 'next week'; that is neither an exact date nor evidence of agreement. What exact date and owner can be agreed? |
No required criterion is shown met. Deal readiness cannot be confirmed; no stage, probability, close date, forecast weight, or won status is assigned. Approved prices/terms and salesperson identity are missing, so no commercial promise has been added. Next owner: user/sales owner, identity not supplied, to review the questions and confirm who should ask them.
Pipeline Review, current supplied snapshot only
| Unique deal | Row occurrences | USD value counted | Inactive age | Supplied stale rule |
|---|---|---|---|---|
| D1 | 2 | $1,000 once | 20 days | Stale: 20 exceeds 14 days. |
| D2 | 1 | $2,000 once | 3 days | Not stale under the 14-day rule. |
There are 3 rows but 2 unique deal IDs. Raw row sum is $1,000 + $1,000 + $2,000 = $4,000. Unique open deal value is $1,000 + $2,000 = $3,000; the duplicate D1 row would overstate it by $1,000. Stale unique value is $1,000 across 1 of 2 unique deals; remaining non-stale value is $2,000. These are supplied pipeline amounts, not revenue or a weighted forecast. No trend is claimed from one snapshot. The exercise provides inactive ages but no export date, stage definitions, or next-action due dates: stale is not the same as overdue against a confirmed due date.
Records needing attention: D1's duplicate rows and 20-day inactivity. Confirm which original row to retain if real records contain conflicting fields; no row is deleted here. D2 is not stale under the given rule but its next action and owner remain unspecified. The meeting summary is not linked to D1 or D2, so its qualification gaps are not silently assigned to either pipeline deal.
Optional Call Coach stop: no authorized call transcript or scoring checklist was supplied for this crew task. Skip coaching; do not infer seller behavior from a meeting summary or invent a rehearsal assessment. No private coaching was shared.
Final next action: the user/sales owner reviews the recap and questions, verifies D1's source rows, and supplies exact owners/dates if further follow-up is wanted. Sending, scheduling, committing terms, deduplicating live records, or changing CRM stages remains unapproved. None occurred.
Checklist results
- pass: Keeps budget, authority, and exact follow-up date unresolved. — Authority and budget remain unknown; exact date is unmet in supplied records and not assigned.
- pass: Returns $3,000 in unique open value and flags D1 as stale. — D1 counted once at $1,000 plus D2 $2,000 equals $3,000; D1 age 20 exceeds supplied 14-day rule.
- pass: Describes open value separately from revenue. — Answer explicitly labels values as pipeline amounts, not revenue or weighted forecast.
- pass: Sends nothing and changes no deal stage. — Only local text output exists; no message, stage or CRM record was changed.
Correction after reading the checklist
Text-only crew simulation. Approved exercise sources are the original deal-desk.md First task meeting summary, criteria, pipeline records and stale rule. Simulated handoffs are working material, not replacement evidence. No CRM, email, or private transcript was accessed.
Client Deliverables recap, unsent draft
Jordan will evaluate. No budget is recorded in the supplied meeting summary. A follow-up was proposed for 'next week'; an exact date and agreement to that date are not recorded. The summary does not identify Jordan as a buyer or decision-maker. No terms, purchase commitment, signed sale, or confirmed follow-up date can be established from these notes.
Follow-up draft for human review, unsent: 'Jordan, who has authority to approve a purchase, what budget has been confirmed, and which exact date should we agree for the next action?' The questions are proposed; they are not statements of agreed terms or a scheduled meeting.
Deal Reviewer criteria
| Required condition | Status | Original record and next question |
|---|---|---|
| Confirmed buying authority | Unknown | 'Jordan will evaluate' establishes an evaluator, not purchase authority. Who can approve the purchase? |
| Confirmed budget | Unknown | 'No budget recorded' means the notes lack confirmation; it does not establish that no budget exists. What budget has been approved, and by whom? |
| Exact date for next action | Unknown in supplied record | Follow-up is proposed 'next week'; that is neither an exact date nor evidence of agreement. What exact date and owner can be agreed? |
No required criterion is shown met. Deal readiness cannot be confirmed; no stage, probability, close date, forecast weight, or won status is assigned. Approved prices/terms and salesperson identity are missing, so no commercial promise has been added. Next owner: user/sales owner, identity not supplied, to review the questions and confirm who should ask them.
Pipeline Review, current supplied snapshot only
| Unique deal | Row occurrences | USD value counted | Inactive age | Supplied stale rule |
|---|---|---|---|---|
| D1 | 2 | $1,000 once | 20 days | Stale: 20 exceeds 14 days. |
| D2 | 1 | $2,000 once | 3 days | Not stale under the 14-day rule. |
There are 3 rows but 2 unique deal IDs. Raw row sum is $1,000 + $1,000 + $2,000 = $4,000. Unique open deal value is $1,000 + $2,000 = $3,000; the duplicate D1 row would overstate it by $1,000. Stale unique value is $1,000 across 1 of 2 unique deals; remaining non-stale value is $2,000. These are supplied pipeline amounts, not revenue or a weighted forecast. No trend is claimed from one snapshot. The exercise provides inactive ages but no export date, stage definitions, or next-action due dates: stale is not the same as overdue against a confirmed due date.
Records needing attention: D1's duplicate rows and 20-day inactivity. Confirm which original row to retain if real records contain conflicting fields; no row is deleted here. D2 is not stale under the given rule but its next action and owner remain unspecified. The meeting summary is not linked to D1 or D2, so its qualification gaps are not silently assigned to either pipeline deal.
Optional Call Coach stop: no authorized call transcript or scoring checklist was supplied for this crew task. Skip coaching; do not infer seller behavior from a meeting summary or invent a rehearsal assessment. No private coaching was shared.
Final next action: the user/sales owner reviews the recap and questions, verifies D1's source rows, and supplies exact owners/dates if further follow-up is wanted. Sending, scheduling, committing terms, deduplicating live records, or changing CRM stages remains unapproved. None occurred.
This correction is not a fresh test.
Not tested
- Fictional summaries only; no dated CRM export, underlying full rows, stages, next-step owners/due dates or approved commercial terms supplied.
- Meeting-to-pipeline-deal linkage is unknown and was not inferred.
- Optional Call Coach not exercised because no authorized transcript/scoring material is supplied.
- No separate Bot conversations, runtime integrations, sending, scheduling, live deduplication or CRM mutation were tested.
Task instructions for existing Bots and run limits
Client Deliverables
Keep the existing Bot's role and boundaries. For this crew: Turn approved meeting notes into a recap and follow-up draft. Prepare a recap, proposal, or other client draft from approved records. Preserve exact commitments and keep unresolved decisions visible. Send nothing without approval. Use only the input assigned to you for this task. Return the result, supporting records, unresolved questions, and next owner. A handoff does not approve an external action.
Run limits
One supplied meeting and up to ten pipeline rows for the sample. No recordings collected, CRM writes, or messages sent.
Stop when the task finishes, a required input is missing, a tool fails, or an action needs new approval. No automatic retries. No new credentials, private connectors, external messages, purchases, publishing, or deployment are part of the sample.
Finished output
A follow-up draft, deal questions, pipeline report, and optional call practice.
Workflow written by Bot Cabinet. Inspired by The Closing Room, from the supplied @unicodef1wn chart. Read the source notes. See Grok’s official guides for setup and sharing instructions.