An AI plugin customer FAQ is not just support copy. It is the place where a plugin, CMS product, or commerce app team explains why AI usage is different from ordinary software features.
If your product includes AI writing, semantic search, product enrichment, review summaries, support answers, or lead qualification, users will eventually ask the same questions: what is included, what counts as usage, what happens when limits run out, and why some AI actions are paid separately.
That question is fair. CMS distribution is large. W3Techs’ CMS usage report shows how broad the plugin and CMS market is, and even a small group of heavy users can create a lot of AI traffic at that scale. AI pricing also varies by model, input, output, and media type, as public model pricing pages such as Google Gemini API pricing make clear.
Use the template below as customer-facing language. Replace the bracketed details with your product’s actual features, usage units, credit rules, and billing labels.
Why Plugin Teams Need an AI Usage FAQ
Traditional plugin features usually have predictable costs. A settings page, shortcode, widget, admin screen, or checkout rule can be offered inside a yearly license or lifetime license without changing cost dramatically each time a customer clicks a button.
AI actions are different. A content generation request, vector search query, product description rewrite, support answer, or document summary may call an AI model. Cost can change with prompt length, output length, model choice, media type, retrieval steps, retries, and customer volume.
That is why many AI products are moving toward usage-based, workflow-based, or hybrid pricing. Bessemer’s AI pricing and monetization playbook describes usage-based pricing, outcome-based pricing, and hybrid models as common ways to connect AI revenue to the actual value and cost of usage.
For plugin teams, the customer FAQ turns that pricing logic into plain language. It should answer questions before a user hits a limit, opens a ticket, or assumes the AI feature was supposed to be unlimited forever.
The Money Flow Your FAQ Should Explain
If your plugin routes paid AI actions through ShareAI Builder, keep the explanation simple.
Your team still builds, ships, supports, and controls the plugin outside ShareAI. ShareAI is not the plugin builder, CMS, hosting platform, or application framework. ShareAI handles the routed AI inference usage, customer payment for that usage, margin or surcharge logic, and monthly Builder payout.
| Role | What they do | What customers should understand |
|---|---|---|
| Plugin or CMS team | Owns the product and decides which AI actions are paid, included, or limited. | The app experience stays under the product team’s control. |
| Customer | Uses AI actions inside the plugin, site, store, or workspace. | They pay for metered AI usage when the product routes paid AI actions through ShareAI. |
| ShareAI | Routes AI inference traffic, tracks usage, handles payment, and supports Builder margin logic. | ShareAI is the AI marketplace and API layer behind the routed usage. |
| Provider | Contributes eligible compute capacity to the ShareAI network. | Provider rewards are separate from Builder payouts. |
FAQ: AI Plugin Customer Usage Template
Use these questions as a starting point for your docs, onboarding emails, pricing page, admin tooltip, or support macros. Keep the answers short and specific to your product.
1. What counts as an AI action?
An AI action is any feature that sends a request to an AI model to generate, search, summarize, classify, rewrite, enrich, or answer something. In this product, AI actions may include [content generations], [search queries], [product descriptions], [support answers], [summaries], or [lead qualification requests].
2. Are AI features included in my plugin license?
Your plugin license includes access to the plugin features listed on your plan. Some AI usage may be included as a starter allowance. Additional AI usage may be paid separately because each AI request creates real inference traffic.
3. Why is AI usage billed separately?
AI usage is billed separately so light users do not subsidize heavy users. A small site may run a few AI actions per month, while a busy store, agency, or content team may run thousands. Metered usage keeps pricing closer to actual consumption.
4. How do AI credits work?
AI credits are a simple way to represent included or prepaid usage. Your account receives [X credits] for [billing period or license term]. Each AI action uses credits based on the action type, model, or amount of generated work.
5. What happens when I run out of credits?
When your included credits run out, the plugin should pause paid AI actions, ask you to add more usage, or route additional usage through the configured paid path. Standard non-AI plugin features should continue to work unless your plan says otherwise.
6. Can I buy AI top-ups?
If top-ups are enabled, you can buy extra AI usage for high-volume periods. Top-ups are useful for launches, migrations, seasonal catalog updates, support spikes, or agency client work where AI demand changes month to month.
7. Can I set limits by site, license, workspace, or user?
If the plugin includes admin controls, you can set limits by [site], [license], [workspace], [client], [role], or [user]. Limits help teams avoid surprise usage, control client accounts, and keep high-volume AI actions intentional.
8. Can I use my own AI API key?
Some products offer bring-your-own-key options, and some use a managed routed-usage model. If BYOK is available, you may connect your own provider account. If ShareAI-routed usage is enabled, the product can manage model access, usage tracking, billing, and paid AI actions through ShareAI.
9. Who charges me for paid AI usage?
For ShareAI-routed paid AI actions, the customer pays ShareAI for the routed usage. The plugin team may earn a configured margin or surcharge from that usage. The plugin license and the AI usage charge should be shown as separate billing concepts.
10. Does every customer pay the same amount for AI?
No. AI usage should reflect actual activity. A customer who runs ten summaries should not pay the same AI usage amount as a customer who generates thousands of descriptions, answers, rewrites, or searches.
11. What should agencies tell their clients?
Agencies should explain that the plugin or client workflow may include a base implementation fee, license, or maintenance plan, while AI usage can be billed separately when clients keep using AI features after launch. Do not describe this as guaranteed revenue. Tie it to actual usage and client outcomes.
12. How can I see what used my AI balance?
The product should show a usage history that names the site, feature, action type, workspace, user, or license that generated the AI action. The more visible the usage record is, the fewer billing questions customers will have later.
How to Customize the Template
Before publishing this FAQ, replace generic language with your exact product terms. The best customer-facing FAQ does not say “AI usage may vary” and then stop. It names the actions people recognize inside your plugin.
- Name the actual AI units: generations, searches, summaries, tickets, product enrichments, images, minutes, or workflows.
- Separate the base license from AI usage so customers understand what they bought and what is metered.
- Explain when usage is counted: before the model call, after a successful response, after a saved output, or after a completed workflow.
- Show what happens at the limit: pause, warning, top-up, downgrade, fallback, or admin approval.
- Describe BYOK only if your product actually supports it.
- Avoid unlimited AI claims unless your team can absorb heavy-user inference costs indefinitely.
- Avoid privacy, compliance, or hosting guarantees unless your product and legal docs support them.
Implementation Checklist Before This Goes Live
The FAQ should match how your product actually tracks usage. If the product says usage is counted by workspace but the system only records account-level totals, customers will notice.
- Tag each AI request with useful identifiers such as site, license, workspace, user, feature, and action type.
- Separate successful billable actions from failed requests, retries, previews, and cached responses.
- Show current usage inside the plugin admin before users hit the limit.
- Warn users before a paid action starts when it may consume credits or trigger routed usage.
- Give admins controls for high-volume features, especially bulk generation and automation.
- Keep support macros aligned with the same wording used in the FAQ and pricing page.
- Link technical readers to ShareAI Documentation and product teams to the Builder Console.
Where ShareAI Fits
ShareAI is the AI marketplace and API layer behind routed usage. A Builder brings the plugin, CMS product, commerce app, or site automation workflow. ShareAI helps route inference traffic, track usage, handle customer payment for that usage, support the configured Builder margin, and pay the Builder monthly based on generated earnings.
This is especially useful when AI usage is valuable but uneven. One merchant may generate a few product descriptions. Another may rewrite an entire catalog. One agency may run a handful of client reports. Another may power recurring client workflows every day. The pricing language should let those usage differences show up clearly.
Teams planning model choice can also browse ShareAI Models before routing production traffic. For more implementation-focused articles, visit the ShareAI Developers category.
Start With One Honest Support Answer
You do not need to explain every token, provider, or pricing edge case in public copy. Start with one honest support answer: AI usage creates real routed inference traffic, and the product prices that usage separately so customers pay for what they actually use.
Then make the controls visible. Show the allowance. Show the top-up path. Show who pays. Show what the Builder earns from. Clear customer language makes AI usage feel like a normal product mechanic instead of a surprise charge.