Awarded ITAD Identity Reveal & CRM Clone

During the bid round, the customer sees offers — price, services, certifications, trust score — but not the bidder’s identity. The masking keeps the round honest: a customer who recognises a familiar name shouldn’t favour them on the basis of recognition alone, and a bidder shouldn’t be able to game the round by exploiting a known relationship. At award, the mask comes off.

What the customer sees during the round

Each bid surfaces with: bid amount, services included, certifications held (verified), trust-score tier (platinum / gold / silver / bronze), SLA committed, optional notes. The bidder is shown as “ITAD #N” where N is a stable identifier across the customer’s session — so the customer can compare and discuss internally without ever needing the company name to track which bid is which.

What the customer sees at award

The moment the customer awards the bid, the awarded bidder’s identity reveals in the customer’s portal: company name, primary contact, certifications with verification dates, the awarded ITAD’s coverage area, recent pickup history (anonymised across the platform’s aggregate). The other bidders’ identities stay masked — the customer who awarded one ITAD doesn’t need the other bidders’ names.

What happens on the ITAD’s side

The awarded ITAD receives a notification with the customer’s identity, the request, and the structured contract that just generated. A one-click “clone to CRM” action surfaces on the same notification: pressing it creates the customer as a Company in the ITAD’s Core CRM with the contact, the address, the request as an Inbound Order skeleton, and a link back to the trade-in record. The relationship starts in the right database; the ITAD doesn’t have to retype 200 fields.

Why a clone, not a join

Trade-in customer accounts and Core companies live in different scopes. The trade-in customer is a marketplace identity (they could have multiple ITADs working for them over time); the Core company is one ITAD’s view of one client. Cloning means each ITAD’s CRM has the customer as their own row, with their own contract and contact data, without any cross-tenant data leakage.

Audit trail of the reveal

Every reveal event writes to the audit log: who awarded, who received the reveal, when, and what data was unmasked. Useful when a customer or a bidder later asks “when did this become known to whom” — the answer is a row, not a guess.