Customer work and campaign objectives
Marketing develops and communicates offerings that provide value, using customer research to inform decisions. Sales helps prospective customers assess and complete purchases. A campaign coordinates activity around a defined audience and objective. A conversion is a specified desired action, such as requesting a consultation; it need not be a purchase. The American Marketing Association’s definition places customer value beyond promotional output.
An individual may choose and buy an offering personally. An organizational purchase can involve finance assessing affordability, operations assessing suitability, and other participants approving adoption. This buying group shares a purchase decision without sharing identical needs. Account-based selling coordinates attention across those participants; the Salesforce introduction illustrates that distinction.
A customer journey describes experiences across discovery, assessment, purchase, and use. A marketing funnel summarizes progression toward selected actions; a sales pipeline organizes potential deals by working stage. Retention means customers continue the relationship or use. These are organizing views: a customer can revisit research, defer a decision, or involve another participant rather than advance through one fixed sequence.
| Work | Customer and team responsibilities | Useful AI contribution |
|---|---|---|
| Research | Customers describe circumstances; marketing investigates needs. | Prepare source-backed summaries for human interpretation. |
| Communication and response | Teams make accurate offers; customers respond or decline. | Draft follow-ups and surface replies for accountable action. |
| Qualification | Sales assesses whether further discussion is useful. | Organize evidence and meeting preparation. |
| Purchase and continued use | Customers decide; teams verify completion and subsequent usefulness. | Support the work without treating a recorded stage as the outcome. |
A sales development representative, or SDR, sources prospects, contacts them, and arranges meetings. Positive replies and booked meetings are closer to this role’s purpose than email volume, but they remain intermediate outcomes. Define the workflow boundary around the intended improvement, including human follow-up when completion depends on it.
Customer records, identity, and lifecycle state
Customer relationship management software, or CRM, organizes customer information and interactions. A contact represents a person; an account represents a managed organization or customer relationship; a lead represents an unqualified prospect; an opportunity represents potential business. Implementations differ, including whether leads are separate records. Salesforce’s object introduction provides one concrete model.
Identity, stage, ownership, and evidence are separate. Duplicate person records can split interaction history or generate duplicate assignments. Several legitimate contacts can participate in one deal. A stale stage can misrepresent current work. A system of record is the designated authority for a particular fact; the CRM need not govern payment or continued use. Establish field meanings and authority before accepting generated updates.
People and a potential deal
ExampleTwo contacts can share one opportunity.
Read the diagram as text
- Contact A.
- Contact B.
- Account.
- Opportunity.
- Recorded interaction.
- Contact A → Account: associated with.
- Contact B → Account: associated with.
- Account → Opportunity: has potential business.
- Recorded interaction → Contact A: involves.
| Proposed change | Required evidence and authority | Completion evidence |
|---|---|---|
| Save a meeting summary | An operator checks the source conversation and mapped fields. | The intended record contains the reviewed values. |
| Advance qualification | An authorized owner applies the organization’s stage criteria. | The recorded change and its supporting reason remain inspectable. |
| Record a purchase outcome | Use the designated business evidence, not a generated stage recommendation. | Reconcile the outcome with its authoritative record; valid JSON alone is insufficient. |
Audience selection and account evidence
An audience segment groups records using explicit criteria. An ideal customer profile, or ICP, describes customers whose circumstances and needs fit the offering. Account-based marketing coordinates activity around selected organizations and their buying groups. Selection should expose its conditions: AND requires all listed conditions; OR permits alternatives. Documented segment filters make that logic inspectable.
First-party data comes from the organization’s direct interactions. Enrichment adds information from another source. Intent signals are observations interpreted as possible interest, not direct access to a person’s intentions. Keep customer statements, observed behavior, external facts, and inferred interests distinguishable. Their origin, age, uncertainty, and permitted use belong with the selection decision; collection and identity explain the broader discipline.
| Criterion | Entity and source | Age and uncertainty | Permitted use | Decision |
|---|---|---|---|---|
| Target industry | Account; company description | Observed this month; business mix may vary | Account research | Pass this condition only |
| Demonstrated need | Contact; direct response | Dated response; purchasing scope unclear | Follow-up assessment | Investigate scope |
| Recent engagement | Contact; recorded event | Recent; event may not indicate buying readiness | Prioritization under campaign policy | Rank separately from fit |
Fit scores summarize properties; engagement scores summarize events. Neither is automatically a purchase probability. A former champion changing employers can justify researching the new account, but does not establish current authority or demand. Revise ICP criteria using wins, losses, and deferred decisions; updating a knowledge base is not necessarily retraining model parameters.
Purpose, consent, and contact eligibility
A lawful basis is an applicable legal ground for processing personal information. Consent is a specific, informed affirmative permission under the relevant requirements; it is not the only possible lawful basis. Purpose limitation constrains why information may be used. Processing authority, contact rules, recipient preferences, and provider restrictions require separate decisions. Privacy decision authority develops these distinctions.
Under UK PECR guidance, unsolicited electronic marketing to individual subscribers generally needs consent or a qualifying soft opt-in, a conditional exception. Corporate subscribers have different rules; sole traders can be individual subscribers. Public details or a purchased list do not establish consent where required. Suppression means retaining contact details to prevent further unwanted marketing, not treating them as a reusable audience.
A stale audience survives an opt-out
ExampleCurrent restrictions govern dispatch.
Eligibility supports export and queueing.
Read the diagram as text
- Contact.
- Audience export.
- Queued message.
- Earlier eligibility snapshot.
- New opt-out recorded.
- Dispatch blocked.
- Contact → Earlier eligibility snapshot: historical state.
- Earlier eligibility snapshot → Audience export: inclusion basis.
- Audience export → Queued message: selected recipient.
- Contact → New opt-out recorded: current restriction.
- New opt-out recorded → Dispatch blocked: prohibits contact.
- Queued message → Dispatch blocked: dispatch recheck.
- Selected. Eligibility supports export and queueing. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message. New: Contact, Earlier eligibility snapshot, Audience export, Queued message.
- Preference changed. The export remains historical. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message, New opt-out recorded. New: New opt-out recorded.
- Dispatch withheld. The local dispatch gate applies the current restriction. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message, New opt-out recorded, Dispatch blocked. New: Dispatch blocked.
US CAN-SPAM guidance requires accurate sender information and subject lines, advertising identification, a postal address, and an opt-out method for commercial email. Opt-outs must be honored within ten business days; that deadline is not a recommended automation delay. Outsourcing sending does not remove responsibility. Message purpose matters even for existing customers. These rules do not establish permission for calls, texts, or every jurisdiction.
In the campaign contract illustrated below, dispatch checks current eligibility even when an older export included the recipient. Record which exports and provider queues need action, and whether those actions are confirmed. A requested cancellation is not evidence that an already accepted provider message was stopped. Authorization must account for changed permissions at the consequential operation.
Withdrawal stops reliance on the withdrawn permission. An unsubscribe can concern one channel; an objection can have broader scope. Correction changes inaccurate information; erasure removes information where applicable. Suppression serves prevention. Determine its necessary contents and permitted retention separately rather than inventing a universal period. Lifecycle fulfillment tracks these different obligations across copies.
Research that preserves evidence and uncertainty
Retrieval-backed research supplies relevant source material to an assistant preparing an answer. It can reduce manual offer selection while preserving access to supporting passages. A visible source is useful only if it supports the associated claim and its conditions. Claim-level grounding explains that boundary; retrieval does not itself verify the generated conclusion.
| Record | Supported statement | Boundary and next use |
|---|---|---|
| Public announcement, June 5 | The company announced a new site. | Account fact; does not establish this contact’s project. |
| Restricted meeting note, June 12 | The contact reported manual scheduling work. | Attributed customer statement; retain the internal audience restriction. |
| Product documentation, version 2 | The specified plan includes scheduling export. | Product fact; do not extend it to every plan. |
| Analyst interpretation | The export feature may address part of the reported work. | Hypothesis; confirm workflow fit and budget with the customer. |
An unsupported budget inference should become an unresolved field and a seller follow-up task, not a claim that funding exists. Preserve disagreements between sources and distinguish their dates. Product comparisons need matching versions and conditions. Meeting preparation needs attributed statements, not reconstructed customer intentions. These distinctions let an incomplete brief remain useful without pretending it is complete.
Voice-of-the-customer analysis synthesizes actual customer feedback into recurring needs or problems. Structured call summaries can support that work after review. Generated personas and simulated reactions instead supply hypotheses: they are not observed testimony. Their usefulness requires comparison with real customer evidence, following the distinction developed in Synthetic Data.
Campaign content and revision-specific review
A creative brief specifies audience, customer problem, offer, channel, desired action, and supported claims. For a scheduling product, it might request an email inviting operations teams to an assessment, using only documented capabilities. AI can draft variants or a meeting follow-up. Sales enablement means preparing material that helps sellers explain the offering and conduct those conversations.
Brand voice is the organization’s chosen communication style. Tone adapts that style to the situation and reader. Mailchimp’s guide distinguishes the two and prioritizes clarity over forced humor. A reassuring style cannot establish availability, correct pricing, or authority to promise an outcome. Localization adapts material for a language and market; review must preserve meaning and applicable offer conditions.
Review the artifact being released
ExampleA changed promise needs a new decision.
Read the diagram as text
- Brief and supported facts.
- Draft A.
- Check claims.
- Commercial and brand review.
- Approve A for specified use.
- Withhold for revision.
- Changed draft B: re-review.
- Brief and supported facts → Draft A: data: drafting basis.
- Draft A → Check claims: data: actual content.
- Check claims → Commercial and brand review: control: checks pass.
- Check claims → Withhold for revision: control: unsupported claim.
- Commercial and brand review → Approve A for specified use: control: authorized approval.
- Commercial and brand review → Withhold for revision: control: changes required.
- Approve A for specified use → Changed draft B: re-review: control: offer subsequently edited.
Claims substantiation means having evidence for consequential assertions. The FTC’s US policy requires a reasonable basis for objective advertising claims before dissemination; implied evidence standards also matter. A fluent generated claim supplies no such basis. Review product promises, comparative assertions, pricing qualifications, endorsements, and audience suitability against their applicable evidence and requirements.
Post-generation checks can reject unsupported dates or figures and flag ambiguous claims for review. Isadora Martin-Dye’s example describes an assistant offering an unavailable date without calendar evidence. Style instructions had not supplied the missing fact. Exact allowed-value checks help only for the facts they cover; examples of good wording do not guarantee correct future output.
Adobe documents review comments, requested changes, and version comparison. A useful local policy additionally binds release approval to the exact revision, audience, and intended use. Changing an offer requires renewed review under that policy; general brand approval cannot authorize the changed promise. Asset rights require their own check, as explained in media release responsibility.
Qualification and accountable sales handoffs
Qualification assesses whether and how a prospect should proceed. Lead routing assigns the resulting work to a responsible recipient. A marketing-qualified lead, or MQL, meets marketing’s criteria for sales attention; a sales-qualified lead, or SQL, meets sales’ criteria for potential business. These are organization-defined classifications, not universal facts or substitutes for supporting evidence.
BANT organizes assessment around budget, authority, need, and timeline. It is a conversation aid, not a universal gate. A buying group may lack one decision maker or a settled purchasing date. Unknown budget differs from an explicit statement that no budget is available; forcing both into a negative value loses useful information.
Routing is not acceptance
ExampleSilence leaves an owner responsible.
Read the diagram as text
- Assess qualification evidence.
- Originator obtains missing facts.
- Record unsuitable or deferred.
- Request seller acceptance.
- Seller owns continuation.
- Originator retains responsibility.
- Assess qualification evidence → Originator obtains missing facts: required facts unknown.
- Assess qualification evidence → Record unsuitable or deferred: evidence supports deferral or rejection.
- Assess qualification evidence → Request seller acceptance: ready under local criteria.
- Request seller acceptance → Seller owns continuation: capable recipient accepts.
- Request seller acceptance → Originator retains responsibility: rejected or deadline expires.
| Dimension | Available evidence | Disposition |
|---|---|---|
| Fit | Account matches explicit industry criteria. | Suitable for further assessment, not proven demand. |
| Need and readiness | Problem stated; budget and timing absent. | Preserve unknowns and obtain missing information. |
| Contact eligibility | Relevant restriction or preference applies. | Apply independently of commercial attractiveness. |
| Next owner | A seller has been proposed but has not accepted. | Keep the originating owner responsible. |
Historical outcomes can reflect earlier attention: if only contacted prospects receive follow-up, untouched prospects have less observed evidence. Missing outcomes cannot establish poor fit. Microsoft’s qualification-agent documentation describes research, matching, email-quality, and groundedness evaluations. Those tests assess components of qualification; they do not establish incremental revenue or successful acceptance by receiving sellers.
Specify an operating agreement for the handoff: evidence, unresolved fields, current owner, proposed recipient, response deadline, and rejection reasons. Under the agreement illustrated below, silence leaves responsibility with the originator. Acceptance requires a recipient able and authorized to act. Accepted handoffs explain why a notification alone does not transfer an obligation.
Outreach, replies, and stopping conditions
An outreach sequence schedules contacts and waiting periods; cadence describes their timing and pattern. Its lifecycle includes selection, drafting, approval, a current eligibility check, sending, delivery feedback, and response handling. Separate authority to draft, send, publish publicly, and make commercial commitments. Permission for one operation does not authorize the others.
A frequency cap limits contacts over a defined interval. A proposed account policy should count automated campaigns and human outreach together where they share a relationship. Otherwise, independently reasonable sequences can produce excessive contact. A substantive reply can pause the account’s automation while an owner handles the request; stopping the sequence does not complete that customer obligation.
The next action depends on state
ExampleWaiting, stopping, and reconciliation differ.
Read the diagram as text
- Check current eligibility.
- Stop further marketing; retain recovery. The responsible owner still reconciles uncertain prior sends and handles outstanding customer obligations under their own authorization. Neither task permits another prohibited marketing send; an opt-out does not resolve a prior timeout.
- Check remaining state.
- Reconcile send.
- Pause; owner resolves.
- Wait.
- Permit scheduled step.
- Sequence finished.
- Check current eligibility → Stop further marketing; retain recovery: prohibited.
- Check current eligibility → Pause; owner resolves: unknown.
- Check current eligibility → Check remaining state: eligible.
- Check remaining state → Reconcile send: send outcome unknown.
- Check remaining state → Pause; owner resolves: otherwise: reply or human obligation.
- Check remaining state → Sequence finished: otherwise: no steps remain.
- Check remaining state → Wait: otherwise: timing or cap blocks.
- Check remaining state → Permit scheduled step: otherwise: due and within limits.
| Observed response | Operational treatment |
|---|---|
| Interest, substantive question, or objection | Pause the automated sequence and retain an owner for a relevant response; an objection is not automatically an opt-out. |
| Automated or ambiguous response | Do not count it as positive intent. Apply the configured wait or route uncertainty for review. |
| Opt-out | Stop the relevant marketing and update suppression handling. |
Deliverability concerns whether messages reach their intended destination. A bounce reports a delivery failure; a deferral postpones delivery. Gmail’s guidance links spam complaints to sender reputation and later filtering, including effects from shared sending IPs. Monitor delivery responses and reduce volume when failures or deferrals rise. Provider compliance does not guarantee inbox placement or establish customer interest.
An uncertain send needs reconciliation, not blind repetition. A timeout can occur after a provider accepted the operation. Repeated requests avoid duplicate effects only when the receiving service enforces an appropriate idempotency contract. Confirmed effects and business recovery cover this boundary. Stopping upcoming steps cannot recall messages already sent.
Conversions and downstream quality
A cohort is a group defined by a shared entry condition or period. A sales cycle is the interval from a specified starting event to the purchase decision. Leading indicators arrive earlier, such as replies; lagging indicators arrive later, such as purchases or retention. Guardrail metrics track harms or unacceptable deterioration rather than quantities to maximize.
Evaluation compares observations with stated criteria. Separate task quality, such as supported claims; workflow performance, such as review effort; customer outcomes, such as a useful held meeting; and business outcomes, such as purchases. Define each event, counting unit, eligible denominator, and observation window before calculating rates. Metrics and proxy failures explains why those boundaries change the meaning of a result.
| Observation | Authority and unit | Denominator and window | Interpretation |
|---|---|---|---|
| Prepared and sent messages | Reviewed artifacts and confirmed send records | Assigned tasks during the campaign | Activity and execution, not customer benefit |
| Positive response | Reviewed reply; unique contact | Contacts reached, within a declared response period | Early progress, distinct from a meeting |
| Booked versus held meeting | Booking versus confirmed attendance; unique meeting | Eligible accounts, within the same follow-up period | Cancellation or nonattendance prevents a booking from counting as held |
| Accepted opportunity | Receiving seller’s decision; unique deal | Submitted handoffs by the response deadline | Report accepted, rejected, and unanswered separately |
| Purchase and retention | Designated purchase and continued-use records; customer or account | Entry cohort with sufficient follow-up | Specify purchase and retention horizons; unfinished observation remains unfinished |
In a constructed ledger, two contacts belong to one account and attend one meeting. The record contains two participating people, one held meeting, and one account with a held meeting. If ten eligible accounts received complete follow-up, the account-level held-meeting conversion is one divided by ten, or 10%. Dividing by contacts answers a different question.
Opens and clicks can arise from security scanners, privacy-related processing, or link previews before a person acts. Filtering changes can move reported engagement without changing behavior. Mailchimp’s bot-activity documentation illustrates these mechanisms and their imperfect detection. Compare engagement with confirmed outcomes, bounces, complaints, opt-outs, and sales rejection rather than treating a click as buying intent.
Suppose an account has not purchased at an interim cutoff but purchases before the declared observation window ends. Its earlier record was immature, not a confirmed final failure. After a complete window, no observed purchase means no observed purchase within that window—not nonconversion forever. Missing tracking is a separate problem from a known absence of the event.
Attribution rules and their limits
A touchpoint is a recorded interaction. Attribution assigns conversion credit to touchpoints under a rule; an attribution window limits which interactions qualify. First-touch assigns credit to the earliest eligible interaction, last-touch to the latest, and linear multi-touch divides it equally. HubSpot’s documentation describes these alternatives. The diagram fixes one journey while the table changes only the rule.
| Rule | Ad interaction | Product email | Sales call |
|---|---|---|---|
| First-touch | 1 | 0 | 0 |
| Last-touch | 0 | 0 | 1 |
| Linear | 1/3 | 1/3 | 1/3 |
One observed journey
ExampleChanging credit does not change events.
Read the diagram as text
- Ad interaction.
- Product email.
- Sales call.
- One purchase.
- Ad interaction → Product email: next recorded.
- Product email → Sales call: next recorded.
- Sales call → One purchase: next recorded.
Coverage constrains interpretation. Unlogged calls, broken identity links, multiple account contacts, sampled histories, and incompatible windows can produce different reports. Overlapping campaigns may claim the same purchase under separate rules. Reconcile units and coverage before combining totals. A generated narrative cannot recover an interaction that was never observed.
Campaign-associated pipeline is potential business linked to campaign activity. Credited revenue is an allocation under an attribution rule. Neither substitutes for the authoritative purchase or payment record. Nor does either establish incremental revenue: the customer might have purchased anyway. Evidence-cited analysts can make an allocation more inspectable without resolving that counterfactual.
Evidence of incremental improvement
Incrementality is the additional outcome caused by an intervention relative to its counterfactual: what would otherwise have happened. The treatment receives the intervention; the control receives the defined alternative. Conversion lift compares downstream conversions between those conditions. Google’s lift description uses advertising eligibility versus a held-back audience, which tests advertising rather than AI assistance itself.
| Treatment | Control | Effect being investigated |
|---|---|---|
| Campaign exposure | Holdout from that campaign | The campaign’s additional conversions |
| AI-assisted campaign work | Existing campaign work | The effect of the defined AI-assisted process |
Compare the assistance intervention
ExampleBoth groups need comparable outcome evidence.
Read the diagram as text
- Eligible accounts.
- AI-assisted work.
- Existing work.
- Assisted-group outcomes.
- Existing-work outcomes.
- Compare outcomes and harms.
- Eligible accounts → AI-assisted work: random assignment: treatment.
- Eligible accounts → Existing work: random assignment: control.
- AI-assisted work → Assisted-group outcomes: declared follow-up window.
- Existing work → Existing-work outcomes: same follow-up contract.
- Assisted-group outcomes → Compare outcomes and harms: defined account outcomes.
- Existing-work outcomes → Compare outcomes and harms: same definitions.
Random assignment uses chance to allocate eligible units rather than selecting treatment recipients for their apparent likelihood of success. Targeting makes observational comparison difficult: people likely to buy may also be more likely to receive advertising. In randomized advertising studies, extensive observed customer information often failed to reproduce experimental effects. That finding motivates careful comparison; it does not measure AI-assisted selling.
Assign a purchasing account together when participants share the intervention or purchasing process. This cluster assignment keeps a group in one arm; membership alone does not justify it. Contamination occurs when shared sellers or reused drafts expose controls to treatment. Seller or team assignment may help. With shared, constrained follow-up capacity, serving one arm can delay the other; account assignment alone cannot contain that interaction.
Predeclare eligible accounts, outcome definitions, follow-up periods, benefit requirements, and unacceptable harms. Record exposure and missing observations without dropping inconvenient accounts. Report uncertainty rather than promoting a noisy difference into a guarantee. Live evaluation supplies the general method; the sales-specific decision depends on mature purchases, accepted work, and customer consequences.
Observed, modeled, and projected outcomes must remain distinct. Google’s lift documentation describes modeling for missing linkage and, for specified studies, projections of delayed conversions. A projected future purchase is not an observed purchase. Align follow-up windows and wait for the planned study endpoint before interpreting immature totals as the final effect.
Operating value, ownership, and expansion
Revenue operations, often shortened to RevOps, coordinates revenue-related processes and data. Adoption means sustained appropriate use in those processes, not merely access to a tool. Compare the complete work before and after assistance. Time saved in research may be consumed by review, exception handling, or seller follow-up; additional capacity creates value only when it serves useful work.
| Work | Before assistance | After assistance | Evidence to collect |
|---|---|---|---|
| Research and preparation | Read sources and assemble notes | Inspect retrieved evidence and repair omissions | Handling effort and unsupported claims |
| Content review | Review human drafts | Review generated drafts and revisions | Editing effort, rejection reasons, queue age |
| Seller follow-up | Prepare and conduct conversations | Handle routed interest and prepared meetings | Accepted workload and unanswered requests |
| Record maintenance | Enter summaries and correct records | Validate generated fields and repair downstream errors | Correction work and confirmed persistence |
Track labor separately from elapsed waiting, software, model calls, and cleanup costs. Backlog is accumulated unresolved work. João Moura’s account of marketing and qualification assistance describes subsequent demand for customer calls, illustrating a possible shift in work rather than measured labor elimination. Whole-process measurement prevents a faster upstream step from hiding that downstream burden.
| Owner | Decision responsibility |
|---|---|
| Campaign owner | Audience, objective, contact schedule, unresolved handoffs, and pause decisions |
| Sales owner | Accept or reject routed work; handle customer needs and record dispositions |
| Data owner | Identity, field authority, permitted use, and correction propagation |
| Brand and commercial reviewers | Expression, claim support, offer authority, and approval scope |
| Engineering owner | Enforced permissions, execution evidence, recovery, and operating limits |
Expand a bounded workflow when accepted outcomes improve and review, customer harms, and operating costs remain within declared limits. Pause when unsupported promises escape, contact restrictions fail, or unresolved work exceeds responsible capacity. Correct the affected records and process before reassessment. Track bypasses and duplicate checking through adoption evidence; neither saved minutes nor favorable anecdotes establish realized cash savings.
Open questions
Reliable intent assessment remains unresolved when engagement reflects automated events or uncertain identity. Wrong interpretations waste attention and distort personalization. Progress would include independently checked person/account matches and evidence that selected signals predict relevant customer responses across changing conditions.
Preference changes need verifiable fulfillment across exports and provider queues. This matters because a correct central record can coexist with unwanted downstream contact, while provider acceptance complicates cancellation. Progress would include destination-specific completion evidence and explicit unresolved states without retaining unnecessary personal information.
AI-assisted sales experiments need credible treatment boundaries when sellers and follow-up capacity are shared. One account’s treatment can change another’s experience, obscuring the effect being estimated. Progress would include measured exposure and spillovers, mature outcomes, and a design whose comparison remains interpretable under those interactions.
Net operating value remains uncertain when preparation improves but review and customer follow-up expand. Saved effort may become useful capacity, duplicate checking, or an unmanaged backlog. Progress would pair accepted customer outcomes with complete work accounting and evidence that displaced effort actually changes costs or delivered value.















