Continue a sales conversation across calls and messages
Preserve conversation context so a voice assistant can resume a call and prepare relevant follow-up messages.
How this works
Preserve conversation context so a voice assistant can resume a call and prepare relevant follow-up messages.
Maintain a single customer conversation state across calls and messages. Preserve what was agreed, what remains unanswered and which channel the customer authorized, while preventing an old offer or mistaken identity from carrying into the next interaction.
Before you start
Defined operating scope
Prospects continue the same conversation across callbacks, messages, and email.
Required source material
Obtain Call history; Customer questions; Product and payment information. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
The person reached is not the original contact. Do not reveal remembered account details; re-establish authorized identity.
Prepare the inputs
- conversation_id
- Required
Account and interaction references
Resolve identity across channels.
- call_state
- Required
Outcome, commitments and open questions
Keep evidence and dates for remembered facts.
- current_offer
- Required
Product and payment terms
Verify freshness before repeating prior details.
- followup_preferences
- Required
Requested callback or message channel
Retain timing and opt-out constraints.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check conversation_id, call_state, current_offer, followup_preferences 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 conversation_id and any missing required fields.
Save the outcome and unresolved questions after a call
- Save a concise state after the call with confirmed facts, unresolved questions and requested follow-up timing.
- Compare remembered facts with the source interaction and current offer version.
Checkpoint: A saved intermediate result for: Save the outcome and unresolved questions after a call.
Resume a requested callback with the existing context
- Before a requested callback, verify identity and refresh current terms; disclose when an earlier detail has changed.
- Check channel preferences, timing and actual delivery or transfer receipts.
Checkpoint: A saved intermediate result for: Resume a requested callback with the existing context.
Prepare a relevant message or email follow-up
- Draft a message that answers the outstanding question and references the prior conversation honestly without overclaiming agreement.
- Compare remembered facts with the source interaction and current offer version.
Checkpoint: A saved intermediate result for: Prepare a relevant message or email follow-up.
Escalate exceptions or requests for a person
- Escalate unsupported exceptions or a request for a person, recording actual transfer or message-delivery status.
- Check channel preferences, timing and actual delivery or transfer receipts.
Checkpoint: A saved intermediate result for: Escalate exceptions or requests for a person.
Package the result and unresolved work
- Verify identity, consent, remembered facts, and the accuracy of offers or commitments.
- Conversation memory does not grant permission for new channels or repeated contact.
Checkpoint: A coordinated follow-up conversation across supported channels. Unresolved items remain visible in the review record.
Decisions along the way
The person reached is not the original contact.
Do not reveal remembered account details; re-establish authorized identity.
An offer changed since the prior call.
Explain the current terms and obtain confirmation before treating an old agreement as applicable.
The customer revoked the follow-up channel.
Stop that channel and preserve the restriction across future runs.
What you will produce
cs-video-cross-channel-sales-follow-up-result.json
JSONA coordinated follow-up conversation across supported channels. Label proposed and completed states separately.
Include: conversation_id · confirmed_facts · open_questions · current_offer_version · authorized_channel · followup_draft · delivery_state · status · evidence_reference · review_note
cs-video-cross-channel-sales-follow-up-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving followup_preferences.
Include: source_reference · question · owner · next_action
Check the result
- Compare remembered facts with the source interaction and current offer version.
- Check channel preferences, timing and actual delivery or transfer receipts.
- Inspect conversation_id and call_state in both the original and output; confirm that record identity and interpretation survived the transformation.
- Verify identity, consent, remembered facts, and the accuracy of offers or commitments.
When something goes wrong
The person reached is not the original contact.
Do not reveal remembered account details; re-establish authorized identity. Retain the affected evidence and recovery status.
An offer changed since the prior call.
Explain the current terms and obtain confirmation before treating an old agreement as applicable. Retain the affected evidence and recovery status.
The customer revoked the follow-up channel.
Stop that channel and preserve the restriction across future runs. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Continue a sales conversation across calls and messages for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Call C-1 ends with a request for an email explaining monthly payment terms. The next day the approved price changes before the email is sent.
Expected result
Synthetic expected result: Draft identifies the current price and notes the changed terms for salesperson review. It does not repeat the old price as a valid commitment or initiate an unrequested callback.
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 context retained correctly; follow-up accuracy and successful human transfers.
Stop or revise
The customer revoked the follow-up channel. Pause affected records and apply this recovery: Stop that channel and preserve the restriction across future runs.
Keep the scope clear
- Conversation memory does not grant permission for new channels or repeated contact.
- Do not infer acceptance of offers from continued conversation or unanswered messages.
Check before using
Verify identity, consent, remembered facts, and the accuracy of offers or commitments.
Business activities
- Handle inbound enquiries
- Run sales conversations and proposals
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: Call history · Customer questions · Product and payment information
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow