Why should you care?

Reps live in CRM; AI must attach to records they already open, not a separate chat tab nobody uses.

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.Crm/Services/CrmAiFacade.cs
public sealed class CrmAiFacade(ICrmCopilotAgent copilot, ICrmRepository repo)
{
    public async Task<AccountAiPanel> BuildPanelAsync(Guid accountId, CancellationToken ct)
    {
        var account = await repo.GetAccountAsync(accountId, ct);
        var summary = await copilot.SummarizeAccountAsync(accountId, ct);
        var nextSteps = await copilot.SuggestNextStepsAsync(account, ct);
        return new AccountAiPanel(summary, nextSteps);
    }
}

What happened?

• CrmAiFacade combines repository facts with copilot summary and suggestions for the account side panel UI.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Define AccountAiPanel DTO for Blazor or React CRM shell.
2. Expose GET /api/crm/accounts/{id}/ai-panel.
3. Log panel views in AiUsageDaily feature crm.panel.
4. Add one-click accept suggestion writing CRM task.
5. Personalize next steps by rep role from JWT.

Remember

CRM AI embeds in record views via facades and DTOs. Ground on ICrmRepository before generation. Track feature usage per account panel.

Account executive workflow

AE opens Contoso account; side panel shows AI brief and three next steps.

Outcome: Rep accepts two tasks into CRM timeline; AiAudit records grounding chunk IDs.