Blog/ AI email prompts & use-cases

AI Email Prompts for Account Managers: 20 Prompts

Nafiul HasanNafiul Hasan· 25 min read
AI Emaily blog cover showing an account manager using AI to draft a QBR follow-up and at-risk check-in email for a client portfolio

The short answer

AI email prompts help account managers write QBR recaps, renewal nudges, scope-pushback notes, price-change notices, escalation handoffs, and at-risk check-ins. Declare the account health, contract stage, and last commitment in every prompt so the AI drafts to the real relationship state instead of assuming everything is fine.

20 AI email prompts for account managers: QBR recaps, renewal nudges, at-risk check-ins, scope pushback, and escalation handoffs.

On this page
  1. 01When do account managers reach for these prompts?
  2. 02What does every account management email need to declare?
  3. 03QBR follow-up prompts
  4. 04Renewal nudge prompts
  5. 05Scope pushback prompts
  6. 06Price-change notice prompts
  7. 07Escalation handoff prompts
  8. 08At-risk check-in prompts: the hard version
  9. 09What to do when there is no reply
  10. 10How AI Emaily handles this across your full book of business

Account managers deal in relationships, not transactions. The email you send three days after a QBR lands differently depending on whether the client hit their goals or missed them by 40 percent. A renewal nudge to a strong advocate reads nothing like one to an exec who has been quietly shopping alternatives. Yet most AI-generated account management emails ignore this entirely. The model writes a cheerful, generic note, and the AM edits it for ten minutes trying to add the tension that should have been in the prompt.

The fix is straightforward: declare the relationship state before you ask for anything. Tell the model the account health, the contract stage, and the last thing that was committed. Do that and the draft arrives already calibrated to the conversation you are actually in, not the one the model imagines you might be having. A model that knows the account is at red health writes a very different check-in than one that assumes green.

This guide gives you twenty prompts organized by the six situations account managers face most often: QBR follow-ups, renewal nudges, scope pushback, price-change notices, escalation handoffs, and at-risk check-ins. Each prompt is copy-paste ready and shows the kind of draft it produces. Fill the bracketed fields for your account and send.

When do account managers reach for these prompts?#

Account management runs on a predictable calendar. QBRs happen quarterly. Renewals come around annually or on a multi-year cycle, with outreach starting 90 to 180 days before the date. Scope conversations happen whenever a client asks for something outside the contract. Price adjustments follow cost reviews or contract anniversaries. Escalations happen when a client is unhappy enough to involve leadership. At-risk check-ins happen when usage drops, a champion leaves, or the account goes quiet at a moment when it should not.

Each of those moments has its own email job. A QBR recap is a record and a commitment device. A renewal nudge is a value conversation that starts early enough to address concerns before they become a decision. A scope pushback is a boundary held with warmth. A price-change notice is a clarity document that respects the client enough to give them time. An escalation handoff is a trust transfer. An at-risk check-in is a direct question about whether the relationship is intact.

AI is well suited to all of them because each follows a recognizable structure, and structure is exactly what large language models handle reliably. The prompt does the structural work. You supply the account-specific facts that make the email real.

What does every account management email need to declare?#

Before the prompts, a short framework. Every AM email, whatever the occasion, is stronger when it declares three things in the prompt: the account's current health, the contract or relationship stage, and the last concrete commitment made by either side. Health tells the model whether to write with confidence or with concern. Stage tells it whether this is a first touch or a critical juncture. Last commitment anchors the email in what was actually agreed, so the note reads as a continuation of a real conversation instead of a generic update.

Beyond those three, the structure varies by type. A QBR recap states decisions, actions, and owners. A renewal nudge leads with value delivered before it asks for a commitment. A scope pushback names the boundary and offers a legitimate path. A price notice explains the reason and the timeline. An escalation note introduces the new contact with enough context that the client does not have to start over. An at-risk check-in asks a direct question rather than talking around the problem.

Email typeDeclare in the promptLead with
QBR follow-upResults vs. targets, decisions made, open items with ownersA summary of what was agreed
Renewal nudgeMonths to renewal, current health, key wins deliveredValue already delivered
Scope pushbackWhat was asked, what is out of scope, relationship warmthAcknowledgment, then the boundary
Price-change noticeEffective date, reason category, length of relationshipThe new rate, then the why
Escalation handoffThe issue, the new contact, what the client has already triedOwnership of the problem
At-risk check-inUsage trend or signal, last meaningful conversation, health statusA direct, caring question

The relationship-state rule

Every prompt in this guide has a bracket for account health, contract stage, or last commitment. Do not skip it. A model that knows the account is at yellow health writes a very different email than one that assumes green. That calibration is the whole point of structured prompting for account management, and no amount of editing after the fact replaces getting it right in the prompt.

QBR follow-up prompts#

The QBR recap is one of the highest-leverage emails an account manager sends. It turns a conversation into a record, assigns ownership to commitments, and keeps the partnership moving between calls. Send it within 24 hours while the discussion is fresh. The first prompt handles a strong QBR where results met or exceeded expectations. The second handles the more common situation where at least one metric fell short.

Prompt 1 — QBR recap after a strong quarter
PromptWrite a QBR follow-up email to [client name] after today's quarterly review. Account health: green. Key results: [list 2-3 wins, e.g. 94% adoption, 18% reduction in support tickets]. Decisions made: [list decisions]. Open items with owners: [list items, owners, and due dates]. Next QBR: [date]. Warm and professional tone. Under 200 words. Format decisions and open items as a short bulleted list.
DraftHi [name], thanks for a productive review today. Quick recap to keep us aligned: Results this quarter: [win 1]; [win 2]; [win 3]. Decisions: [decision 1]; [decision 2]. Open items: [Owner A] to [action] by [date]; [Owner B] to [action] by [date]. We are on track for [next milestone]. Next QBR is [date] — I will send an agenda a week out. Thanks again, [you]

When results fell short, the recap still needs to go out the same day, but the framing shifts. The goal is to acknowledge what happened, lock in the corrective actions, and keep the client confident that the problem is being handled. Avoid language that softens the miss into invisibility.

Prompt 2 — QBR recap when results missed targets
PromptWrite a QBR follow-up email to [client name] after a review where [metric] came in at [result] against a target of [target]. Account health: yellow. Tone: direct and ownership-taking, not defensive. Acknowledge the shortfall plainly, state the root cause agreed on the call, list corrective actions with owners and due dates, and confirm the next check-in milestone. Under 180 words.
DraftHi [name], following up on today's review. To put it plainly: [metric] landed at [result] against our [target] target, and we own that. Root cause as we discussed: [cause]. What we are doing about it: [Owner] to [action] by [date]; [Owner] to [action] by [date]. I will check in on [interim milestone date] to give you a progress update before the next QBR. Thanks for your candor today. [you]

Sometimes the contact who needs the recap was not in the room. The next prompt handles the non-attendee update, which requires a tighter summary because the reader has no context from the call. The last prompt covers an unresolved item that came out of the review and needs a follow-up decision.

Prompt 3 — QBR update to a stakeholder who did not attend
PromptWrite a post-QBR update to [name], who did not attend today's review. They are [role] at [company]. Summarize where the account stands in one paragraph, highlight the two or three most important outcomes from the meeting, list the actions they specifically own, and note the next milestone. Scannable, under 150 words, assume they are busy.
DraftHi [name], quick summary from today's QBR since you could not join: The account is [health status]. Key takeaways: [point 1]; [point 2]; [point 3]. Your action items: [Owner A] to [action] by [date]. Next checkpoint: [date]. Full notes are attached if you want the detail. Let me know if anything needs clarifying. [you]
Prompt 4 — Following up on an unresolved QBR item
PromptWrite a short follow-up email to [name] about an item left unresolved in our QBR: [describe the item]. We agreed to have a decision by [date]. Remind them of the item and why it matters for [business outcome]. Ask for a decision or a call to work through it. Under 100 words. No guilt, just clarity.
DraftHi [name], circling back on [the open item] from our QBR. We flagged [date] as the decision point because [business outcome] depends on it. Could you share a direction by then, or would a 20-minute call this week be easier to work through? Happy to prepare a one-pager if that helps. [you]

Renewal nudge prompts#

Renewals are won or lost long before the renewal date. An account manager who starts the conversation 90 to 180 days out has room to address objections, demonstrate value, and bring in the right stakeholders. The AM who starts 30 days out is negotiating under pressure. The four prompts below cover the full timeline, from early value-led outreach to the late-stage nudge when the clock is running short.

Prompt 5 — Early renewal outreach (90+ days out)
PromptWrite a renewal outreach email to [name] at [company]. Their renewal date is [date], about [X] months away. Account health: green. Key wins delivered this year: [list 2-3 concrete outcomes]. I want to start the conversation early, remind them of the value delivered, and open a door to discuss what they need from the next term. Under 180 words. No pressure, just a check-in with a clear offer to talk.
DraftHi [name], with your renewal coming up in [X] months, I wanted to reach out now rather than when the timeline is tight. Looking back at the year: [win 1]; [win 2]; [win 3]. As we head into the next term, I would love to hear what is on your roadmap and make sure what we deliver keeps pace. Would a 30-minute call in the next few weeks make sense? Happy to work around your schedule. [you]
Prompt 6 — Mid-cycle renewal check-in
PromptWrite a mid-term check-in email to [name], six months into their contract, to gauge satisfaction and lay groundwork for renewal in [X] months. Account health: [green/yellow/red]. If health is yellow or red, acknowledge it and ask what would need to change. If green, reinforce value and ask what a successful next term looks like. Under 150 words. Conversational, not salesy.
Draft (green health)Hi [name], we are at the midpoint of your contract and I wanted to check in — not to sell anything, just to ask: what is working well, and what would make the next six months even more valuable? I would also love to understand what you are planning for [next year's initiative] so we can position ourselves to help. A short call or a few lines by email both work. [you]
Draft (yellow health)Hi [name], we are halfway through the contract and I want to be direct: I know [the issue] has not gone the way either of us wanted. I am not waiting for the renewal conversation to address it. What would need to change for you to feel confident about the next term? I would rather know now and fix it. [you]
Prompt 7 — Late renewal nudge (30 days out)
PromptWrite a renewal nudge to [name] with 30 days until their contract expires. Account health: yellow. They have not engaged on renewal discussions. Acknowledge the short timeline, reference one concrete win from the year, ask directly if there are concerns holding up the decision, and offer to escalate to my leadership if that would help. Under 150 words. Direct, not desperate.
DraftHi [name], your contract expires on [date] and I want to make sure we have time to handle this properly rather than rushing at the last minute. This year, [concrete win]. I also want to ask directly: is there anything making this decision harder on your end? If bringing in my [VP/director] would help move things forward, I am happy to set that up. What is the best next step? [you]

Declare health before you draft a renewal

The same renewal prompt at green and red health should produce two very different emails. Include the account health explicitly in every renewal prompt. The model will not assume the relationship is strained unless you say so, and a cheerful renewal email to a dissatisfied client makes the situation worse, not better.
Prompt 8 — Renewal after a rough quarter
PromptWrite a renewal email to [name] whose account had a significant service issue in [month] that was resolved in [month]. The relationship recovered but trust is still rebuilding. Acknowledge what happened in one plain sentence without dwelling on it, pivot to what was fixed and what has been stable since, and make the renewal ask. Under 160 words. Honest and forward-looking.
DraftHi [name], I know [month]'s issue tested your confidence in us, and I am not going to pretend otherwise. Since the fix went in on [date], [stability metric or outcome]. The steps we put in place to prevent a recurrence are [brief summary]. We would like to earn the next term, and I am committed to making sure the value we deliver this year reflects that. Would you be open to a call this week to talk through what the renewal looks like? [you]

Scope pushback prompts#

Scope conversations are some of the hardest emails to write. You need to hold a boundary without sounding inflexible, and you need to offer a path so the client does not feel like you are simply refusing. The three prompts below handle the most common situations: a single out-of-scope request, a pattern of scope creep that has accumulated over time, and the change-order redirect.

Prompt 9 — Declining a single out-of-scope request
PromptWrite a polite but clear email to [name] declining a request for [out-of-scope item], which falls outside our current agreement covering [scope summary]. Acknowledge the request, explain that it is outside the current scope in one sentence without apologizing for it, and offer two options: a change order to add it, or a conversation to reprioritize what is already in scope. Under 150 words. Warm and collaborative.
DraftHi [name], thanks for flagging this. [The request] is not covered under our current agreement, which focuses on [scope summary]. That is not a no to the idea, just a question of how we scope it. Two options: I can put together a change order so we can add it cleanly, or we can talk about reprioritizing something already in scope if this is the higher-value item for you right now. Which would be more useful? [you]
Prompt 10 — Addressing accumulated scope creep
PromptWrite a scope conversation opener to [name] where the client has been adding small out-of-scope requests over several months. I want to name the pattern directly without sounding accusatory, show the cumulative impact with a brief summary, and propose a scoping conversation to either expand the contract or reset expectations. Under 180 words. Matter-of-fact, not confrontational.
DraftHi [name], I want to raise something I should have flagged sooner. Over the past few months, the work has expanded beyond our original scope in a few ways: [brief list of 2-3 items]. Each individually felt manageable, but together they represent [time or cost impact]. I would rather address this openly than let it affect the quality of what we deliver. Could we find 30 minutes to talk about whether the contract should reflect the current scope? I can come prepared with options. [you]
Prompt 11 — Change-order redirect for recurring requests
PromptWrite an email to [name] redirecting a recurring type of out-of-scope request toward a formal change order process. They have repeatedly asked for [type of requests]. Be direct that these need to go through a change order, but make the process easy: offer to draft it for them, give a rough turnaround timeline, and keep the relationship tone warm. Under 130 words.
DraftHi [name], for [type of requests] going forward, I want to route these through our change order process so the work gets properly resourced and does not compete with what we have already committed to delivering. Here is what I can do to make it easy: send me the details of what you need and I will draft the change order for your review. Turnaround is typically [X days]. That way you have a clear scope and timeline from the start. Sound good? [you]

Price-change notice prompts#

A price-change email fails in two predictable ways: it arrives too late for the client to plan around it, or it buries the number in so much context that the client has to search for it. Both feel disrespectful. The prompts below lead with the change, follow with the reason, and give a clear effective date. Long-tenured clients get more context; the third prompt handles that specific situation.

Prompt 12 — Standard price-increase announcement
PromptWrite a price-increase notice to [name] at [company]. New rate: [amount or percentage increase]. Effective date: [date]. Reason: [general category, e.g. infrastructure costs, expanded feature set, market adjustment]. Client tenure: [X years]. Lead with the rate change in the first sentence, give the reason in one clear paragraph, offer a call to discuss specifics, and note that renewals signed before [date] lock in the current rate. Under 180 words. Professional and direct.
DraftHi [name], starting [date], our pricing will increase by [amount or percentage]. The reason: [one clear sentence on the driver]. As a [X]-year client, I wanted to give you maximum notice and make sure you have the option to lock in your current rate by renewing before [date]. I am also happy to walk through what the change looks like for your account on a quick call. Let me know if that would be useful. [you]

For a long-tenured client who has never seen a rate increase, the email needs to feel like a genuine conversation, not a form letter. The prompt below builds in that history explicitly.

Prompt 13 — Price change for a long-tenured client
PromptWrite a price-change notice to [name], a client of [X] years who has never seen a rate increase. New rate: [amount or percentage]. Effective: [date]. Acknowledge the history, be honest about why the change is necessary now, give them the early-lock option, and offer to discuss. Under 200 words. The tone should feel like a conversation between partners, not a policy notice.
DraftHi [name], I want to be upfront with you about something. After [X] years with no rate changes, we are making an adjustment: [new rate or percentage], effective [date]. The honest reason: [one sentence on the driver]. I know this changes a long period of stability, and I did not want you to see it first in a contract renewal notice. You have the option to lock in your current rate by renewing before [date]. I am also happy to talk through the impact on your account directly. You deserve the full conversation. [you]

Lead with the number

A price-change email that opens with three paragraphs of context before naming the new rate makes the client search for the information that affects them most. Lead with the change in the first or second sentence regardless of how much context surrounds it. A reader who has to hunt for the number will be more frustrated than one who sees it first and then understands why.
Prompt 14 — Rate adjustment tied to expanded usage
PromptWrite a pricing conversation opener to [name] whose account has grown significantly beyond the original agreement: [describe the growth, e.g. 3x seat count, usage 40% above contracted volume]. Acknowledge the growth as a positive signal, explain that we need to adjust the rate to reflect current usage, and propose a call to work out a structure that makes sense for where they are now. Under 160 words. Frame as a partnership conversation, not an invoice.
DraftHi [name], I have been watching your account grow this year and I want to acknowledge it: [the growth detail]. That is a real signal of the value the team is getting. It also means we should talk about pricing that reflects where you actually are today rather than where you were when we signed the original contract. I want to make sure the structure works for both sides long-term. Could we find 30 minutes this week to work through some options? I will come prepared. [you]

Escalation handoff prompts#

An escalation email has one job: transfer trust. The client is frustrated, something went wrong, and they need to know that the right person now owns the problem. A weak escalation email introduces a new contact without context and puts the burden back on the client to re-explain the situation. A strong one brings the new contact up to speed, confirms ownership clearly, and gives a specific next step.

Prompt 15 — Introducing the escalation contact
PromptWrite an escalation handoff email introducing [escalation contact name and title] to [client name] after [describe the issue]. The client has been dealing with [describe what they have tried]. Transfer ownership clearly to [escalation contact], summarize the history in 2-3 lines so the client does not have to repeat it, and give a specific next step with a timeline. Under 180 words. The client should feel the problem is in more capable hands, not that they are being passed off.
DraftHi [client name], I am bringing in [escalation contact], our [title], to take point on this directly. To make sure [escalation contact] is fully up to speed: [2-3 line summary of the issue and what has been tried]. [Escalation contact], over to you. [Client name], [escalation contact] will reach out by [specific time today/tomorrow]. You have my direct line if anything changes in the meantime. [you]
Prompt 16 — Escalation email after a service failure
PromptWrite an escalation email to [name] after a service failure that caused [describe impact, e.g. four hours of downtime, a missed launch date]. Take clear ownership without qualifying the failure. State the cause in one sentence, describe what has been fixed, give a concrete remediation step, and confirm the ongoing contact. Under 200 words. No passive voice, no corporate hedging.
DraftHi [name], what happened on [date] was unacceptable and I am not going to qualify that. The cause was [one clear sentence]. It has been resolved by [specific fix]. What we are doing about it: [concrete remediation step, e.g. a service credit, a post-mortem shared with you, a dedicated on-call contact through [date]]. Going forward, [name and title] is your primary contact and has my direct escalation line. I will also send you a written root-cause summary by [date]. You deserved better and I am committed to making sure this does not happen again. [you]
Prompt 17 — Client requesting executive escalation
PromptWrite an email to [client name] who has asked to speak with executive leadership about [the issue]. Acknowledge the request without being defensive, confirm that I am arranging the call, give a proposed date and time with a backup, and describe briefly who will be on our side. Under 120 words. The client should feel heard, not managed.
DraftHi [name], understood, and I respect the request. I am setting up a call with [executive name, title] for [proposed date and time, plus a backup option]. On our side it will be [names and roles]. Could you confirm if [time] works, or send two or three alternatives if not? I will make sure [executive name] is fully briefed before the call. [you]

At-risk check-in prompts: the hard version#

These are the prompts the account management calendar does not schedule. At-risk check-ins happen when something signals that the account is quietly in trouble: usage has dropped for two consecutive months, the main champion just accepted a role elsewhere, or a client who used to reply within hours has gone silent for three weeks. The instinct is to send a cheerful email as if nothing is wrong. The better move is to ask directly.

An at-risk check-in that works is short, specific, and honest. It names the signal in one sentence rather than pretending not to notice it. It offers a door and asks an easy question. These prompts are harder to write than renewal nudges because they require the AM to name something uncomfortable. That discomfort is also why they work: the client sees that you are paying attention.

Prompt 18 — Declining usage check-in
PromptWrite a check-in email to [name] whose account usage has dropped by [percentage] over the past [timeframe]. Account health: yellow trending red. Name the usage trend in one plain sentence, do not make them feel accused of anything, ask directly whether something has changed on their end, and offer to help if there is a blocker. Under 120 words. No corporate softening.
DraftHi [name], I noticed usage has been lower over the past [timeframe] and I wanted to ask directly rather than wait for the next QBR: is something blocking adoption on your end, or has something shifted in your team's priorities? I would rather know now and help you get value from what you have than find out at renewal. Happy to jump on a call if that is easier. [you]
Prompt 19 — Champion departure check-in
PromptWrite a check-in email after learning that [champion name], our main internal contact at [company], has left the company. Acknowledge the transition warmly, ask who is taking over the account relationship, offer to help onboard the new contact, and keep the door open with the departing champion for future connections. Under 150 words.
To departing championHi [champion name], I heard you are moving on from [company] and I wanted to reach out before you go. Working with you has been genuinely great, and I hope the next role is everything it should be. Could you let me know who will be taking over the account relationship? I would love to get them up to speed quickly so nothing falls through the gap. And wherever you land next, I hope our paths cross again. Congratulations on what is ahead. [you]
To new contactHi [new contact name], I am [your name], your account manager at [company]. [Champion name] mentioned you would be taking over the relationship. I would love to set up a brief intro call to share where things stand and understand your priorities for the account. Does [date/time] work? [you]
Prompt 20 — Re-engagement after unexpected silence
PromptWrite a direct re-engagement email to [name] who has not responded in [timeframe] despite [number] outreach attempts. This is unusual given the normal cadence of the relationship. Account health: unclear. Name the silence in one sentence without guilt-tripping them, ask one direct question about whether everything is okay with the account, and give them an easy out if the timing is bad. Under 100 words. No passive-aggression, no fake urgency.
DraftHi [name], I have reached out a few times without hearing back, which is not like our usual rhythm. I want to ask directly: is everything okay with the account, or has something changed? If the timing is bad or something has shifted on your end, I would genuinely rather know than keep guessing. A quick reply either way would mean a lot. [you]

Check before you send an at-risk email

Before sending an at-risk check-in, verify there is not an obvious explanation for the silence: a public holiday, a visible company crisis, a major product launch. An at-risk email sent to a client who just had a high-pressure internal event can read as tone-deaf and make the relationship harder to recover. When the cause is unclear, a one-line check-in asking if it is a good time to connect costs nothing and avoids the misstep.

What to do when there is no reply#

Account managers who do not hear back after a check-in or renewal nudge often wait too long to follow up, then re-send the same email. Both are mistakes. The right move is to wait a reasonable interval — three to five business days for a warm client, one week for a cooler one — then send a shorter, different message rather than a copy of the first one.

The second touch should acknowledge the silence in one sentence and not make it the story. Something like 'I want to make sure this did not get buried' is enough. Then restate the one thing you need and make it easy to answer. For a renewal conversation, 'Is a call still useful, or would you prefer I send the renewal terms in writing?' is easier to respond to than 'Following up on my last email.'

After two attempts with no reply, the situation is either a communication breakdown or a signal about the account. A third attempt should ask a direct question: 'Is the timing wrong, or should we have a different kind of conversation?' That phrasing opens the door to a harder discussion without forcing it. It also gives the client permission to be honest, which is what an account manager needs more than silence.

How AI Emaily handles this across your full book of business#

The twenty prompts above work in any AI tool. The gap is not the drafting. It is knowing which accounts need which email today, across a book of business that might run to fifty or a hundred relationships at different health states, contract stages, and communication histories. That context lives in your inbox, not in a chatbot that has no view of it.

AI Emaily connects directly to your Gmail, Outlook, or IMAP account and lets you set a Context Brain for each client — capturing their account health, contract stage, and communication preferences — so every draft the assistant writes is grounded in the relationship state this guide tells you to declare manually. Copilot mode queues every draft for your review before anything sends, with a full audit trail and undo on every action. Your client emails stay in your inbox, not a third-party training dataset. Learn more at aiemaily.com, or start a 7-day free trial at aiemaily.com/pricing. No migration required. We build AI Emaily.

Frequently asked

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Stop writing account emails from scratch.

AI Emaily drafts QBR recaps, renewal nudges, and at-risk check-ins grounded in your real client context — with Copilot approval before anything sends, full undo, and an audit trail. Start a 7-day free trial at aiemaily.com/pricing.

  • 7-day free trial
  • Cancel anytime
  • Every provider