[object Object]

A service admin spends Friday afternoon configuring a routing rule, gets it wrong, and only finds out Monday when the Tier-1 queue overflows. The Copilot admin assist in Wave 1 is meant to catch that exact failure mode by reading the configuration intent in natural language and translating it into a tested policy. It is genuinely useful, and it requires a new mental model for admin work.

Admin Assistance

Configuration via natural language — “route high-priority cases from premium customers to senior agents” becomes a policy without code. Error diagnosis AI-assisted. Optimization recommendations surface from usage data. The admin describes intent, Copilot drafts the rule, and the admin reviews before publish.

Admin: "Route premium customer cases over $10k value to senior agents during business hours"
Copilot: drafts a rule with conditions on Account.tier, Case.estimatedvalue, time-of-day, and routes to the Senior team queue
Admin: reviews and clicks Publish

The review step is non-optional. Copilot will sometimes pick the wrong field when two have similar names; the admin catches that in seconds. Skipping the review loses the safety.

Supervisor Help

Real-time queue health analysis. Agent coaching suggestions. Intent trend alerts. Anomaly detection on customer interactions. Supervisors get AI co-pilots for operational decisions. The anomaly detection is the highest-value tile for floor supervisors; it surfaces a sentiment dip on a specific intent in the last 30 minutes before it becomes a queue problem.

<fetch aggregate="true">
  <entity name="msdyn_ocsession">
    <attribute name="msdyn_csat" aggregate="avg" alias="csat" />
    <attribute name="msdyn_intent" groupby="true" alias="intent" />
    <filter>
      <condition attribute="createdon" operator="last-x-minutes" value="30" />
    </filter>
  </entity>
</fetch>

Wire this into the supervisor home page and the anomaly badge appears next to any intent with CSAT below the rolling baseline.

Quality Evaluation

AI grades agent-customer interactions against quality rubrics. Consistent scoring replaces ad-hoc listens. Coaching feedback specific and actionable. Reduces subjective variation in quality programs. The rubric is a YAML-style configuration that the quality team owns; admins do not need to touch it.

rubric:
  greeting: required
  hold_announcement: required_if_hold > 30s
  resolution: required_summary
  empathy: detected_in_response_to_complaint
  closing: required

Calibrate the rubric against a sample of 50 calls scored by humans before letting it grade at scale. Without the calibration, the AI grades against the rubric’s letter and not the team’s actual standards.

Time-to-Value

Most orgs see admin productivity improve 20-40 percent within 90 days. Supervisor effectiveness harder to measure directly but coaching frequency and quality improve measurably. Track admin time-to-publish on routing changes as a leading indicator; it should drop from days to hours within the first month.

The supervisor metrics are slower to move because the workflow change is bigger. Plan for two quarters before the coaching cadence stabilizes around the new tools.

Audit Trail for AI-Generated Config

Every Copilot-drafted rule should land with metadata that says it was Copilot-drafted. Add a custom field on the routing rule entity that captures the original natural language prompt and the draft version. When something breaks in production, the post-mortem can replay the prompt and see what the admin asked for versus what they got.

async function logCopilotDraft(ruleId, prompt, draftVersion) {
  await fetch(`/api/data/v9.2/msdyn_routingrules(${ruleId})`, {
    method: "PATCH",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ ai_prompt: prompt, ai_version: draftVersion })
  });
}

Permissions for Copilot Admin

The Copilot admin features respect the existing System Administrator and System Customizer roles but introduce a new Copilot Author privilege. Grant it deliberately; an admin with this privilege can ship policy changes faster than the change advisory board can review them.

What to do this week

Stand up the rubric, calibrate against a 50-call sample, and add the audit field on routing rules. Pick one admin and one supervisor to pilot for two weeks before opening the features to the full team.

[object Object]
Share