CRM Settings
The CRM Settings page is where you set up everything the Agent needs to do its job: which mailbox to send from, how many emails a day, which Teams channel to notify, and which template to use. This is admin-only territory — everyone in your project can see the settings, but only Owners and Admins can change them.
Automation toggle
- Enable CRM automation — the master on/off switch. When off, the Agent skips your organization entirely on every 5-minute tick.
- For a temporary halt (holiday, incident, template migration) use the Paused until control on the Agents tab instead — it auto-resumes without needing a re-enable click.
Mail configuration
The CRM sends email via Microsoft Graph, using your organization's own Microsoft 365 tenant. There are two ways to authorize it:
- Shared mailbox — e.g.
sales@yourcompany.com. Recommended when you want replies to land in a shared inbox the whole team can see. Set the address in CRM Shared Mailbox. - User principal — a real user's mailbox (e.g.
alice@yourcompany.com). Replies land in that user's inbox. Set the address in CRM Mail User Principal.
You also need:
- Tenant ID — your Microsoft 365 tenant identifier.
- Mail provider — pick Graph (or None to disable sending while you set things up).
The actual app registration credentials (Client ID + Secret with the Mail.Send application permission) are configured by your administrator at the Azure App Service environment-variable level, not in the UI — this keeps secrets out of the database.
Daily email cap
- Daily email cap — hard upper limit on how many emails the Agent will send per organization, per UTC day.
- The Agent counts sends from the same day and stops when the cap is hit; the rest of that day's eligible leads are deferred to the next tick after midnight UTC.
- Start low (5–10) until you trust the template and the lead quality, then raise.
Teams notification channel
- CRM Notification Channel — the Microsoft Teams channel where the Agent posts its post-send Adaptive Cards. Pick the channel your sales team monitors.
- Leave blank to suppress notifications — the Agent still sends, but silently.
- The post-send card carries the lead summary, the template name, and a one-click Stop automating this lead button (see Agents).
Email templates
- Each org can store multiple templates with a Subject + an HTML body.
- The body supports full HTML — links, formatting, inline styles, tables. Whatever the recipient's inbox renders, you can put in.
- Placeholders look like
{{LeadName}},{{ContactName}},{{CompanyInsight}}— they're flat string replaces, so the HTML around them stays untouched. (Don't put placeholders inside HTML attributes that need escaping, e.g.href="{{Website}}"— safe values are fine, but spec-strict HTML may need a sanitization pass.) - Pick which template the Agent uses by setting it as the org's default. The Agent's Stage 3 send uses that template for every eligible lead.
Tips
- Test the template by manually sending to your own inbox before turning the Agent loose — the first “wait, the link is broken” happens to everyone.
- Use a shared mailbox if you can — outbound from a real human's inbox makes vacations awkward and breaks if that person leaves.
- Keep the daily cap conservative. Cold-outbound deliverability degrades fast above ~50/day from a fresh sending domain; warm up gradually.
- Re-check the Teams notification channel after any internal reorg — if the channel is archived, the post-send card silently fails (the email still sends, but you lose the audit trail in Teams).
Settings are intentionally lean — one mailbox, one cap, one template, one notification channel. The product opinion is that small CRM teams benefit more from one clean automation than from twenty knobs to forget about.