Why should you care?

CRM revenue impact justifies AgentNest investment; copilot must be fast, grounded, and trustworthy on customer data.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Api/Controllers/CrmCopilotController.cs
[ApiController]
[Route("api/crm/copilot")]
[Authorize(Policy = "AiUser")]
public sealed class CrmCopilotController(ICrmCopilotAgent agent) : ControllerBase
{
    [HttpPost("ask")]
    public async Task<CopilotReply> Ask([FromBody] CopilotAskRequest req, CancellationToken ct)
    {
        var answer = await agent.AskAboutAccountAsync(req.AccountId, req.Question, ct);
        return new CopilotReply(answer.Text, answer.Citations);
    }

    [HttpPost("draft-email")]
    public async Task<EmailDraft> DraftEmail([FromBody] DraftEmailRequest req, CancellationToken ct) =>
        new(await agent.DraftEmailAsync(req.OpportunityId, req.Tone, ct));
}

What happened?

• CrmCopilotController exposes ask and draft-email endpoints returning citations for trust.
• ICrmCopilotAgent wraps kernel, CRM plugins, and RAG.

Practice next

1. build ICrmCopilotAgent with CrmPlugin and playbook RAG.
2. Wire Blazor CRM sidebar to copilot endpoints.
3. Log CopilotReply citations to AiAudit.
4. Add voice input endpoint transcribed via Azure Speech.
5. Personalize tone from rep profile setting.

Remember

CRM Copilot serves ask and draft via dedicated controller. Ground with plugins plus RAG; return citations. Human confirms before outbound customer email.

Rep daily driver

AE uses copilot for account brief, drafts follow-up, logs call notes via NL.

Outcome: CRM activity completeness rises 30%; AiUsageDaily proves daily adoption.