Rebuild prospect meeting outcomes without double-counting reschedules

Setup requirements

1. Define whether the denominator is initial requests, booking instances or attended sessions; do not mix them.

2. No attendance or no-show inference from elapsed time, calendar presence or silence.

3. Before any pilot, confirm an actual unresolved need and approve minimized inputs, processing environment, retention and recipients. This design does not authorize execution.

Inputs and access

1. Name

   booking_history.csv

   Source or owner

   Sales operations

   Scope

   Synthetic booking IDs, original/replacement IDs, contact tokens and creation/change times.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

2. Name

   meeting_outcomes.csv

   Source or owner

   Sales owner

   Scope

   Explicit completed, no-show or cancelled evidence and meeting IDs.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

3. Name

   report_snapshot.json

   Source or owner

   Reporting owner

   Scope

   Existing totals, date window and owner-approved denominator definitions.

   Sensitivity

   Synthetic fixture only; actual commercial, personal or location data requires minimized approved handling.

   Permission needed

   Specific owner approval before any real-data pilot. No live account access, credential handling or upload is authorized.

Human approval boundaries

1. Before a pilot, the accountable owner approves exact synthetic/minimized copies, processing environment, retention and allowed recipients.

2. Owner validates identity mappings, authority, status definitions and all unresolved evidence.

3. Any source mutation, account access, upload, external communication, commercial commitment, payment or changed permission requires separate appropriate authorization.

The problem

Overwritten booking dates can hide the relationship between an original prospect meeting and its replacements.

Suggested task

Build an evidence-linked booking lineage and report outcomes under a supplied denominator policy.

What you could produce

A meeting-chain register and metric bridge with unresolved lineage and unverified attendance kept visible.

Why an agent / simpler alternative

Mixed narrative and structured evidence can benefit from assisted extraction and explanation. Identity joins, interval calculations and totals require deterministic checks. A supported native report, query or spreadsheet is preferable when it answers the owner’s question reliably.

When this work comes up

Role

Sales operations coordinator

Trigger

Booked, rescheduled and attended totals disagree.

Human approval

Owner approves scope, rules and evidence interpretation. Any operational action requires separate appropriate authorization.

Finished output

A meeting-chain register and metric bridge with unresolved lineage and unverified attendance kept visible.

Proposed evaluation scope — no pilot authorized

Scope

At most 50 prospect meeting chains and 200 booking/cancellation/outcome events across one quarter.

Limit origin

Editorial evaluation bound, not a verified platform limit.

Overflow action

Stop and ask for approved partitioning; no silent truncation.

Pilot authorized

No

Evidence boundary

Firsthand reports establish stated friction or concerns only. O*NET provides duty context. Official documents establish limited native features or general primitives. This workflow, safeguards, fixtures and outputs are original proposals, not source-documented executions.

Proposed steps

1. 1

   Freeze reporting window and three separate units: request chain, booking instance and attended session.

   Output: metric_scope.json

   Expected output: metric_scope.json

   Checkpoint: Owner approves the denominator and time-boundary rule.

   Approval gate: Owner approves exact inputs and rule scope before any pilot.

2. 2

   Extract explicit replacement/cancellation links from histories and supplied messages.

   Output: booking_links.csv

   Expected output: booking_links.csv

   Checkpoint: Same contact and date proximity alone do not prove a replacement.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

3. 3

   Build acyclic chains with one original request ID and isolate branches or orphaned replacements.

   Output: meeting_lineage.json

   Expected output: meeting_lineage.json

   Checkpoint: Two unrelated meetings for one prospect remain distinct.

   Approval gate: Owner resolves ambiguous identity, authority or language before affected rows advance.

4. 4

   Attach explicit outcome evidence to the right instance and identify chains with an evidenced attendance.

   Output: chain_outcomes.csv

   Expected output: chain_outcomes.csv

   Checkpoint: Past scheduled meetings with no outcome remain unknown.

   Approval gate: Owner validates the calculation or decision rule before relying on its result.

5. 5

   Calculate request-level and instance-level totals separately and bridge them to the supplied dashboard.

   Output: meeting_metric_bridge.csv

   Expected output: meeting_metric_bridge.csv

   Checkpoint: Rescheduled instances do not create extra initial requests.

   Approval gate: Owner reviews unresolved findings; no operational action is authorized.

6. 6

   Deliver a review packet of denominator definitions, source-linked differences and missing-outcome questions.

   Output: meeting_review.json

   Expected output: meeting_review.json

   Checkpoint: No CRM changes, invitations or prospect messages are sent.

   Approval gate: Owner accepts the separate artifact; all live actions require separate authorization.

Original starter prompt — proposed

Origin

editorial_proposal

Execution authorized

No

Text

Using only {approved_synthetic_inputs} and {owner_rules}, Build an evidence-linked booking lineage and report outcomes under a supplied denominator policy. Follow the six-step design. Preserve exact identities, evidence spans and uncertainty. Use inspectable calculations. Write only separate review artifacts described by the output schema. Stop for missing authority, ambiguous evidence or out-of-scope data. Do not change source records, contact anyone, access live accounts, post transactions or execute recovery actions.

Expected output schema — proposed

Primary key

1. request_chain_id

2. booking_instance_id

Columns

1. replaces_id

2. contact_token

3. scheduled_time

4. event_state

5. explicit_outcome

6. outcome_evidence

7. report_window

8. metric_inclusion

9. source_spans

10. owner_decision

Record status

draft_review_only

Common provenance columns

1. input_snapshot_id

2. rule_version

3. source_document_id

4. source_row_or_span

5. reviewer_decision

Unknown value policy

Unknown values remain null, not zero. Keep raw identities and evidence. Unresolved rows do not silently enter approved totals.

Synthetic output illustration — not an executed result

Label

Synthetic authored example, not observed output

Synthetic

Yes

Executed

No

Input

Replacement edges

1. 1. M1

   2. M2

2. 1. M2

   2. M3

Attended

1. M3

Expected

Initial requests

1

Booking instances

3

Replacement events

2

Attended chains

1

Limits

1. Original proposed and untested design; no source documents this complete agent workflow.

2. A reported problem is not proof of prevalence, willingness to pay, harm magnitude or current demand.

3. Historical product reports require current-installation checks; a current capability document only establishes general primitives.

4. Native reports or a deterministic script may be simpler. Exports, identity mappings, context size, privacy controls and actual tool compatibility remain untested.

5. Numerical fixtures are synthetic and have not been executed. Owner review is necessary; no time saving, cost saving or revenue outcome is asserted.

Candidate platforms — compatibility untested

1. Name

   ChatGPT Work

   Required capabilities

   1. Assess this plan’s input, operation and output requirements before selecting an account.

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   Selection basis

   Editorial candidate only. Shared source facts are general primitives; this plan remains unexecuted.

   Workflow compatibility

   BotCurrent has not tested this workflow.

Failure modes

1. A replacement has two possible parent bookings.

2. The latest date overwrote earlier history.

3. A completed flag conflicts with cancellation evidence.

Recovery and troubleshooting

1. Signal

   A replacement has two possible parent bookings.

   Recovery

   Keep lineage unresolved and ask for the original cancellation/reschedule reference.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

2. Signal

   The latest date overwrote earlier history.

   Recovery

   Report the loss of observability; do not reconstruct invented dates.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

3. Signal

   A completed flag conflicts with cancellation evidence.

   Recovery

   Hold the outcome pending the owner’s record review.

   Resume condition

   The accountable owner supplies the missing authoritative evidence or explicit rule; otherwise retain the affected result as unresolved.

Unexecuted validation plan

Sample setup

Replacement edges

1. 1. M1

   2. M2

2. 1. M2

   2. M3

Attended

1. M3

Acceptance checks

1. M1 replaced byM2 replaced byM3, with explicit attendance onM3, yields one request, three instances and one attended chain.

2. A separateM4 for the same prospect remains another request absent a replacement link.

3. An elapsedM5 with no outcome is unknown, not no-show.

4. Duplicate event IDs must not inflate either instance or reschedule counts.

5. Every conclusion traces to a source row or an explicitly labelled owner rule; repeated evaluation of identical frozen inputs must preserve identities and totals.

6. All original copies remain unchanged. Output is a draft review artifact, not an operational decision.

Stop conditions

1. Required identity, source coverage, calculation policy or owner authority is missing.

2. Unexpected real sensitive data is supplied without approved handling.

3. Requested work would require live access, upload, external communication, accounting posting, payment, permission change or irreversible action.

Executed

No

Fixture status

Designed specification only. No acceptance fixture or business workflow executed.

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Plan access, model usage, tool runtime and storage costs unknown.

2. Export preparation, evidence cleanup, review and correction effort unmeasured.

3. No native integration, paid service, new account or software installation assumed.

4. Case-specific effort is unknown: source extraction, identity repair, owner-rule preparation, fixture design and review may dominate model cost.

Caveat

No measured time saving, current demand, ROI or price claim. Compare the simpler remedy first.

Canadian adaptation — proposed

Verify local privacy and organizational record-handling requirements before any real-data pilot; preserve original currency, business calendars and time zones. No Canadian deployment or compliance claim.