PlaysbyMoat8
Back to the library
The workflow guideMarketing

Use reviewed call signals to evaluate acquisition channels

An education business classified sales conversations against its qualification criteria, added the results to acquisition reports, and sent qualified-lead events to advertising platforms.

6 implementation stepsAdvanced

How this works

An education business classified sales conversations against its qualification criteria, added the results to acquisition reports, and sent qualified-lead events to advertising platforms. Raw lead counts can hide differences in whether enquiries match the offered service. Reviewed qualification signals can improve measurement, provided the rubric is explicit and the reporting keeps uncertainty, missing calls, and attribution gaps visible.

Extract only explicit statements from consented calls, review them against a versioned rubric, and join accepted labels to campaign records using stable identifiers. Build the acquisition report first. Any event export to an advertising platform is a separate authorized action using minimum necessary data and deduplication keys.

Before you start

Consented call material

Use transcripts permitted for this analysis, with a retention policy and a way to review unclear passages.

Qualification rubric

Define observable service-fit criteria, unknown states, exclusions, and reviewer responsibility.

Attribution mapping

Have lead identifiers, campaign records, spend, and downstream outcomes from compatible periods.

Prepare the inputs

call_records
Required

Transcript table

Include call ID, lead ID, date, consent status, and transcript quality.

qualification_rules
Required

Versioned rubric

Use explicit needs and service fit; do not infer protected traits, personality, or creditworthiness.

campaign_records
Required

Attribution export

Record campaign IDs, acquisition dates, mapping method, and unknown attribution.

spend_outcomes
Required

Period table

Align spend, reviewed lead counts, and matured downstream results.

optional_event_authorization
Optional / conditional

Export specification

Define permitted destination, minimum fields, event timing, and deduplication rules.

Implementation, step by step

  1. Freeze the rubric

    • Translate each qualification criterion into observable evidence and unknown outcomes.
    • Define how incomplete calls and contradictory statements will be routed to review.

    Checkpoint: Labels have an explicit meaning independent of a model's confidence.

  2. Extract evidence

    • Locate relevant statements about needs, timing, motivation, and stated budget.
    • Attach transcript spans and distinguish silence from a negative answer.

    Checkpoint: Every proposed label is explainable from permitted evidence.

  3. Review classifications

    • Have a reviewer inspect uncertain cases and a sample of routine labels.
    • Compare accepted labels with later outcomes without rewriting historical rubric versions silently.

    Checkpoint: The report uses reviewed labels with known coverage.

  4. Join acquisition data

    • Match leads to campaigns through stable identifiers and retain unmatched records.
    • Deduplicate repeat calls and define which lead-level qualification event counts.

    Checkpoint: A person with multiple calls does not become multiple acquired leads.

  5. Calculate channel results

    • Compute reviewed qualified-lead volume and cost from compatible cohort totals.
    • Show reviewed coverage, unknown qualification, attribution gaps, and outcome maturity.

    Checkpoint: The comparison does not reward channels merely because more calls were analyzed.

  6. Prepare authorized event delivery

    • Build a minimal event file with stable event IDs and the approved qualification timestamp.
    • Upload only when authorized, retain receipts, and prevent duplicate delivery on retries.

    Checkpoint: Prepared events, accepted events, and reporting results remain separate states.

Decisions along the way

The prospect never states a budget

Label budget unknown; do not infer it from language, identity, or neighborhood.

Several calls belong to one lead

Apply the documented lead-level rule and preserve call evidence without inflating counts.

Platform delivery has an uncertain outcome

Reconcile the receipt or existing event state before retrying.

What you will produce

Acquisition quality report

Table and summary

A cohort-based channel comparison with uncertainty visible.

Include: channel · spend · reviewed_leads · qualified_leads · unknowns · cost · coverage

Reviewed signal ledger

Structured file

A traceable qualification and optional event-delivery record.

Include: lead_id · rubric_version · evidence · label · review_status · event_id · delivery_status

Check the result

  • No emotion or personality inference substitutes for explicit service-fit evidence.
  • Unknowns and missing calls remain in coverage reporting.
  • The cost denominator contains unique reviewed qualified leads.
  • No raw transcript or unnecessary personal data is included in advertising events.

When something goes wrong

Transcription is unreliable

Request human review or mark the call unclassifiable.

Campaign joins are incomplete

Report the unmatched bucket and withhold misleading channel rankings.

The rubric changes

Version the change and compare cohorts only with clearly stated differences.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Compare two channels using reviewed qualification signals.

Inputs

Synthetic example. Channel A spent 1,000 and produced 20 unique reviewed qualified leads from 30 reviewed calls; B spent 800 and produced 10 from 12. Some unreviewed calls remain. Two calls in A belong to the same lead.

Expected result

Synthetic expected result. After deduplication the report uses the confirmed unique lead count, calculates cost per qualified lead, and shows reviewed coverage separately. A prepared event export contains stable IDs and approved fields only; it is not uploaded without authorization.

Run a small pilot

Start small

One consented call batch and two acquisition channels.

Record the baseline

Measure manual label agreement and current attribution completeness.

Agree success criteria

Track reviewed label agreement, unique-lead reconciliation, and reporting coverage before any event use.

Stop or revise

Stop automated event preparation when consent, qualification evidence, or lead mapping is unreliable.

Keep the scope clear

  • Qualification labels are imperfect service-fit assessments, not grounds to deny education, credit, or other consequential access.
  • Analysis authorization does not automatically authorize sharing signals with advertising systems.

Check before using

Validate errors, consent, and fairness before using inferred signals. The scores are imperfect estimates, not objective facts, credit assessments, or grounds to deny access to education.

Business activities

  • Run sales conversations and proposals
  • Run advertising and acquisition tests
  • Review business performance

Editorially adapted workflow; not independently tested.

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: Consented sales-call transcripts · Agreed qualification criteria · Campaign and outcome records

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗