A Better Offer Should Not Require a Customer Dossier

A merchant considering a better price has a narrow question: is this an offer worth making? Yet online commerce often answers it by collecting a broad profile. Forms ask for more fields. Sales teams request more documents. Customers disclose more than the decision needs, before knowing whether the price will change at all.

Agent-led negotiation creates an opportunity to reverse that sequence. Start with an offer. Identify what could materially improve it. Then let the customer decide whether the additional disclosure is worth making. The goal is a commercially useful decision with a smaller information footprint.

Begin with the merchant's decision

Imagine a software merchant willing to invest in customers switching an established team from another provider. The relevant questions might be whether the buyer already uses a competing service, how many seats they need, and which product they intend to purchase. Their unrelated purchases, personal correspondence, and entire work history do little to justify that particular concession.

This example is illustrative, but the discipline is practical: define the commercial reason for a discount before asking for evidence. Give the negotiator a clear customer segment and an authorized discount ceiling. A specific decision creates a natural stopping point for disclosure; a vague instruction to “understand the customer” does not.

Make the first quote useful

In Haggl's protocol, an agent can open with self-reported context, without attaching email evidence. That first exchange matters. It gives the buyer a baseline and lets the merchant explain what might support a different offer. Evidence becomes a possible next step rather than an entrance fee.

Sometimes the initial quote is enough. Sometimes the merchant does not need verification for the segment at all; Haggl supports no-proof segments. A customer who declines further disclosure can evaluate the offer already available or walk away. Neither side benefits from collecting a document that cannot change the decision.

Ask permission for a specific exchange

“May I use your data?” is too broad to guide a useful choice. A better agent explains which evidence it proposes to submit, to whom, and why. For example: “I can submit this subscription receipt to support the switching offer. The verification service will receive the original message. Shall I proceed?”

Haggl's protocol instructs buyer agents to obtain consent before sending personal data. That instruction is an interaction requirement, not an automatic guarantee that every external agent has implemented a good consent screen. Agent builders should make the approval explicit and scoped to the proposed submission. Permission to search an inbox should not silently become permission to send its contents to every merchant.

Authenticate the source; assess the claim separately

Haggl's default engine can check the DKIM signature of an original email. A passing signature is evidence about the signed message and its signing domain. This is stronger than accepting a buyer agent's typed description as if it were independently verified.

It does not settle every question the merchant cares about. Does the message concern this buyer? Is the relationship still current? Does it support the requested product or quantity? A signature is not a prediction of future customer value, and it does not automatically validate a separate excerpt or interpretation supplied by an agent.

Those distinctions belong in the pricing judgment. The engine labels evidence with its verification status; the negotiator weighs it against the merchant's brief. Treating “authenticated source” and “commercially relevant conclusion” as separate questions produces a more defensible offer than calling everything verified.

Know who receives what

Privacy depends on the actual route a submission takes. In Haggl's default engine, the service receives raw email bytes for verification. It removes those raw bytes before passing the submission to the pricing model and replaces raw-message fields with hashes before saving the negotiation round. Evidence annotations can still include sender, subject, date, and a supplied excerpt. Other submitted fields can also remain in the record.

This limits the retained raw-message payload; it does not mean no email content is ever processed or that the merchant receives only a yes-or-no answer. An excerpt can itself contain sensitive information. The useful question is what the negotiation actually requires, not simply whether a field is called a proof.

There is also an important integration boundary: a merchant using a custom pricing webhook receives the submitted customer data through that webhook, which can include raw proofs. Its handling must be assessed separately. An agent should establish the recipients and processing path before presenting the customer with a disclosure choice.

Give the negotiator a stopping rule

A sensible sequence is short: request a quote, identify one relevant uncertainty, ask permission for evidence that could resolve it, then reassess the offer. Stop when further disclosure has no clear commercial purpose. Do not turn a possible discount into an open-ended request for personal history.

Merchants should evaluate the result against their economics: the concession, the customer segment, and the eventual purchase and retention outcomes. Customers should evaluate the proposed price alongside the information requested. Neither a better quote nor a verified source guarantees that the final deal is right for both sides.

The opportunity is still substantial. A merchant can make a considered offer without demanding a complete customer dossier. A buyer can present a stronger case without treating disclosure as unlimited. That is a practical way to build more private, more deliberate negotiation today, while keeping advanced cryptographic privacy separate from what the system currently does.

For the current request format and evidence flow, see the Haggl protocol. Start your merchant setup with a clear customer segment and an authorized offer.