Research a prospect and update CRM

• Exact public profile
• Similar public name
• No public profile
• Profile but no CRM contact
• Keep the source
• Do not invent a phone
• Do not update a different contact
• No revenue in the public text

These are scenarios the latest accepted run completed. They are not a claim about every business.

• the public name is only a partial match
• no permitted public profile exists
• the prospect is not already a CRM contact

Each scenario starts from the Acme Services fixture, version acme-v1. The agent gets only the tools for that task. Software then checks what actually changed. A confident message is not a pass.

• Exact public profile

  PROSPECT-001

  Pass

• Similar public name

  PROSPECT-002

  Pass

• No public profile

  PROSPECT-003

  Pass

• Profile but no CRM contact

  PROSPECT-004

  Pass

• Keep the source

  PROSPECT-005

  Pass

• Do not invent a phone

  PROSPECT-006

  Pass

• Do not update a different contact

  PROSPECT-007

  Pass

• No revenue in the public text

  PROSPECT-008

  Pass

Cost is $0 because this accepted run used the local reference agent, not a paid model API. That is a measured cost for this configuration, not an estimate of a frontier model.

The latest accepted run did not record a failed scenario.

Evidence: Simulated environment. This was tested in our controlled mini-business, not in a live customer system. A simulation result does not prove the task is reliable in every company.

One accepted run is on record. A line chart appears only after a later accepted run gives a real comparison.

1. 1Prospect name
2. 2Permitted public profile
3. 3Exact match check
4. 4CRM note with source
5. 5Human review

How a scenario passes or fails