Automate the collection of approved information, controlled proposal assembly, internal reminders and follow-up drafts. Before anything is sent, a responsible person should review the exact version, recipient, channel, price, scope, terms and claims. Enroll only a genuine opportunity with documented contact context and applicable permission. Stop when there is a reply, refusal, opt-out, closed opportunity, invalid contact, dispute or material change.
That is the useful boundary: automation prepares and checks; an authorized person controls consequential commercial commitments and external communication. This guide gives you a copyable Proposal-to-Follow-up Control Pack, an observable state model, a fictional example and pre-launch tests.
It does not promise more sales, a universal “best cadence,” legal compliance or an autonomous salesperson. It is an educational operating model, not legal advice or a substitute for reviewing the rules that apply to your audience, jurisdiction and channel.
Treat the proposal and its follow-up as one controlled workflow
A proposal is not just a PDF. It combines an opportunity, recipient, approved offer, scope, exclusions, price, conditions, validity, claims and a specific version. Follow-up is not a separate stream of generic messages. It must remain attached to that exact commercial context.
If those records drift apart, a polished automation can send the wrong price, follow up after a rejection, refer to an obsolete scope or contact someone who asked it to stop. The workflow therefore needs one stable opportunity_id, versioned proposal data, a current state and a suppression check before every external action.
Use process mapping to identify sources, exceptions and owners before implementing this example. If proposal follow-up is being considered as your first automation, first check whether it is a safe pilot.
Automate preparation before automating delivery
Good early candidates for automation include:
- reading structured fields from approved sources;
- assembling a draft from authorized content blocks;
- checking required fields, version and validity;
- creating an internal review task;
- preparing a follow-up draft;
- checking for replies, closure and suppression immediately before sending;
- updating the ledger after a channel result is confirmed.
Keep a responsible person in control of:
- price, discount, scope, exclusions, deadline, contractual terms and validity;
- claims about capability, availability, results or customers;
- exceptions to commercial policy;
- uncertain recipient, channel, permission or opportunity state;
- objections, disputes, complaints and material negotiations;
- approval of the exact proposal or message and its external send.
AI may help draft or classify, but it must not invent a price, term, availability statement, reference customer or expected result. Missing evidence should create a review task, not plausible text.
Separate three kinds of communication
Do not treat every message called “follow-up” as the same activity:
- a receipt confirmation or reminder tied directly to a requested proposal;
- later commercial communication within a documented relationship;
- cold outreach or mass communication.
The context, reasonable expectation, permission and legal treatment can differ. This guide covers the first category and carefully bounded parts of the second. It does not teach cold prospecting, bought lists, scraping or bulk messaging.
For WhatsApp, use official products and current policies. The WhatsApp Business Messaging Policy says a business may contact people only after they have provided their number or username and opted in to subsequent messages or calls. It also requires businesses to respect requests to block, discontinue or opt out. For the Business Platform, business-initiated conversations use approved message templates, and messages outside the applicable 24-hour customer-service window require approved templates. The policy also requires clear paths to human escalation when automation responds during that window.
Channel policy is not the same as law. In Brazil, the ANPD guide to legitimate interest describes a contextual analysis of purpose, necessity, reasonable expectations, balancing and safeguards for non-sensitive personal data. It does not make proposal follow-up automatically lawful.
Rules also differ across jurisdictions. The UK ICO guidance on electronic mail marketing explains consent and a limited “soft opt-in,” together with identification and opt-out requirements. Its detailed PECR guidance says silence or inactivity is not consent. In the United States, the FTC’s CAN-SPAM materials address truthful headers and subject lines and an opt-out method for covered commercial email. None of these sources creates one worldwide rule.
When the applicable basis or permission is unclear, do not send. Ask a competent privacy or legal professional for the real case.
Bind approval to the exact action
“Approved by someone” is too vague. The execution must be able to prove that the approval covers this actor, tool, recipient, channel, proposal or message version, material parameters and time window.
At minimum, the approval record should include:
- a unique
approval_id; - the authorized actor;
- a narrow scope such as
send_proposalorsend_follow_up; - normalized bound parameters;
- the exact recipient and channel;
- proposal and message versions;
- expiration;
- single-use status when one action is authorized.
The decision record and the send mechanism must be separate. Immediately before execution, validation outside the drafting agent compares the current payload with the approved payload, checks expiration and use status, reads the latest opportunity and suppression state and fails closed on any mismatch.
For the full control design—including replay protection, normalized parameters and separation between approval and execution—see how to define human approval in automation.
Use observable states, including an unknown send state
Use states that can be proven from records rather than inferred from hope:
draft → under_review → approved → sending → sent | send_state_unknown
sent → replied → negotiation → accepted | rejected
sent → expired | withdrawn
approved → superseded
any_active_state → suppressed
sending means the action started but the channel result is not yet confirmed. sent requires confirmed evidence from the channel. A timeout after submission leads to send_state_unknown, not “failed.” Retry and any new send remain blocked until the channel or source of truth is reconciled.
An open or click does not prove interest, refusal, acceptance or negotiation. Any reply pauses the sequence for review. A new proposal version never silently inherits approval from the old one.
Build a cadence around purpose, not persistence
There is no universally correct number of messages or interval. Relationship, channel, jurisdiction, proposal complexity and company policy all matter. Each planned step needs a legitimate purpose and a useful next action:
- confirm receipt or invite questions;
- provide or clarify relevant information;
- communicate a real validity date without artificial urgency;
- close the loop respectfully.
For every step, record its enabling event, purpose, channel, local send time, exact draft, applicable approval, deduplication key, stop conditions and human next step.
Before sending, read current state again. Stop on any reply, opt-out, block, complaint, accepted or rejected proposal, closed opportunity, invalid contact, dispute, material proposal change, uncertain permission, expired approval, duplicate key, unknown previous result or failed validation/log lookup.
No reply is not consent. A scheduled message does not outrank a later reply or opt-out.
Copyable Proposal-to-Follow-up Control Pack
Copy this into your operating documentation. Test it with fictional data before connecting any channel.
opportunity:
opportunity_id:
person_or_company:
request_source:
request_date:
declared_need:
owner:
last_confirmed_interaction:
intended_channel:
documented_channel_context_or_permission:
locale:
timezone:
current_state:
suppression_reference:
source_of_truth:
proposal:
proposal_id:
version:
offer:
deliverables: []
exclusions: []
assumptions: []
price:
currency:
approved_price_source:
terms:
validity:
customer_dependencies: []
supplier_dependencies: []
permitted_claims: []
material_field_sources: []
owner:
reviewer:
state: draft / under_review / approved / sending / sent / send_state_unknown / superseded / withdrawn
executable_approval:
approval_id:
actor:
scope: send_proposal / send_follow_up
bound_parameters:
opportunity_id:
proposal_id:
proposal_version:
message_id:
draft_version:
recipient:
channel:
price_source:
validity:
expires_at:
single_use: true
status: unused / consumed / expired / revoked
follow_up_step:
message_id:
purpose:
enabling_event:
planned_local_time:
exact_draft_version:
approval_id:
deduplication_key:
useful_information_or_action:
pre_send_checks:
- current_opportunity_state
- current_reply_and_suppression_state
- exact_payload_matches_approval
- approval_valid_and_unused
- no_confirmed_or_in_flight_duplicate
- no_unreconciled_send_state_unknown
stop_conditions:
- any_reply
- opt_out_or_block
- complaint_or_dispute
- accepted_rejected_or_closed
- invalid_contact
- proposal_superseded_or_expired
- permission_or_state_uncertain
- validation_or_log_failure
human_next_step:
suppression:
subject_channel_or_opportunity:
reason:
scope: opportunity / campaign / channel / global
source:
recorded_at:
systems_and_queues_updated: []
propagation_confirmed:
minimum_retention_and_disposal_rule:
exception_owner:
ledger:
message_id:
opportunity_id:
proposal_id:
proposal_version:
recipient:
channel:
purpose:
approval_id:
deduplication_key:
planned_at:
state_before_action:
state_during_action:
channel_result:
result_confirmed_at:
final_state: sent / send_state_unknown / blocked
reply_or_human_classification:
stop_reason:
next_action:
owner:
This is a Pulse editorial model, not an official template from Meta, ANPD, ICO, FTC, NIST, OWASP or Microsoft.
Fictional example: a design consultancy proposal
The names, addresses and identifiers below are fictional.
opportunity_id: OPP-2041
request:
source: inbound website request
date: 2026-09-22
need: visual identity refresh
owner: commercial lead
contact:
recipient: fictional.client@example.com
channel: email
context: proposal explicitly requested by recipient
locale: en-US
timezone: America/New_York
suppression_state: clear_at_last_check
proposal:
id: PROP-2041
version: v3
scope: approved-brand-refresh-package
price_source: approved-price-table-2026-Q3
exclusions:
- trademark registration
- printing
validity: 2026-10-09
approval_status: approved
executable_approval:
approval_id: APR-2041-v3-email
actor: commercial-director-01
scope: send_proposal
bound_parameters:
opportunity_id: OPP-2041
proposal_id: PROP-2041
proposal_version: v3
recipient: fictional.client@example.com
channel: email
price_source: approved-price-table-2026-Q3
validity: 2026-10-09
expires_at: 2026-10-09T17:00:00-04:00
single_use: true
status: unused
follow_up_approval:
approval_id: APR-2041-FUP-01
actor: commercial-lead-02
scope: send_follow_up
bound_parameters:
message_id: MSG-2041-FUP-01
opportunity_id: OPP-2041
proposal_id: PROP-2041
proposal_version: v3
draft_version: FUP-2041-v1
recipient: fictional.client@example.com
channel: email
expires_at: 2026-10-02T17:00:00-04:00
single_use: true
status: unused
follow_up_plan:
- purpose: confirm receipt and invite questions
message_id: MSG-2041-FUP-01
draft_version: FUP-2041-v1
deduplication_key: OPP-2041:PROP-2041:v3:FUP-01
approval_id: APR-2041-FUP-01
send_only_if:
- proposal_v3_is_still_current
- no_reply_or_suppression
- approval_actor_scope_and_bound_parameters_match
- approval_is_valid_and_unused
- deduplication_key_has_no_confirmed_or_in_flight_send
pre_send_checks:
- read_current_opportunity_state
- read_reply_and_suppression_state
- reconcile_any_send_state_unknown
- validate_recipient_channel_and_timezone
- validate_exact_payload_against_approval
stop_if:
- any_reply
- opt_out
- opportunity_closed
- state_check_failed
ledger:
message_id: MSG-2041-PROP-01
approval_id: APR-2041-v3-email
deduplication_key: OPP-2041:PROP-2041:v3:INITIAL
state_before_action: approved
state_during_action: sending
channel_result: accepted_by_email_provider
result_confirmed_at: 2026-09-25T14:30:04-04:00
final_state: sent
approval_use: consumed
next_action: human_review_before_follow_up
unknown_state_example:
message_id: MSG-2041-FUP-01
state: send_state_unknown
reason: provider_timeout_after_submission
retry_allowed: false
required_action: reconcile_with_channel_before_any_retry
The original request does not remove the need to follow applicable law, channel policy and the recipient’s current wishes. If the recipient replies before the planned follow-up, the reply wins and the pending send stops.
Test the control pack before connecting a real channel
Run these tabletop tests with fictional records and no real external effects:
- A reply arrives seconds before the scheduled send: block it.
- An opt-out is recorded in another system: read and propagate suppression before acting.
- Price or scope changes after approval: invalidate the old version.
- The draft differs from the approved price source: create a human task and block.
- The same trigger arrives twice: allow at most one action to proceed.
- A timeout leaves the previous send unknown: block retry until reconciliation.
- Channel context or permission is missing: block.
- Recipient or timezone is missing: block or route to review.
- The reviewer rejects the proposal or message: do not execute.
- Reply, suppression, approval or log lookup fails: fail closed.
- The proposal expires before the next step: stop and review; do not manufacture urgency.
- An out-of-office reply arrives: do not classify it as acceptance, refusal or permission to persist.
- The opportunity closes in another channel: cancel pending work.
- The person asks to stop in free-form language: route to a person and apply suppression without requiring a magic keyword.
Success means no message leaves with mismatched version, approval, recipient or context; reply and suppression outrank the schedule; duplication and unknown states are contained; and the ledger records decisions without unnecessary personal data.
For unknown sends, reconciliation and recovery, use the automation failure contingency plan. To include review and maintenance costs before implementation, estimate the real cost of the workflow.
When not to automate this workflow
Keep the process manual or obtain specialist support when:
- the workflow is cold outreach, scraped contacts, bought lists or mass messaging;
- no approved source exists for price, scope or terms;
- the matter involves a complex negotiation, dispute, complaint or exception;
- the product, service or communication is regulated;
- sensitive data, children, health, credit, employment or decisions about people are involved;
- the channel lacks an official, authorized integration;
- replies, opt-outs, duplicates or unknown send states cannot be detected;
- a contractual or legal obligation needs qualified interpretation;
- nobody owns reply review and safe-stop decisions.
Do not use an unofficial WhatsApp API, automate a consumer interface to bypass controls, hide automation deceptively or delete suppression records just to make a contact appear eligible again.
When approved incoming requests need to become internal work before the commercial flow begins, use the message-to-task intake contract to keep provenance, uncertainty and duplicate handling explicit.
If proposals and follow-ups depend on competing spreadsheets or a CRM migration, first define the canonical customer record with the spreadsheet-or-CRM decision packet.
FAQ
How many follow-ups should I automate?
There is no universal number. Define each message’s purpose, applicable permission, stop conditions and owner. A short, relevant sequence that stops correctly is safer than an arbitrary volume target.
Can I send automatically because the person requested a proposal?
The request supplies important context, but it is not a worldwide legal exemption or unlimited permission. Check the actual message, relationship, channel policy, jurisdiction and current opt-out state.
Does an email open mean I can send the next message?
No. An open is not consent or reliable evidence of commercial intent. Use observable replies and current opportunity state.
What if the provider times out after I submit the message?
Set the state to send_state_unknown. Do not retry until you reconcile with the provider or another source of truth. Otherwise, you may create a duplicate.
Can AI approve the proposal it drafted?
No. Drafting and consequential approval should remain separate. A named authorized actor approves the exact payload, and an independent execution check enforces that decision.
Sources and editorial method
Primary sources consulted on 28 September 2026 include the WhatsApp Business Messaging Policy, ANPD legitimate-interest guide, ICO electronic-mail guidance, FTC CAN-SPAM materials, NIST AI RMF Core, OWASP AI Agent Security Cheat Sheet and Microsoft’s approval documentation.
Commercial search results were used only to map competing formats and language, not as proof that automation improves sales. AI materially supported research, structure and drafting. This version received independent validation and was integrated locally. Connecting channels, processing real data, executing external actions, deploying and publishing remain separate gates that require explicit authorization.