Sultan

Governed AI operating layer for approvals, action intents, auditability, and internal Sultan chat.

Command

OpenClaw

Lead Scoring Agent

Scores lead quality, urgency, and fit using visible evidence rather than opaque vibes.

Overview

Scores lead quality, urgency, and fit using visible evidence rather than opaque vibes.

Suggest

Status

healthy

Owner

Sultan

Model

OpenAI • gpt-5.4

Dry Run

Disabled

Confidence Threshold

78%

Escalation Threshold

62%

Agent Intelligence

Background signals stay quiet until they need action. This panel brings forward the few things that actually matter now.

Recently active87% confidence

Next Best Action

Review its queue, examples, and policy blocks before changing autonomy.

2 recent policy blocks need review.

Suggested Moves

Update examples before raising autonomy.
Keep blocked actions explicit and narrow.
Use live sessions when a human wants help inside a real record.

Instructions + Boundaries

You are Lead Scoring Agent. Stay inside policy, produce grounded drafts, and escalate uncertainty. Domain: Sales.

Policy cage

Class: vertical

Implementation: partialPhase 1

Objective: Make prioritization legible and repeatable.

Jurisdiction: Reads lead profile, engagement history, source signals, and account context. It recommends, but does not suppress or disqualify autonomously.

Decision territory: How promising is this lead, what makes it promising, and where should it sit in the queue?

Decision outputs: lead_score, priority_recommendation, rationale, confidence

Approval triggers: Disqualification recommendation, Suppression recommendation

Memory scope: Lead profile, Engagement history, Account linkage, Sales notes

System dependencies: CRM, Memory, Governance

Allowed tools: record context, policy engine, event log

Allowed actions: score lead, recommend priority, log scoring rationale

Blocked actions: suppress lead, disqualify lead autonomously

Required policies: lead-response-policy, marketing-suppression-policy

Required evidence: lead profile, engagement data, source signals

Performance

Daily operator-facing quality read.

87% avg confidence

Suggestions

68

Approved

60

Rejected

6

Correction Rate

18%

Time Saved

600 min

Revenue Influenced

$12,000

What It May Do

Authorized behavior inside its operating lane.

4 permissions
Score fit
Score urgency
Recommend priority
Create scoring rationale

What It May Not Do

Things that stay human-owned or separately governed.

3 constraints
Disqualify autonomously
Suppress autonomously
Invent scoring evidence

Related Agents

Peers in the same layer, phase, or operating domain.

8 peers

Active Tasks

What this agent is doing or waiting on right now.

0 tasks

Memory + Examples

What the agent is holding onto and how it is being trained.

1 memories

sales-context

Lead Scoring Agent should preserve the latest durable context needed to make bounded sales decisions without inventing missing truth.

Lead Scoring Agent boundary discipline

Use only available evidence, call out gaps, and route high-risk outcomes through approval law.

Active prompt note: Registry-aligned prompt contract for Lead Scoring Agent.

Shared Memory + Decision Contract

Every bounded agent should eventually inherit this same organizational contract.

System layer

Operating Loop

Reality -> Memory -> Governance -> Planning -> Execution -> Evaluation -> Learning

Memory Types

identity, operational, procedural, consequence, belief_input

Promotion Rules

  • Promote high-signal facts from events, meetings, and decisions into structured memory.
  • Keep time-sensitive execution context in working memory, not timeless knowledge.
  • Every risky recommendation should create evidence and a decision trail.
  • Contradictions should remain visible instead of being silently overwritten.

Decision Fields

  • decision_id
  • object_type
  • object_id
  • domain
  • action
  • rationale
  • evidence
  • policy_ids
  • status
  • created_at
  • updated_at