CRM campaign to sales meeting

The run always starts from sales statistics in business terms and becomes executable only when a verified CRM campaign with campaign_id, campaign reference, campaign-ready leads and CRM evidence exists. The deployment is complete only when every lead is in an evidenced CRM state: confirmed sales meeting, rejection, qualified question or documented blocker.

Agents and roles in the deployment

Three operational agent areas participate in the sales-meeting run: cron, opportunity and crm. Together they call eight subroles that carry the run from sales statistics to sales meeting. cron/runner starts the daily run and secures run evidence. opportunity/triage, opportunity/communications and opportunity/review take over demand classification, process guidance and dispatch review. crm/new-email-verification, crm/email, crm/pending-email-replies and crm/scheduler provide the CRM-adjacent execution services for inbound review, e-mail, response need and scheduling path.

Two control edges additionally secure the run. sentry checks untrusted inbound content before it is returned into the communication run. Company-Agent/review approves outward-facing communication with company knowledge when final text, claims, routing or external effect are affected. Both edges are deliberately not additional business owners: they check, limit and return, but do not guide the sales-meeting run themselves.

Service hierarchy

flowchart TB
  cron_runner[cron/runner]
  triage[opportunity/triage]
  comms[opportunity/communications]
  opportunity_review[opportunity/review]
  company_review[Company-Agent/review]
  crm_verify[crm/new-email-verification]
  sentry[sentry]
  crm_email[crm/email]
  crm_pending[crm/pending-email-replies]
  crm_scheduler[crm/scheduler]
  crm[(Dynamics Dataverse CRM)]
  microsoft365[(Microsoft 365<br/>Mailbox Graph Teams Calendar)]

  cron_runner --> triage
  cron_runner --> crm_verify
  triage --> comms
  comms --> opportunity_review
  comms --> company_review
  comms --> crm_email
  comms --> crm_pending
  comms --> crm_scheduler
  crm_verify --> sentry
  crm_verify --> crm
  triage --> crm
  crm_pending --> crm
  crm_email --> crm
  crm_scheduler --> crm
  crm_verify --> microsoft365
  crm_scheduler --> microsoft365

Systems in the deployment

Two system areas are used in the deployment. Dynamics Dataverse CRM remains the leading evidence location for sales statistics, campaign, leads, e-mail activities, meeting status and CRM timeline. Microsoft 365 carries mailbox, Graph, Teams and calendar for incoming replies, holds and final sales meetings. Technical and business evidence is not shown as separate systems, but guided in the artefact chain.

Artefacts in the deployment

The following view does not show all deployment artefacts, but the most important public evidence. Four points are decisive: which campaign triggers the run, which lead assignment is guided, which communication and inbound response are permissible and which sales outcome finally stands in CRM.

Campaign-Handoff

Owner: opportunity/triage

Meaning: Connects demand from CRM sales statistics with a verified campaign. Contains campaign_id, campaign reference, campaign-ready leads and evidence that the run does not start from an implicit campaign assumption.

Communication Case

Owner: opportunity/communications and cron/runner

Meaning: Keeps run status, campaign, lead, communication history, next step, return and blocker together in one process context. The artefact shows whether the run was started, continued, blocked or terminally completed.

Communication Decision

Owner: opportunity/communications, opportunity/review, Company-Agent/review, crm/email, crm/new-email-verification and sentry

Meaning: Bundles approved send, CRM e-mail activity, permissible inbound response and inbound security decision. Evidences whether a message was allowed to be sent, whether a reply was usable and which next step arises from it.

Sales Outcome

Owner: crm/scheduler and opportunity/communications

Meaning: Bundles meeting need, appointment, meeting_reference, confirmed sales meeting, rejection, qualified question or documented blocker. This artefact closes the lead assignment in business terms and shows the reliable outcome in CRM.

From meeting demand to agreed sales call

The value stream connects technical cadence, demand detection, campaign handoff, communication run, review, CRM e-mail, inbound review, safe response guidance, scheduling and CRM return into a controlled operating process. The standard path starts as soon as outreach or meeting demand emerges from CRM sales statistics and a verified CRM campaign is available as execution basis.

Jadey then guides the run along clear states: take over campaign, load leads, check communication context, approve dispatch, execute outreach, verify inbound, evaluate response situation, trigger follow-up or scheduling path and return the result to CRM. A CRM signal therefore does not become a loose work package, but a controlled revenue process with clear closing logic.

flowchart TB
  subgraph cron_lane["cron/runner<br/>Technical cadence"]
    c1[Start CRM sales run]
    c2[Start opportunity/triage waiting]
    c3[Cadence inbound verification]
    c4[Write run logs and runner report]
    c1 --> c2 --> c4
    c1 --> c3
  end

  subgraph triage_lane["opportunity/triage<br/>Demand and campaign connection"]
    t1[Use CRM sales statistics]
    t2{Outreach or<br/>meeting demand?}
    t_no[Document no run]
    t3[Assign verified<br/>CRM campaign]
    t4[Take over campaign_id<br/>campaign_name]
    t_block[Block campaign connection]
    t1 --> t2
    t2 -->|no| t_no
    t2 -->|yes| t3 --> t4
    t3 -->|not unambiguous| t_block
  end

  subgraph comms_lane["opportunity/communications<br/>Communication run"]
    o1[Start communication run]
    o2[Load campaign leads<br/>and history]
    o3[Determine next step]
    o4[Create dispatch package]
    o5[Request review gate]
    o6{Approved?}
    o_block[Document send blocker]
    o1 --> o2 --> o3 --> o4 --> o5 --> o6
    o6 -->|no| o_block
  end

  subgraph review_lane["Review and governance"]
    r1[opportunity/review<br/>local dispatch gate]
    r2[Company-Agent/review<br/>external communication]
    r1 --> r2
  end

  subgraph crm_lane["crm<br/>E-mail and inbound"]
    m1[crm/email<br/>Email Activity]
    m2[crm/new-email-verification<br/>Check inbound]
    m3{sentry<br/>permitted?}
    m4[crm/pending-email-replies<br/>Response need]
    m_block[Document inbound blocker]
    m1 --> m2 --> m3
    m3 -->|yes| m4
    m3 -->|no| m_block
  end

  subgraph scheduling_lane["crm/scheduler<br/>Scheduling path"]
    s1[Classify response<br/>and next step]
    s2{Closing state?}
    s3[Preflight slot hold]
    s4{Confirmed by both sides?}
    s5[Final sales meeting]
    s6[CRM appointment evidence]
    s_reject[Document rejection]
    s_question[Document qualified question]
    s_block[Document meeting blocker]
    s1 --> s2
    s2 -->|meeting demand| s3 --> s4
    s2 -->|rejection| s_reject
    s2 -->|question| s_question
    s2 -->|blocker| s_block
    s4 -->|yes| s5 --> s6
    s4 -->|no| s_block
  end

  c2 --> t1
  c3 --> m2
  t_no --> c4
  t_block --> c4
  t4 --> o1
  o5 --> r1
  r2 --> o6
  o6 -->|yes| m1
  m4 --> s1
  s2 -->|follow-up| o4
  o_block --> c4
  m_block --> c4
  s_reject --> c4
  s_question --> c4
  s_block --> c4
  s6 --> c4