# Clarification behavior in company records | SourceX

Canonical: https://refer.sourcex.si/guides/concept-clarification-behavior
Last updated: 2026-11-04

Clarification behavior is the habit of stopping to ask for missing or conflicting information before acting, instead of guessing. In an ordinary business workflow it shows up when an employee sees two facts that cannot both be true, such as two different discount approvals for the same customer, puts the work on hold, asks the person with authority which one stands, and acts only on the answer. The record of that pause, question, answer and outcome is what makes it useful.

## What does clarification behavior mean in an ordinary business workflow?

It means a person noticed a conflict or a gap and asked before committing the company. The pause itself is the valuable part of the record, because it shows when asking was the right move and what happened as a result.

AI developers care about this because models tend to push ahead. The CLAMBER benchmark, published at ACL 2024, found that current language models have limited practical utility in spotting and clarifying ambiguous requests, and attributed weak clarifying questions partly to a lack of conflict resolution. OpenAI's published Model Spec (version dated 2026-08-18) describes the trade-off from the other side: attempt the task by default, but ask when a wrong guess is costly or the request is too ambiguous. A discount on a signed quote is a costly guess.

Business systems are where these moments get written down. Appen, which sells agent training and evaluation work, markets environments built around the same systems companies already run, such as ERP, CRM and IT service management. A real company's records show the human version: who spotted the conflict, whom they asked, and whether the answer held up. Our explainer on [why AI agents fail](/questions/why-ai-agents-fail) covers what goes wrong when an agent guesses instead.

## Annotated example: two discount approvals for one customer (Illustrative)

A 140-person industrial parts distributor is renewing an annual supply agreement with one customer. Every record below is fictional.

| Step | Record | System | What it shows |
|---|---|---|---|
| 1 | Sales rep requests a renewal discount for the customer | CRM opportunity | The request and its justification |
| 2 | Regional sales manager approves 12% | CRM approval field | First approval, with approver and timestamp |
| 3 | Finance approves 8% as the margin limit for the same renewal | Deal desk email thread | Second approval, conflicting with the first |
| 4 | Quote clerk sees both and puts the quote on hold | Quoting tool status change | The pause: the clerk did not pick one |
| 5 | Clerk asks the sales director which approval stands, citing both | Ticket comment | The clarification question, naming the conflict |
| 6 | Director confirms 10%, with a one-year term, and voids both earlier approvals | Ticket reply plus CRM update | The resolution and who had authority |
| 7 | Quote issued at 10%, signed, invoiced, paid without dispute | Quoting tool, ERP invoice | The outcome that proves the question mattered |

Steps 4 and 5 are the clarification. Steps 1 to 3 are the context that made it necessary, and step 7 is the evidence that the right answer was reached. Without step 7, nobody can tell whether asking helped.

Consider the path not taken. Had the clerk issued the quote at 12% because the sales manager's approval was in the CRM and finance's was only in email, the invoice would have gone out above the margin limit, finance would have caught it, and the company would have issued a credit note or reopened a signed agreement. The disputed version and the clean version start from identical facts. Only the pause separates them, which is why a record of the pause is worth more than a record of the final price alone. The live [deal desk approval guide](/data-types/deal-desk-approval-process) covers this record family in general; this page is about the narrower moment where approvals collide.

## The fields that capture the pause

A clarification is easy to lose in records, because the visible result is just a quote at 10%. These fields keep the whole episode intact.

| Field | Where it sits in the example | Why the example depends on it |
|---|---|---|
| Both approvals, each with approver and timestamp | CRM approval field and deal desk email | Proves the conflict existed before anyone acted |
| Hold status with time and user | Quoting tool, step 4 | Shows work stopped rather than continuing on a guess |
| Hold reason | Free text or code on the quote | Separates a clarification hold from a pricing or credit hold |
| The question, naming both facts | Ticket comment, step 5 | Shows what was asked and of whom |
| The answer and the person giving it | Ticket reply, step 6 | Shows who had authority to resolve the conflict |
| Voided approvals | CRM update, step 6 | Stops the old 12% and 8% from being reused later |
| Shared customer or opportunity key | Present on quote, ticket and invoice | Joins records held in three systems |
| Outcome | Signed quote, invoice, payment without dispute | Shows the question led to a clean result |

If the ticket comment had been a hallway conversation, steps 5 and 6 would leave no trace, and the record would look like a quote that simply sat on hold for a day.

## What the example shows, and what it cannot

One episode illustrates the idea. It does not establish that a company asks well, or often, and a reviewer reads it with those limits in mind.

- **Not every pause is clarification.** A quote can sit on hold because a clerk was on leave. The hold reason and the question are what separate the two.
- **Asking is not always right.** The Model Spec's point cuts both ways: for a trivial, low-cost choice, asking wastes time. A useful archive includes cases where staff reasonably proceeded without asking.
- **The answer can be wrong too.** The director's 10% held up here. Elsewhere a confident answer can lead to a dispute, and only the outcome shows which happened.
- **Real conflicts are hard to invent.** Synthetic versions tend to stage the conflict too neatly, one reason [synthetic data rarely replaces real data](/questions/will-synthetic-data-replace-real-data) for this kind of judgment.

## Who owns these records, and what stays unknown

Sales operations owns the CRM and quoting records, finance owns approvals and invoices, and IT or revenue operations administers the systems. Customer contracts that may limit reuse of deal records sit with legal or the CFO. Authority to discuss licensing rests with the CEO, usually the owner in an owner-run company.

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews the opportunity: whether there is SourceX's current data needs for these records, the outcome of the rights review, what de-identification is needed, the company's offer and any reward. Industry interest in clarification does not mean every approval archive qualifies. Before you introduce anyone, read how to [document client consent for a referral](/resources/how-to-document-client-consent-for-a-referral). For the questions an owner raises first, see [whether a company can license its data to AI companies](/questions/can-a-company-license-its-data-to-ai-companies) and [evidence that AI companies pay for data](/proof/ai-companies-pay-for-data). More record families are listed under [data types](/data-types).

## Go deeper on clarification behavior

- [Questions to ask a client about clarification behavior](/questions/does-clarification-behavior-data-qualify): a short discovery script for checking whether a company's records could qualify.
- [Record gaps that make clarification behavior hard to assess](/questions/clarification-behavior-evidence-gaps): a guide to the missing questions, unlinked threads and absent outcomes that weaken these records.
- [Clarification behavior review packet](/resources/clarification-behavior-review-packet): a list of the metadata a company prepares before SourceX reviews its approval and quote history.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's quote holds, approval threads and outcomes can be linked to one customer case, [register as a partner](/register), confirm the basics on [who qualifies](/who-qualifies), and read the [program terms](/terms) before making the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://model-spec.openai.com/2026-08-18.html
- https://aclanthology.org/2024.acl-long.578/
- https://www.appen.com/agentic-ai
