AI agents that email customers and update the CRM
Let sales agents research, draft and log activity, and have a rep confirm anything a customer will see or sign. With NobleCloak, policy decides which CRM and outreach tools an agent may call alone, which wait for a person, and which, like bulk deletes, it can't call at all. Every decision is recorded.
100 scenarios in 5 areas
These are scenarios for how teams govern AI agents in Sales & Revenue. Some depend on capabilities still in development. Products named in a scenario are systems your team runs, named to make the example concrete. The policy applies to the AI agent's calls into them.
Prospecting & Outreach20 examples
Rep confirms every outbound email
An SDR's Claude drafts cold emails in Gmail, but the `send_email` tool is set to ask, so the rep confirms each message in-session before it leaves. Drafting stays fast; nothing is sent on autopilot.
Book meetings freely, ask before cancelling
SDR agents can create Google Calendar events for discovery calls without friction, but deleting or moving a prospect's meeting asks first.
Gift sends capped per prospect
The Sendoso tool sends gifts under $50 without review, holds anything above $50 for in-session approval, refuses anything over a $150 per-call cap, and enforces the monthly gifting budget.
Enrichment credits from approved vendors
The research agent can buy contact-enrichment credits only from ZoomInfo and Apollo, under a monthly budget the sales ops lead sets. Calls to any other data vendor are refused at the gateway.
No direct scraping of LinkedIn
The prospecting agent has no route to the open internet, and the governed proxy blocks LinkedIn profile scraping endpoints. Reps keep their Sales Navigator accounts in good standing.
Interns draft, they don't enroll
The `sales-intern` role can write sequence steps in HubSpot but is denied `enroll_in_sequence`, so a new hire's AI can't push 2,000 contacts into a cadence on day one.
Block sends to suppressed contacts
A send tool call is denied if the recipient appears on the company's do-not-contact or opt-out list, which helps keep AI-written outreach within the company's CAN-SPAM and GDPR commitments.
Credit union bans AI-sent texts
A credit union denies the Twilio SMS tool org-wide for every role, because TCPA exposure on member texting is not worth the risk. AI tools never see the tool.
One AE gets InMail access
The Sales Navigator InMail tool is off for the sales team, but a per-user override enables it for the enterprise AE who runs the strategic-accounts motion.
Research token spend per SDR pod
Tokens and tool calls from account-research agents are metered per user, so the sales director sees which pod is spending $3,000 a month on AI research and what it booked.
Record of who sent what, for licensed agents
An insurance brokerage keeps a ledger record of every email an AI sent for a licensed producer, with inputs and approver, for the state DOI's advertising review.
Opener-writing sub-agent cannot send
The outreach agent spawns a sub-agent to write personalized first lines. The sub-agent does not inherit its parent's send permission, so only the parent, behind its gate, can email.
Daily send cap protects domain reputation
Each rep's AI is limited to 50 outbound emails per day through the Gmail tool, so one enthusiastic agent can't get the sending domain blacklisted.
Unknown partner agents can't pull lead lists
A reseller's agent attempts an A2A call to request the company's target-account list. It isn't on the peer allowlist, so the call is rejected and logged.
Strip personal phone numbers from prospect lists
Before a purchased list is sent to the LLM for scoring, personal mobile numbers and home addresses are scrubbed from the tool response.
Dialer only during calling hours
The Salesloft dialer tool is usable by AI only between 8am and 8pm in the prospect's time zone, keeping auto-dialing inside telemarketing rules.
Check a new BDR's reach before day one
Sales ops uses "inspect as user" on a new BDR to confirm they can draft and research but not export contacts or launch sequences, before granting the role.
EU team never sees the data broker
The US data-broker connector isn't entitled to the EMEA sales role, so it's invisible to their AI clients. Nobody in Dublin can accidentally process US-sourced personal data.
Sales can't target from patient tables
At a health-tech vendor, the sales role is denied queries on the production Snowflake connection that holds clinical data, so AI-built lead lists do not draw on PHI.
Marketing's scoring agent hands off leads
Only marketing's lead-scoring agent is allowlisted to call the sales agent's `create_lead` tool over A2A. No other internal or external agent can push leads into the queue.
CRM & Pipeline Hygiene20 examples
Closed Won needs a human click
Moving an opportunity to Closed Won asks the rep to confirm in-session, so a hallucinated "they signed" never shows up in the bookings report.
Owner reassignments routed to the manager
When an AI proposes reassigning an account owner, the approval goes to the sales manager.
Write freely in sandbox, ask in prod
CRM update tools are allowed on the Salesforce sandbox connection and set to ask on the production connection, so admins can test automation without slowing down.
Ask before slipping a deal out of quarter
A close-date update asks only when the new date moves the opportunity into the next fiscal quarter. Routine date fixes stay frictionless.
No AI bulk deletes in Salesforce
`mass_delete_records` is denied for every role and agent. Cleanup proposals go to a human in RevOps, who runs them by hand.
Only RevOps merges accounts
The `merge_accounts` tool is entitled only to the RevOps role. AEs' AI tools can flag duplicates but never see the merge tool.
Nightly hygiene bot on a tight leash
The autonomous data-hygiene agent may update industry, employee count, and address fields, and is not allowlisted for owner changes, deletes, or stage edits.
Forecast edits leave a trail
Every AI-initiated change to forecast category or amount is in the audit ledger with who, which agent, and the before value, ready for the board's pipeline-quality questions.
Contact exports limited to ops
The `export_report_csv` tool is denied to AE and SDR roles, so a departing rep's assistant can't pull the full contact database.
Read the full exampleSync agent's helpers don't inherit deletes
A HubSpot-to-Salesforce sync agent spawns per-object sub-agents, and none of them inherit its archive permission. Each gets only field-update tools.
Mask account numbers in CRM notes
At a bank, call notes the AI writes into the CRM have deposit account numbers and SSNs redacted before they're saved or read back.
RevOps lead gets mass picklist updates
A per-user override lets the RevOps director run bulk picklist migrations during a field cleanup, without opening the tool to the whole ops team.
Call-summary cost by team
Tokens spent writing Gong call summaries into Salesforce are attributed per team, so CS and sales each carry their own AI bill.
Confirm SEs can't edit amounts
Before rolling out Claude to solutions engineers, the admin inspects an SE's effective policy and verifies the opportunity-amount field tool is denied.
Hourly cap on agent record updates
The enrichment agent is limited to 200 Salesforce updates per hour, so a bad mapping can't overwrite 40,000 records before someone notices.
Activity logging stays wide open
`log_activity` is set to allow for all sales roles with no prompt. Low-risk writes stay frictionless, so reps don't start approving prompts without reading them.
Finance's agent reads pipeline, nothing more
The FP&A forecasting agent is allowlisted over A2A to call only the read-only pipeline summary tool on the sales agent. It can't call update or export tools.
Call recordings can't be deleted by AI
`delete_recording` in Gong is denied for every principal, preserving the conversation record for disputes and coaching.
Reconstruct who touched a policyholder
During a complaint investigation, an insurer pulls the ledger for one policyholder's CRM record and sees every AI read and write, and the user each one ran for.
Time-boxed rights for territory realignment
Account-owner bulk updates are granted to sales ops only for the two-week territory realignment window, then expire automatically.
Quoting, Pricing & Discounts20 examples
Build quotes freely, send with a click
The rep's AI can generate quotes in Salesforce CPQ without friction, but `send_quote` asks first, so no customer gets a draft with the wrong term length.
Discounts over 20% go to deal desk
When a requested discount exceeds 20%, the approval is routed to the deal desk role instead of the rep.
Loan rate exceptions for loan officers only
At a community bank, the rate-exception tool in the loan origination system is visible only to the loan-officer role and asks before each exception is saved.
Read the full exampleTrial extensions need confirmation
Extending a free trial in Chargebee asks the CSM in-session, keeping AI from quietly giving away a quarter of free service.
Two people sign off on multi-year price locks
A three-year price-lock clause requires confirmation from the rep and a second approver in finance before the quote is finalized.
Storefront price changes ask
An e-commerce merchandiser's AI can propose Shopify price updates, but `update_product_price` asks before anything live changes.
Price books are pricing-team only
Price book edit tools are entitled only to the pricing team. Sales AI clients can read list prices but never see a write tool.
No AI-minted Stripe coupons in live
Coupon creation is allowed on the Stripe test-mode connection and denied on the live connection, so a helpful agent can't create a 100%-off code customers can use.
AI cost per quote
Tokens and tool calls behind each CPQ quote are attributed to the rep and team, showing whether AI-built quotes are cheap enough to use on $5k deals.
Evidence for non-standard terms
For rev-rec auditors, the ledger shows who approved each quote with non-standard payment terms, through which agent, and what the inputs were.
Margin floor on quotes
A quote tool call is denied if the computed margin falls below the floor finance has set for that product line.
Underwriting tools for licensed producers
An insurer entitles the premium-rating tool only to the licensed-producer role, so unlicensed service staff never see it in their AI tools.
Competitor pricing research through the proxy
The pricing-research agent can read public competitor pricing pages only through the governed egress proxy, which logs every domain it visits.
Hide internal cost columns from the AI
Cost and margin fields are removed from CPQ tool responses for sales roles, so the AI can't paste them into a customer email.
Partner agents request quotes, not discounts
An allowlisted reseller agent can call `request_quote` over A2A but is not delegated `apply_discount`. Channel pricing stays in channel managers' hands.
Proposal sub-agent has no discount tool
The proposal writer spawns a sub-agent to draft the pricing section. The sub-agent's allow-list excludes `apply_discount`, so it can describe pricing but can't change it.
Preview a new AE's pricing reach
Before onboarding a new AE, sales ops inspects their effective policy and confirms they see list-price lookups only, not discount or price-override tools.
End-of-quarter discount authority, then off
Regional VPs get elevated discount tools for the last five business days of the quarter only, and the grant expires on its own.
FX data purchases capped
The pricing agent buys exchange-rate feeds only from the approved data vendor, with a $500 monthly budget and a per-call cap.
Fair-lending evidence for rate quotes
A credit union exports ledger records of every AI-assisted auto-loan rate quote, showing the inputs and who approved each, for its NCUA exam.
Contracts & Deal Desk20 examples
DocuSign sends need confirmation
The deal desk AI can prepare a DocuSign envelope, but `send_envelope` asks before a customer receives anything to sign.
Flag non-standard indemnity before sending
A send call asks only when the contract body contains indemnity or liability-cap language that differs from the approved template.
MSA deviations go to legal
When an AI-drafted MSA deviates from the playbook, the confirmation is routed to the contracts lead in legal.
Legal AI vendor credits under budget
The deal desk can buy clause-analysis credits only from the approved vendor, with a monthly budget and approval for any single purchase above $1,000.
Booking orders in NetSuite is finance's call
Creating a sales order in NetSuite from a signed contract is limited to the finance role and asks before posting.
Redlining agent reads, never signs
The contract-review agent is allowlisted for Ironclad read and comment tools only. Execute and countersign tools are outside its rung.
Only legal voids envelopes
`void_envelope` is entitled to the legal role alone, so a rep's AI can't cancel a contract mid-signature to "fix" a typo.
No public links on the contracts folder
Creating "anyone with the link" shares in Box or Google Drive is denied for the contracts folder connection, for every role.
SOX evidence for countersignatures
Every AI-assisted countersign of an order form is in the ledger with signer, agent, and approver, so the controller can answer SOX walkthrough questions from the record.
Procurement agents get questionnaire answers, not files
A customer's procurement agent on the peer allowlist may call the security-questionnaire tool over A2A. Calls to the document repository are refused.
Strip bank details from W-9s and forms
Bank routing and tax ID numbers are redacted from vendor forms before the contract agent reads them.
General counsel can delete drafts
Draft-deletion in the contract repository is denied org-wide, with a per-user override for the general counsel who cleans up abandoned matters.
BAAs signed only by the privacy officer
At a health-tech vendor, the tool that executes Business Associate Agreements is visible only to the privacy-officer role.
Who pays for contract analysis
Tokens spent summarizing and redlining contracts are attributed per user, so legal and sales see separate lines on the AI bill.
Contract text stays off random AI sites
The contract agent's egress allows only the approved model providers and the e-sign API, so full contract text can't reach an unvetted summarization site.
Deal desk agent active only at quarter end
The autonomous deal-desk triage agent may call contract tools only during the quarter-close window it was built for.
Signature authority by contract value
Contracts above $250,000 can only be executed when the confirmer holds the CFO role. Below that, the VP of Sales role is enough.
No bulk export of the contract repository
`export_all_contracts` is denied for every principal. Individual retrieval stays allowed, so a compromised session can't empty the archive.
Hand the bank its AI-controls evidence
A bank customer's vendor-management team asks for proof of AI controls. The deal desk exports ledger records of every AI action on that customer's contract.
Two insurers, two tenants
A holding company runs two insurance carriers as separate NobleCloak orgs, so each carrier's contracts, policies, and ledgers stay apart.
Partners, Channels & Renewals20 examples
Renewal notices confirmed before sending
The CSM's AI drafts renewal notices with new pricing, and the send tool asks for confirmation, so a wrong uplift never reaches a customer.
MDF disbursements under a budget
Market development fund payouts through the partner tool are capped per quarter, with approval required above $10,000 per partner.
Uplifts over 7% need approval
A renewal price change asks for approval only when the uplift exceeds 7%. Standard escalators go through without a prompt.
Renewal credit memos routed to finance
When the CSM's AI issues a NetSuite credit memo as a renewal concession, approval goes to the finance role, not the CSM.
No AI-initiated auto-renew cancellations
Turning off auto-renewal in the billing system is denied for every agent. Cancellations go through the retention team by hand.
Reseller agents can register deals
Allowlisted resellers' agents may call `register_deal` over A2A. Agents not on the peer list are refused before they reach the PRM.
Partner tiers are the channel team's call
Tier and margin edits in the PRM are entitled only to the channel-manager role.
Churn-risk agent is read-only
The churn-risk agent is allowlisted for Zendesk ticket reads and a read-only Snowflake connection, and has no write or email tools.
MSP partner manager gets extra reach
A per-user override lets the MSP partner manager provision partner sandbox tenants, a tool the rest of the channel team doesn't have.
Partner-portal agent reaches only the partner API
The portal agent's egress allows only the partner's documented API host, so it can't be steered toward arbitrary URLs.
Commission data is read-only to AI
Adjustment tools in the commissions platform are denied for all agents, so no AI "fixes" a rep's payout.
Renewal forecast changes on the record
Every AI edit to renewal likelihood or ARR at risk is in the ledger, ready for the board's net-retention review.
Chargeback partner-facing AI costs
Tokens and tool calls from the co-selling agent are attributed per partner account, so channel can bill high-usage partners or renegotiate.
CUSO agents can't reach member data
A credit union lets its CUSO's agent call the product-catalog tool over A2A but blocks it from any member-record tool.
Outbound calls only to approved partner agents
The renewal agent can delegate to the distributor's agent for inventory checks, but outbound A2A calls to any non-allowlisted peer are refused.
Scrub end-customer contacts from reseller reports
Usage reports shared with resellers have end-customer names and emails removed before the partner agent sees the response.
Partner SEs never see internal pricing
The partner-SE role isn't entitled to internal price book or discount tools. They're simply not listed in that role's AI clients.
Per-account renewal agents can't email
The renewal playbook agent spawns one sub-agent per account. None inherit the parent's email permission, and every customer touch goes back through the gated parent.
Daily call limits per partner
Each partner's agent is limited to 1,000 A2A calls per day, so one partner's runaway integration can't degrade service for others.
Commission trail for the DOI exam
An insurer that pays independent agencies keeps ledger records of every AI-touched commission statement for state insurance department exams.
| Action | Who | Decision |
|---|---|---|
| draft_email | SDR agent | allowed |
| send_email | SDR agent | needs approval |
| update_opportunity | rep's assistant | allowed |
| mark_closed_won | rep's assistant | needs approval |
| bulk_delete_records | any agent | denied |
| send_for_signature | deal desk agent | needs approval |
Approval requests go to the rep or the deal desk in Slack or the web inbox (Teams and email coming soon).
Illustrative: names no package, import or API call
AI agents in Sales & Revenue: common questions
Can an AI agent email prospects on its own?
Only if you allow it. Many teams let the agent draft freely and mark the send tool as needs approval, so the rep confirms each message before it goes out.
Can an agent change pricing or discounts?
Price book and discount tools can be scoped to the pricing team or held for approval. Routing a discount to a different approver once it passes a set percentage is coming soon.
Can different reps' assistants have different access?
Yes. Policy can be scoped to a role or to one person, so RevOps can merge accounts while reps' assistants cannot. Inspect as user shows what each person's agent would get.
What does sales leadership see afterward?
A record of each decision: which agent called which tool from which person's session, what policy decided (allowed, held for approval, or denied) and how any approval request was answered. It covers the calls policy blocked as well as the ones it allowed.
Set this policy up for your own agents.
Start with your own agents, your tools and the approvers you already have.
Other functions
Finance & Accounting
Payments, the close, treasury, budgets and payroll.
Software Development & Engineering
Code review, releases, production systems and on-call.
IT & Security Operations
Identity, devices, threat response, SaaS admin and cloud.
People & HR
Hiring, onboarding, compensation, employee relations and training.
Marketing & Communications
Content, campaigns, paid media, social and the website.
Customer Support & Success
Ticket replies, refunds, privacy requests and escalations.
Legal, Risk & Compliance
Contracts, regulatory work, audit evidence, vendor risk and records.
Operations, Procurement & Facilities
Purchasing, vendors, inventory, facilities and projects.
Data, Analytics & AI Operations
Warehouse access, pipelines, agent-to-agent work, models and AI cost.

