- Salesforce Managed Services
Salesforce publishes one number for Agentforce, and it looks settled. $2 per Conversation. The billing event behind that number changes depending on which Agentforce product you run. ASA Messaging bills on a conversation window, Sales Coach bills when a seller clicks a button, and SDR bills when an agent sends its first email to a lead. Three products, three different things consuming the same $2 unit. Pricing checked: September 4, 2026.
Your forecast depends entirely on which event you count. Message volume tells you almost nothing about Agentforce $2 per conversation spend, and Salesforce Agentforce pricing gives you no shortcut around identifying the trigger that applies to your deployment. We built this page at VALiNTRY360 to walk the billing rules as Salesforce currently documents them, then show what the arithmetic does at real volume.
What Does Agentforce $2 Per Conversation Actually Buy?
- Published rate: $2 USD per Conversation, listed on Salesforce’s current pricing page and subject to whatever your contract negotiates from there.
- Eligible usage: customer-facing Agentforce agents under the applicable Conversation SKU, which excludes employee-facing agents and Voice deployments.
- Billing unit: one qualifying Conversation event, defined differently for each Agentforce subtype rather than by a single shared rule.
- Buying route: Salesforce currently excludes conversation-based pricing from PayGo and Pre-Commit, which leaves Pre-Purchase as the route.
- Multiplier: 1 for all three subtypes on the current rate card, so one qualifying event draws exactly one Conversation from entitlement.
- Tracking method: Digital Wallet, provided at no cost for enabled products, reporting consumption and remaining balance in near real time.
Two of those lines carry more weight than the rate itself. Customer-facing scope is the first filter Salesforce Agentforce pricing applies, so employee-facing agents and Voice deployments sit outside this SKU, and a mixed rollout will price on more than one meter at once.
Entitlement and usage are separate ideas, and Pre-Purchase keeps them separate. You buy a quantity of Conversations up front and draw them down as qualifying events occur, which makes Agentforce $2 per conversation planning a purchasing decision taken months before you hold any consumption data of your own.
Agentforce conversation pricing describes a usage unit and nothing wider. Implementation, integrations, and the AI and data usage running underneath an interaction sit outside that figure, and your contracted rate can differ from the published one once volume and term enter the negotiation. Our Agentforce AI consulting team maps workload behavior to a commercial model before a quote reaches procurement, working from Salesforce’s current Agentforce pricing page.
What Counts as an Agentforce Conversation?
Salesforce Help currently lists three Conversations billable usage subtypes, and each one consumes a Conversation on a completely different event with its own forecasting input.
Subtype | Consumption trigger | Forecasting input |
|---|---|---|
ASA Messaging | A qualifying conversation window opens | Conversation starts per channel |
Sales Coach | A user clicks Get Feedback after a role play or stand-and-deliver session | Feedback submissions |
SDR / Engagement | The agent sends the initial email to a lead | Leads entering outreach |
ASA Messaging is the one most buyers picture, and it runs on windows rather than exchanges. A customer can send 15 messages inside one open window and consume one Conversation. Sales Coach has no customer and no window, so the volume you forecast there is a coaching adoption number. SDR consumes its Conversation at the first outbound email, with subsequent activity for that lead included and a restart after cancellation consuming another.
Most deployments start with one subtype and add a second later. A service team starts with ASA Messaging, a sales org starts with SDR, and running both means maintaining two forecasts against one shared entitlement, since Agentforce $2 per conversation billing draws everything from a single pool.
Message count multiplied by $2 therefore produces a wrong answer in all three products. The correct input is the count of qualifying trigger events, and that is a different number in each product and a different report in each case. Salesforce documents all three in its Agentforce Conversations billable usage types reference, and estimating the Agentforce conversation cost of a service deployment starts with knowing which of the three you are buying. Our Agentforce for Service work begins by measuring conversation starts rather than case volume.
How ASA Messaging Conversation Windows Start and End
The window is where Agentforce $2 per conversation billing gets specific, and where most published guidance gets it wrong. A window opens when the customer sends a message for the first time after the previous window has ended, or when the service agent sends a configured welcome message first. That second trigger means the meter can start before the customer types anything.
How it closes depends on the channel.
Customer interaction
→ Which channel?
→ Enhanced Web Chat: authenticated or not?
→ Unauthenticated: the window ends when the user explicitly clicks End Conversation
→ Authenticated: the window ends 24 hours after it starts
→ In-App Chat, WhatsApp, Facebook Messenger, Apple Messages for Business, SMS, Bring Your Own Channel: the window ends 24 hours after it starts
→ The next message after that window closes opens a new billable one
Read the 24-hour rule carefully, because it runs from the start of the conversation rather than from the last message, and Salesforce describes no inactivity timer anywhere in its current documentation. That distinction drives your bill more than volume does. A customer who messages you three times across one afternoon on WhatsApp consumes 1 Conversation, and the same customer messaging once a day for three days consumes 3.
Identical message counts, triple the cost, and no volume forecast will surface the difference. Unauthenticated Enhanced Web Chat deserves its own check, since its window closes when the user clicks End Conversation and most people close the browser instead. Confirm the practical session behavior with your account team before you build a channel strategy on it.
Salesforce sets out the channel rules in its considerations for Agentforce Service Agent page. Our Agentforce Digital Engagement practice tests each deployed channel against its documented rule, and because channel mix is a commercial decision as much as a service one, our Agentforce Contact Center team models it before rollout.
Events That Can Create or Repeat a Billable Conversation
Each of the seven below is checkable in your own reporting today. Pull the numbers before you size an entitlement, because these events are what Agentforce $2 per conversation billing actually counts and what your forecast has to predict.
- A customer opens a new ASA messaging window. Look at unique conversation starts per channel per month in your Messaging session reports, which is a smaller number than message volume and a different number from case volume.
- A configured welcome message fires first. Check each Messaging channel for an automated welcome, because a welcome that sends before the customer speaks has already opened the window and started the meter running on a contact that may go nowhere.
- A previous 24-hour window has expired and the customer returns. Run a distribution of repeat contacts by hours since last contact, and treat everything falling past the 24-hour mark as a second billable Conversation rather than a continuation.
- An unauthenticated web user ends a conversation and comes back. Count End Conversation clicks against return visits, and measure browser abandonment separately, since the documented window stays open in that case and the return lands inside it.
- A seller clicks Get Feedback. Pull feedback submissions from Sales Coach, counted separately from coaching sessions held, since a session that ends without a feedback request consumes nothing and never reaches the meter.
- An SDR agent sends its first email to a lead. Count leads entering agent outreach in the period against total emails sent, because the gap between those two figures is nurture activity that carries no separate charge under the initial Conversation.
- Cancelled SDR outreach restarts. Check campaign cancellation and re-enrollment logs, since each qualifying restart consumes another Conversation for a lead you have already paid to reach once, which makes campaign hygiene a cost control.
Our Salesforce Service Cloud implementation services team validates items 1 through 4 during testing, because messaging, routing, and session configuration decide how many of those events your deployment generates.
What 1,000 to 50,000 Agentforce Conversations Cost
Illustrative arithmetic using Salesforce’s current $2 public list rate. Contract terms and other consumption are excluded.
Monthly conversations | Monthly public-rate amount | Annual public-rate amount |
|---|---|---|
1,000 | $2,000 | $24,000 |
5,000 | $10,000 | $120,000 |
10,000 | $20,000 | $240,000 |
25,000 | $50,000 | $600,000 |
50,000 | $100,000 | $1,200,000 |
The curve is linear, which makes it easy to underestimate. A mid-sized service team handling 10,000 conversation starts a month sits at $240,000 a year on the Conversation meter alone, before any other Salesforce usage is counted, and Agentforce conversation pricing carries no volume break in the published rate, so the ten-thousandth conversation start costs exactly what the first one did. Published rates and contracted rates are separate questions, and only the first one is on the pricing page.
Two forecasting errors cost real money here, and Pre-Purchase makes both of them expensive. Underestimating conversation starts leaves you buying more entitlement mid-term at whatever rate is available then. Overestimating them leaves you holding entitlement you cannot use, because the Conversations Rate Card states that Conversations must be used before the Order End Date set on the Order Form and no rollover is permitted.
Measuring Agentforce conversation cost against a real pilot beats modeling it from assumptions, which is why our Agentforce Quickstart exists as a way to get a traffic baseline before a large commitment. The current Conversations Rate Card, dated December 2024, sets out both the multiplier and the expiry rule.
What Can Cost Extra Beside the $2 Conversation Meter?
Five layers can appear on the invoice around a Conversation charge, and Agentforce $2 per conversation covers only the first.
- The conversation meter. Measures qualifying Conversation events drawn from your Pre-Purchased entitlement, priced at the rate your contract sets. Investigate before contracting, then monthly after launch.
- Model and AI usage. Measures Einstein Requests, which the Conversations Rate Card says certain Agentforce features may consume alongside Conversations. Investigate when the agent design calls the LLM heavily or generates long replies.
- Data consumption. Measures Data 360 or Data Services usage, depending on which consumption card your contract carries. Investigate when agents are grounded in unified data, a knowledge corpus, or documents you upload.
- Connected systems. Measures APIs, middleware, and the external systems your agent actions reach on either side of the interaction. Investigate when an agent writes to anything outside Salesforce.
- Delivery and operations. Measures configuration, testing, monitoring, and support, including the metered portion of your build and test cycle. Investigate at scoping, then monthly once the agent is live and owned.
One naming conflict is worth handling carefully rather than smoothing over. The Conversations Rate Card still says Data Services Credits while newer Salesforce product documentation discusses Data 360, those labels are not interchangeable, and your active contract and Digital Wallet cards decide which applies to you.
Salesforce Agentforce pricing publishes the units, and the billing constructs behind them appear in Agentforce and generative AI usage and billing. Agentforce Flex Credits sit outside this stack entirely, since they cannot run in the same org as Conversations.
Our Data 360 team at VALiNTRY360 sizes the data layer against the agent design rather than a generic profile count, and our Salesforce integration services practice scopes the connected-systems layer separately from the agent build.
Conversation Pricing vs Flex Credits and Other Salesforce Options
Salesforce currently publishes four consumption units a service buyer will encounter, and two of them cost $2.
Pricing unit | Billing event | Workload input | Planning issue |
|---|---|---|---|
Conversations, $2 | A qualifying Conversation window or event | Conversation starts by subtype | Pre-Purchase only, no rollover |
Flex Credits, $500 per 100,000 | Each metered action, prompt, or data operation | Actions per interaction | Cannot share an org with Conversations |
Help Agent Resolutions, $2 | A qualifying Help Agent resolution | Resolutions completed | Includes unmetered actions and Data 360 queries per resolution |
Service Portal Login, $4 | A portal login session | Logins per month | Includes unmetered activity during a 24 hour login session |
A $2 Conversation and a $2 Resolution are different billing events with different inclusions, so matching prices tell you nothing about matching value. The Resolution and Login units both bundle activity a Conversation does not, and the Login unit prices a portal session rather than a support interaction, which puts it in this comparison for teams running a self-service portal and nowhere else.
Agentforce Flex Credits give the cleanest arithmetic comparison. At $500 per 100,000 credits one credit lists at $0.005, the April 21, 2026 rate card puts a standard action at 20 production credits, and that makes a standard action $0.10 at list. Divide and you get a benchmark: $2 ÷ $0.10 = 20 standard actions.
Treat that as arithmetic and nothing more, because Agentforce $2 per conversation and the action meter measure different things and Salesforce Agentforce pricing publishes no conversion between them beyond this division. A real deployment also consumes prompts, Voice, and data operations, your contracted rates will differ from list on both sides, and Agentforce conversation pricing cannot coexist with credits in one org, which makes this a decision taken once per org. Salesforce publishes the Resolution and Login rates on its customer self-service pricing page and the action multipliers in the current Flex Credits rate card.
Original Cost Model: When Does $2 Become Expensive?
This is a VALiNTRY360 calculation model built on Salesforce’s published public pricing. The workloads are constructed to test the meter rather than drawn from customer accounts, and every figure shows its inputs.
Workload A: the short FAQ. Conversation volume: 1. Work completed: 2 standard actions to look up an order status and reply. Conversation price: $2. Action benchmark: 2 × $0.10 = $0.20. Other usage to check: one Einstein Request if the reply is generated. What would change it: nothing, since this is as thin as an interaction gets. Result: the Conversation meter charges 10 times the action equivalent.
Workload B: the multi-step service case. Conversation volume: 1. Work completed: 14 actions across identity checks, a policy lookup, an update, and a confirmation. Conversation price: $2. Action benchmark: 14 × $0.10 = $1.40. Other usage to check: prompts and any grounded data retrieval. What would change it: action count, which is a design decision rather than a customer behavior. Result: the two meters land within 43% of each other.
Workload C: repeat contact across days. Conversation volume: 3, since each 24-hour window closes before the next contact. Work completed: 4 actions per contact, 12 in total. Conversation price: 3 × $2 = $6. Action benchmark: 12 × $0.10 = $1.20. Other usage to check: whether channel mix pushes contacts across window boundaries. What would change it: how often contacts fall either side of a boundary. Result: the Conversation meter charges 5 times the action equivalent.
Workload D: the action-heavy workflow. Conversation volume: 1. Work completed: 35 actions in a long troubleshooting session. Conversation price: $2. Action benchmark: 35 × $0.10 = $3.50. Other usage to check: Voice actions at 30 credits each where the channel is voice. What would change it: escalation rate, since a session handed off early never reaches this count. Result: the Conversation meter costs 57% of the action equivalent.
The flat $2 rewards deep work inside a single window and penalizes thin, repeated contact, which makes Agentforce $2 per conversation cheap for Workload D and expensive for Workloads A and C. Agentforce conversation pricing therefore turns on two variables: work completed per window, and how often new windows open. Neither of those appears in a headcount, a case count, or a message count.
Measure both before you compare Salesforce Agentforce pricing models against each other. Agentforce conversation cost per useful outcome is the figure worth carrying into procurement, and Agentforce Flex Credits change that calculation rather than settling it.
Case Study: What 18,000 Agentforce Conversations Cost at List Rate
Salesforce publishes customer results on its own newsroom, and one of them is stated in the exact unit this page bills on. reMarkable has handled over 18,000 service conversations through Agentforce since deployment.
Salesforce publishes the volume rather than the invoice, which is useful, because the volume is the number a forecast has to get right and the invoice follows from it.
- Published volume: over 18,000 service conversations handled by Agentforce since deployment, reported by Salesforce.
- List-rate arithmetic: 18,000 × $2 = $36,000 under the Conversation meter at published rates.
- What is not published: the commercial model, the contracted rate, or whether Conversations are the meter in use at all.
- What the figure does show: a service deployment of that size reaching five figures on the Conversation meter before any other consumption is counted.
- The forecasting lesson: missing the volume estimate by 20% moves that number by $7,200, which is the cost of a bad baseline rather than a bad rate.
Salesforce publishes deflection figures alongside the volumes, and those decide how many conversation windows open in the first place. OpenTable reached 73% of restaurant web queries within three weeks, Datasite resolves 70% of day-to-day chat questions, and Fisher & Paykel moved self-service from 40% to 70%.
Read those as demand signals for the meter. A higher deflection rate means Agentforce is opening more of the windows itself, which raises the Conversation count at the same time as it lowers the human cost per contact. Both numbers move together, and only one of them lands on the Salesforce invoice.
That is the case for measuring conversation starts before signing rather than after. Deflection is the outcome most service teams are buying, and it is also the input that drives the Conversation meter upward as the agent gets better at its job.
Why Sales Coach and SDR Need Different Cost
Forecasts
Neither product has a customer messaging window, so the messaging model produces nothing usable for either one and both need a forecast built from their own trigger.
Sales Coach
Forecast from eligible sellers, role-play and stand-and-deliver sessions run per seller, the share of those sessions ending in a Get Feedback click, and adoption ramp across the rollout. The method is eligible coaching sessions multiplied by the percentage that end in a click.
Adoption moves this figure more than any other input, since an unused coaching tool consumes nothing at all and a well-adopted one consumes on every single submission a seller makes. Forecast the ramp rather than the steady state, because month 1 and month 9 produce very different consumption from the same seller population. Our Agentforce for Sales team models this against seller headcount and enablement cadence.
SDR and Engagement
Forecast from leads entering agent outreach, initial emails sent, cancellations, restarted outreach, and campaign growth. The method is initial outreach events plus qualifying restarted outreach, since Salesforce says subsequent agent activity for a lead stays inside the initial Conversation and adds nothing.
Restart behavior is the line item to watch. A team that cancels and relaunches campaigns frequently consumes a second Conversation on leads it has already paid to reach, and each Conversation can also consume Einstein Requests when it calls the LLM, so the outbound meter rarely runs alone. Our Agentforce for SDR Agent work starts with lead enrollment volume rather than email volume.
Run both forecasts separately and add them to the messaging number, because a single blended estimate across three products will be wrong in three different directions. VALiNTRY360 keeps the three components visible in the model, since Agentforce $2 per conversation spend moves for different reasons in each one.
Checklist: What to Measure Before Buying Conversations
Ten numbers to collect before you commit to an entitlement, each of which already exists somewhere in your reporting. Collect them from a live period rather than a design document, since the gap between how a channel was configured and how customers actually use it is where forecasts break.
- Monthly conversation starts. Unique messaging session starts by month, taken from your Messaging session reports across a representative period.
- Channel mix. Session volume split across Web Chat, In-App, WhatsApp, SMS, and every other deployed channel, measured over a full month.
- Authenticated versus unauthenticated web traffic. The ratio between them, since each carries a different window end rule and therefore a different billable count.
- Repeat-contact rate. Distribution of hours between contacts from one customer, bucketed either side of the 24-hour boundary that closes a window.
- Welcome-message configuration. Whether an automated welcome fires before the customer speaks, checked separately on every channel you have deployed.
- Work completed per conversation. Average action count per session, taken from agent design documents and validated against your testing logs.
- SDR initial outreach volume. Leads entering agent outreach per month, alongside restart frequency for the same period and the cancellation rate behind it.
- Sales Coach Get Feedback usage. Feedback submissions per month, counted separately from the coaching sessions that produced them.
- Other AI and data consumption. Your active Digital Wallet cards and the usage each one meters alongside the Conversation entitlement.
- Expected growth and unused-entitlement risk. Month-over-month trend measured against your Order End Date, tracked in both directions rather than only upward.
Work that list and Agentforce conversation pricing stops being a guess. Our team at VALiNTRY360 runs it as a pre-purchase assessment, since Agentforce conversation cost is decided by these ten inputs and Agentforce Flex Credits would be judged against the same evidence.
How to Forecast Conversation Demand Before Launch
The what is the count of qualifying billing events your workload will generate. The why is that Pre-Purchased entitlement is finite and expires at the Order End Date. The how is a monthly forecast rolled into a contract-term total, built in the order below.
- Baseline volume. Current monthly conversation starts, measured from live reporting rather than estimated from case counts or ticket volume.
- Billing trigger. The subtype rule that applies to each agent you run, since messaging, Sales Coach, and SDR each count a completely different event.
- Channel and authentication state. The end rule per channel, which decides how many separate windows a given contact pattern produces over a month.
- Repeat-contact behavior. The share of customers returning after their window closes, which multiplies windows without multiplying customers.
- Monthly growth. Expected trend across the contract term, applied month by month rather than as an annual average that flattens the shape.
- Peak-month factor. Seasonal or campaign-driven spikes, which raise the term total by more than a smoothed average would ever suggest.
- Rollout ramp. Pilot volumes differ from production volumes, so model the months between them rather than pricing the endpoint alone.
- Pre-purchase buffer. Headroom for forecast error, sized against how confident your baseline actually is and how volatile the underlying traffic has been.
- Resulting entitlement requirement. The sum of the adjusted monthly figures across the term, checked against the Order End Date before anything is signed.
Build it monthly rather than annually. A single annual average hides the peak months that decide whether you run short, and it hides the quiet months that decide whether you finish the term holding entitlement you cannot use.
Forecast Sales Coach from Get Feedback events and SDR from initial outreach on their own, then add all three into one entitlement figure while keeping the components visible. Agentforce $2 per conversation spend is only as accurate as the weakest of the three inputs, and Agentforce conversation cost errors compound across a full contract term.
How Implementation Choices Can Change Conversation Volume
Five build decisions affect when a billing window opens, and each of them moves Agentforce $2 per conversation spend without appearing anywhere in a price list. Test each rather than assuming the effect.
Welcome message. Possible billing effect: a configured welcome can open an ASA Messaging window before the customer sends anything at all. Validation: run the deployed messaging path end to end and check whether a session registers against the entitlement.
Authentication. Possible billing effect: authenticated Enhanced Web Chat closes 24 hours after the start, while unauthenticated closes only on an End Conversation click. Validation: test both journeys separately and compare the session records they produce.
Channel selection. Possible billing effect: each channel carries its own documented end rule, so one contact pattern produces different window counts across channels. Validation: map billing behavior per deployed channel before go-live.
Routing and session continuation. Possible billing effect: how a customer enters or resumes a messaging experience determines whether a new window opens or an existing one continues. Validation: test the actual handoff path rather than assuming a transfer rule Salesforce has not documented.
SDR restart behavior. Possible billing effect: restarting cancelled outreach for a lead consumes another Conversation against the same prospect. Validation: test campaign cancellation and re-enrollment logic against your consumption records.
Testing is metered in places. Salesforce says building in Agentforce Builder is not metered, while previewing an agent in chat or voice is, and testing through Testing Center and sandbox is metered to cover compute. Budget for the build cycle rather than treating non-production activity as free, because a thorough test pass across several channels and journeys lands before a single customer reaches the agent.
How to Monitor Conversation Spend and Decide Whether to Switch
Digital Wallet is where consumption becomes visible. Salesforce provides it at no cost for enabled products and reports usage in near real time, with threshold alerts and usage trends.
- Conversations consumed against forecast. Warning: consumption running above 110% of plan for two consecutive months. Action: reforecast the remaining term before the balance forces the decision for you.
- Entitlement remaining against months left. Warning: current burn rate implies exhaustion before the Order End Date arrives. Action: model the shortfall in months and open the purchase discussion early.
- Consumption by subtype. Warning: one subtype growing faster than the business driver sitting behind it. Action: audit that product’s trigger against its actual event volume for the period.
- Daily conversation starts. Warning: an unexplained step change with no matching movement in traffic. Action: check for a welcome-message, routing, or channel configuration change made that week.
- Projected Order End Date balance. Warning: material entitlement forecast to go unused before the term closes. Action: redirect volume where you can, and size the next term against measured demand rather than the original plan.
Reporting shows you the position without changing it, and no threshold alert stops a service when an entitlement runs down, so the review needs a named owner with time for it. Set the cadence monthly for the first two quarters, since consumption patterns settle only after the rollout ramp completes, and the early months are when a configuration change or an unexpected channel behavior is cheapest to catch and correct.
Switching models is possible and deliberate. Salesforce says a customer moving to Flex Credits must swap all existing Agentforce Conversation SKUs, and the two cannot run in the same org at once, so revisit the choice once you hold real data on work completed per window and on how often new windows open. Agentforce Flex Credits become the better fit only when that data says so. Those two numbers decide whether Agentforce $2 per conversation or Agentforce Flex Credits suits the workload.
Salesforce documents the tracking in its Digital Wallet usage monitoring guidance. Our Agentforce Managed Services team at VALiNTRY360 runs this review monthly, our Salesforce Service Cloud support practice handles the channel and routing changes that follow from it, and both Agentforce conversation pricing and Salesforce Agentforce pricing alternatives read differently once you are working from your own consumption data.
FAQs About Agentforce $2 Per Conversation Pricing
How much does an Agentforce Conversation cost?
Salesforce Agentforce pricing lists Conversations at $2 each for customer-facing agents, bought through the Pre-Purchase route. That is a public list rate, and your contracted rate can differ once volume and contract term are negotiated. Pricing checked September 4, 2026.
What counts as one Agentforce Conversation?
The trigger depends on the subtype. ASA Messaging consumes one when a qualifying conversation window opens, Sales Coach when a user clicks Get Feedback after a coaching session, and SDR when the agent sends its initial email to a lead.
Does every Agentforce message cost $2?
Messaging bills on windows. A customer can exchange many messages inside one open conversation window and consume a single $2 Conversation. Your cost tracks how often new windows open, which is a different number from message volume.
Does an Agentforce Conversation always last 24 hours?
It depends on the channel. Authenticated Enhanced Web Chat, In-App Chat, WhatsApp, Facebook Messenger, Apple Messages for Business, SMS, and Bring Your Own Channel end 24 hours after the start. Unauthenticated Enhanced Web Chat ends when the user explicitly ends it.
Can a welcome message start a billable Conversation?
Yes. Salesforce documents that an ASA Messaging conversation window can begin when the service agent sends a pre-configured welcome message first, before the customer sends anything. Check your channel setup to see whether that applies to your deployment.
How does Salesforce bill Agentforce SDR Conversations?
One Conversation is consumed when the SDR agent sends its initial email to a lead. Subsequent activities for that lead stay inside the initial Conversation. Restarting outreach for the same lead after cancellation consumes another Conversation.
Is Agentforce conversation pricing cheaper than Flex Credits?
It depends on your workload. At list rates $2 equals 20 standard actions, so deep sessions favor the flat unit and thin, repeated contacts favor metered actions. Agentforce Flex Credits and Conversations also cannot run in the same org.
Do unused Agentforce Conversations roll over?
No. The current Conversations Rate Card states that Conversations must be used before the Order End Date set out on the Order Form, and no rollover is permitted. Overbuying entitlement on a Pre-Purchase model is a real cost risk.
Can Conversations and Flex Credits run in the same Salesforce org?
No. Salesforce states the two are not supported in the same org. Moving from Conversations to Flex Credits requires swapping all existing Agentforce Conversation SKUs, which is a contract change rather than a setting.
How can I estimate Agentforce conversation cost before launch?
Run a pilot and measure conversation starts by channel, repeat-contact patterns either side of the 24-hour mark, SDR outreach volume, and Sales Coach feedback events. Add expected growth, then size the entitlement against your contract term.