Agents In Use
What’s new todayLast update
11 use cases added today

How a lead enrichment agent exposed a billing gap

Scared_Sentence_2834 describes a custom lead-enrichment agent processing an 11,212-row CSV. Higher-cost research calls consumed prepaid credits, but an unitemised balance left the team unable to explain the charge promptly, leading to a reported $600 refund.

Source published reddit.comAuthor's unnamed custom lead-enrichment agent
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Before enriching [lead CSV], estimate the total cost and identify any higher-priced research steps. Require approval above [budget]. During the run, record row counts, tool calls, timestamps and credit deductions. Produce an itemised usage report that a customer can reconcile to their balance.

Evidence at a glance

Sourced account
Original account
Read the source ↗
Published
Source link checked
Reported result
The author reports that the agent enriched all 11,212 CSV rows, with some invoking a research tool priced at four times the normal rate. Explaining the credit usage required two days of log reconstruction, and the team issued a $600 goodwill refund. They report adding itemised run records and spending alerts.
Human involvement
A customer team member initiated the run. The builders investigated logs, explained usage and authorised the reported refund. The source does not describe per-row human review or an advance spending-approval boundary.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. A customer team member started an enrichment run on an 11,212-row CSV.
  2. The agent enriched each row and invoked a more expensive deep-research tool for some rows.
  3. The service deducted credits but displayed only aggregate usage without run details or timestamps.

Reddit author Scared_Sentence_2834 describes a four-person team building a lead-enrichment agent for sales customers. Customers prepay credits, which the service deducts per row. The post reports an actual large run and a billing failure, rather than a proposed agent product. The agent itself is not named.

A customer added $2,000 in credits and later saw only $100 remaining. When the customer challenged the usage, the team's dashboard showed a single total of 1,900 credits used, without run details or timestamps. The author says reconstructing events from logs took two days.

Their reconstruction found a run against an 11,212-row CSV. The agent enriched every row, and some rows invoked a deep-research tool that cost four times as much. The author says the charges were legitimate, but the customer still requested a $600 goodwill refund. The team reports issuing it rather than face a possible chargeback. This entry cannot independently verify the ledger or the refund.

The author says the team now links each run to the credit balance and emails customers when they consume half a top-up in one day. Who it's for: teams selling usage-priced agent workflows. The observed lesson concerns explaining agent activity and variable tool costs. It does not prove that the enriched leads were accurate or that the billing changes prevented later disputes.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/Scared_Sentence_2834

Frequently asked questions

Which agent platform did the team use?

The source does not name a platform or model. It describes the team's own lead-enrichment agent and a higher-cost deep-research tool, so the entry does not assign an unsupported vendor.

What did the team change after the dispute?

The author says they added per-run records against the credit balance and an email when a customer consumes 50% of a top-up in one day. The post does not report a later test of whether those changes prevented disputes.

More details

Remaining steps

  1. After the customer's complaint, the team reconstructed the run from logs over two days.
  2. The team reports issuing a $600 goodwill refund and adding per-run balance records and consumption alerts.

About this account

The author's custom agent processed the lead CSV and used a higher-cost deep-research tool for part of the run. The post does not identify the underlying model, explain its routing logic or establish lead-data accuracy.

Builder's operational account by u/Scared_Sentence_2834: https://www.reddit.com/r/aiagents/comments/1x6wo1i/we_had_to_refund_600_to_a_customer_even_tho_we/. Full public RSS evidence re-read on 16 October 2026; repaired-policy body gate passed at 0.80. Row counts, credit costs and refund are author-reported, not independently audited. Suggested prompt by Agents In Use, not the author's original prompt. Original title-stage rejection is preserved.

Credit: u/Scared_Sentence_2834 on Reddit

Source published

Added to Agents In Use

Source checked

Tools and topics

custom lead-enrichment agent · deep-research tool · CSV lead list · usage logs · prepaid credit ledger

lead enrichment · usage billing · audit trails · customer disputes

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.