Build an action plan for an existing customer relationship
Combine correspondence, meetings, tasks, and product context to identify unresolved tensions in an existing account. Prepare a concrete plan for the account owner to discuss and act on.
How this works
Combine correspondence, meetings, tasks, and product context to identify unresolved tensions in an existing account. Prepare a concrete plan for the account owner to discuss and act on.
Build an account plan from the relationship’s unresolved commitments, conflicting expectations and current product context. Keep customer statements separate from internal interpretations and propose actions the owner can verify before making new promises.
Before you start
Defined operating scope
Account owners need to reconcile relationship history, outstanding tasks, and product-use context.
Required source material
Obtain Account correspondence and meeting notes; Open tasks; Relevant product-use signals. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
Internal notes contradict a customer’s explicit statement. Present both sources and ask the owner to reconcile the current understanding.
Prepare the inputs
- account_id
- Required
Customer and owner identifier
Scope all records to this relationship.
- relationship_history
- Required
Messages and meeting notes
Preserve chronology and participant roles.
- open_tasks
- Required
Owners, due dates and completion evidence
Treat stale status as uncertain.
- usage_context
- Required
Relevant permitted product signals
Use dated account-level evidence.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check account_id, relationship_history, open_tasks, usage_context before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected account_id and any missing required fields.
Collect the relationship history for the selected account
- Collect the relevant history and latest task state, noting missing channels or periods.
- Trace each proposed action to an unresolved issue and current evidence.
Checkpoint: A saved intermediate result for: Collect the relationship history for the selected account.
Separate confirmed commitments, conflicts, and missing context
- Separate confirmed agreements, unmet expectations and internal hypotheses, retaining supporting and contrary evidence.
- Check that fulfilled commitments and superseded expectations are not presented as active conflicts.
Checkpoint: A saved intermediate result for: Separate confirmed commitments, conflicts, and missing context.
Connect unresolved issues to possible next actions
- Map unresolved issues to possible next actions with prerequisites, responsible roles and questions to clarify.
- Trace each proposed action to an unresolved issue and current evidence.
Checkpoint: A saved intermediate result for: Connect unresolved issues to possible next actions.
Draft an account plan for the owner to correct and prioritize
- Prepare a prioritized account plan for the owner to correct, then record decisions without assuming customer acceptance.
- Check that fulfilled commitments and superseded expectations are not presented as active conflicts.
Checkpoint: A saved intermediate result for: Draft an account plan for the owner to correct and prioritize.
Package the result and unresolved work
- The account owner confirms the interpretation and owns customer communication. Automated checking of task completion was a proposed extension, not an established part of the example.
- The account owner controls customer communication and commitments.
Checkpoint: An account-specific action plan linked to the underlying relationship evidence. Unresolved items remain visible in the review record.
Decisions along the way
Internal notes contradict a customer’s explicit statement.
Present both sources and ask the owner to reconcile the current understanding.
A task appears open but delivery evidence exists.
Check acceptance and status separately before proposing another reminder.
A suggested action creates a new commercial commitment.
Label it a proposal for owner approval rather than an agreed next step.
What you will produce
customer-history-to-account-action-plan-result.json
JSONAn account-specific action plan linked to the underlying relationship evidence. Label proposed and completed states separately.
Include: account_id · confirmed_commitments · conflicts · unresolved_issues · proposed_actions · owners · evidence_gaps · status · evidence_reference · review_note
customer-history-to-account-action-plan-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving usage_context.
Include: source_reference · question · owner · next_action
Check the result
- Trace each proposed action to an unresolved issue and current evidence.
- Check that fulfilled commitments and superseded expectations are not presented as active conflicts.
- Inspect account_id and relationship_history in both the original and output; confirm that record identity and interpretation survived the transformation.
- The account owner confirms the interpretation and owns customer communication. Automated checking of task completion was a proposed extension, not an established part of the example.
When something goes wrong
Internal notes contradict a customer’s explicit statement.
Present both sources and ask the owner to reconcile the current understanding. Retain the affected evidence and recovery status.
A task appears open but delivery evidence exists.
Check acceptance and status separately before proposing another reminder. Retain the affected evidence and recovery status.
A suggested action creates a new commercial commitment.
Label it a proposal for owner approval rather than an agreed next step. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Build an action plan for an existing customer relationship for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Customer A-9 expected weekly updates; internal notes say monthly. Two updates were sent, but a requested migration estimate remains unanswered.
Expected result
Synthetic expected result: Plan highlights cadence conflict and the missing estimate as separate issues. Owner should confirm cadence and assign the estimate; the assistant does not promise a delivery date.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure owner-confirmed issues and next actions; incorrect interpretations and preparation time.
Stop or revise
A suggested action creates a new commercial commitment. Pause affected records and apply this recovery: Label it a proposal for owner approval rather than an agreed next step.
Keep the scope clear
- The account owner controls customer communication and commitments.
- Product-use signals support questions; they do not establish sentiment or churn probability.
Check before using
The account owner confirms the interpretation and owns customer communication. Automated checking of task completion was a proposed extension, not an established part of the example.
Business activities
- Run sales conversations and proposals
- Deliver recurring client work
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Account correspondence and meeting notes · Open tasks · Relevant product-use signals
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow