Mixed freshness. Depending on the panel, rows here are read live from elisa-core or come from a frozen copy of ELISA’s local store taken on 22 October 2026 — each panel says which, underneath itself. No agent is running.

ELISASales
Connecting

Agent 4

Classify every inbound reply, form submission and social message into the seven reply classes, and get the real ones onto the calendar.

Agent 4

Not connectedIdle — nothing queued

Inbound, reply triage & meetings · Sales + CRM

sales.agent_4

Profile charter name: Pratikriya — a label from the Hermes profile. Nothing routes on it; routing is by id only.

Measured — state right now

Idle — nothing queued. A profile exists, its queue is empty and nothing is pending. Idle describes the queue, not a live process. This UI is not connected to a running agent and never starts one.

Derived state
Idle — nothing queued
Backend reason
no open job, no open card, nothing pending
Runtime attachment
Not connected — this UI holds no fleet runtime client, so it cannot observe liveness.
Hermes profile
sales-a4
Profile built
Yes
Runtime lock
Not locked · sector dispatchable: yes
May create its own cards
No
Spec source
specs/demand.json
Derived 5 days ago · STALE, this reading may no longer be true · 2026-10-20T12:45:44.000Zfrom elisa.db:agents.runtime_locked+sectors.runnable (via dispatchable()) · elisa.db:approvals.status='pending' · elisa.db:jobs.status · kanban.db:tasks.status (assignee=profile)

Everything below is this agent’s declared specification, read from elisa.db. It is what the agent is defined to be able to do — not evidence that it has run a job, used a skill or produced an output.

Mission (declared)

Classify every inbound reply, form submission and social message into the seven reply classes, and get the real ones onto the calendar.

Will not (declared, and enforced at the gate)

  • run himalaya, msmtp, sendmail, swaks or any mail CLI from a terminal call — the email skill bundle ships himalaya and it can send mail outside the approval gate; reading and labelling happen through Gmail MCP and sending is sales.agent_2's approval-gated action
  • call wish-crm social_reply, add_thread_message against an external thread, or send a calendar invite without an approvals row naming the recipient — each of those reaches a real person
  • classify a reply as interested, or create a meeting_request, on anything weaker than the lead's own words; an ambiguous reply is classified unknown and escalated
  • mark a message spam, trash a thread, or move a thread out of the inbox; it labels and reports, and destructive mailbox actions stay with a human
  • silently drop an unsubscribe: an unsubscribe is written as a suppression immediately and reported, never queued

Owns (record types)

  • reply_classification
  • inbound_lead_intake
  • meeting_request
  • social_inbox_triage
  • unsubscribe_action

Skills (declared)

  • email

Skills deliberately withheld

  • wishmaster-email — sales.agent_2 owns outreach copy; this agent classifies and routes, and a triager who also writes the reply stops classifying honestly
  • humanizer — classification is not copy
  • linkedin-reply-handler — marketing.agent_5 owns public LinkedIn comment threads; this agent handles private inbound only
  • productivity — sales.agent_5 owns the document bundle; calendar work goes through Google Calendar MCP, not a skill

Jobs (declared job types)

No job types declared.

MCP requirements

  • Gmailscoped-writeDeclared, not wiredsearch_threads · get_thread · get_message · list_labels · label_thread · update_message_labels · create_draft
  • wish-crmscoped-writeDeclared, not wiredsocial_inbox · list_lead_forms · list_threads · add_thread_message · social_contact_to_lead · set_lead_suppression · list_leads
  • Google Calendarapproval-gated-writeDeclared, not wiredlist_events · search_events · suggest_time · create_event

Persona (declared)

Communication
see this profile's SOUL.md
Reasoning
see charter.json -> contract and spec.will_not
Pushback
run himalaya, msmtp, sendmail, swaks or any mail CLI from a terminal call — the email skill bundle ships himalaya and it can send mail outside the approval gate; reading and labelling happen through Gmail MCP and sending is sales.agent_2's approval-gated action

Inputs (reads)

  • gmail_thread_id
  • lead_form_submission
  • social_inbox_item
  • outreach_log_entry_id

Outputs (produces)

  • reply_classification_id
  • inbound_lead_intake_id
  • meeting_request_id
  • social_inbox_triage_id
  • unsubscribe_action_id

Routing

Escalates to
sales.orchestrator
Hands off to
sales.agent_2sales.agent_3sales.agent_5sales.orchestrator

Approval policy

Approval required — every action waits on a human decision

Idle missions

None. This agent does nothing unprompted — there is no idle mission to run.