# RevCent Subscription Renewals Overview for AI/MCP

AI/MCP-focused overview for Subscription Renewals in RevCent.

This document explains what Subscription Renewals are, why they matter, how they are created, how they connect to payment attempts, shipments, salvage recovery, AI/voice workflows, and how AI/MCP clients should retrieve and report on renewal data.

---

## Core Concept

A Subscription Renewal is an individual renewal event or renewal attempt for a RevCent Subscription.

In plain language:

```text
Subscription = the customer's recurring billing relationship
Subscription Profile = the renewal schedule/rules
Subscription Renewal = a specific renewal event/attempt generated from that subscription
```

A Subscription Renewal represents one occurrence of a subscription trying to renew.

It can connect to:

- customer,
- subscription,
- Subscription Profile,
- product,
- campaign,
- third-party shop,
- payment type,
- credit-card transactions,
- PayPal transactions,
- Offline Payments,
- shipments,
- tax,
- discounts,
- salvage transactions,
- pending refunds,
- chargebacks,
- fraud detections,
- AI threads,
- AI Assistants,
- API calls,
- metadata,
- billing dates.

Subscription Renewals are the measurable recurring billing events that make subscription businesses analyzable and recoverable.

---

## Related Overview Links

AI/MCP clients should use these related overview files for context:

| Overview | Link | Why It Matters |
|---|---|---|
| Subscription Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscription.md` | Explains how Subscriptions work, how they are created, lifecycle status, renewal billing, WooCommerce guidance, AI, voice, reporting, and recovery. |
| Subscription Profile Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscriptionProfile.md` | Explains how Subscription Profiles define renewal frequency, occurrence rules, overdue behavior, payment profile, and subscription-specific custom cycles. |
| Payment Profile Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewPaymentProfile.md` | Explains how Payment Profiles process subscription renewal payments. |
| Product Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewProduct.md` | Explains how Products configured with Subscription Profiles create Subscriptions and future renewals. |
| Product Sales Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewProductSale.md` | Explains line-item purchase context behind subscription creation and product-level metrics. |
| Sales Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSale.md` | Explains the original Sale that can spawn subscription and renewal-related commerce events. |
| Shipping Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewShipping.md` | Explains shipment creation, fulfillment, tracking, and shipment lifecycle for shippable renewal products. |
| Shipping Profile Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewShippingProfile.md` | Explains renewal shipping rate calculation for shippable subscription products. |
| Salvage Transaction Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSalvageTransaction.md` | Explains recovery opportunities from declined or partially declined renewal attempts. |
| Email Template Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewEmailTemplate.md` | Explains renewal-related customer and internal email automation. |
| AI Assistant Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewAIAssistant.md` | Explains event-driven and scheduled AI automation for renewal recovery, review, reporting, and support. |
| AI Voice Agent Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewAIVoiceAgent.md` | Explains inbound/outbound voice support and subscription renewal recovery. |
| Customer Portal Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomerPortal.md` | Explains customer self-service for payment updates and subscription support. |
| Shop Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewShop.md` | Explains WooCommerce/third-party shop context for subscriptions and renewals. |
| BigQueryRunQuery | `https://revcent.com/documentation/markdown/mcp/operation/BigQueryRunQuery.md` | Correct method for renewal metrics, reporting, aggregation, and data mining. |

---

## Related Operation Links

| Operation | Link | Purpose |
|---|---|---|
| `GetSubscriptionRenewals` | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptionRenewals.md` | Retrieve a bounded operational list of Subscription Renewals. Not for reporting/aggregation. |
| `GetSubscriptionRenewal` | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptionRenewal.md` | Retrieve one Subscription Renewal by ID. |
| `RenewSubscription` | `https://revcent.com/documentation/markdown/mcp/operation/RenewSubscription.md` | Manually renew a subscription only when there is explicit purpose to charge immediately. |
| `GetSubscription` | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscription.md` | Retrieve the parent Subscription. |
| `GetSubscriptions` | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptions.md` | Retrieve subscriptions operationally. Not for reporting. |
| `SearchSubscriptions` | `https://revcent.com/documentation/markdown/mcp/operation/SearchSubscriptions.md` | Search subscriptions manually or through automated/AI workflows before retrieving exact details. |
| `CreateSubscriptionProfile` | `https://revcent.com/documentation/markdown/mcp/operation/CreateSubscriptionProfile.md` | Create renewal schedules used by Subscriptions. |
| `EditSubscriptionProfile` | `https://revcent.com/documentation/markdown/mcp/operation/EditSubscriptionProfile.md` | Edit renewal schedule behavior carefully. |
| `ProcessSalvageTransaction` | `https://revcent.com/documentation/markdown/mcp/operation/ProcessSalvageTransaction.md` | Process a salvage transaction after eligibility review and wait period. |

---

## Why Subscription Renewals Matter

Subscription Renewals are where recurring revenue actually happens.

A Subscription can be active, but the business value comes from successful renewal events.

Subscription Renewals allow RevCent and ecommerce businesses to understand:

- renewal revenue,
- successful recurring billing,
- failed renewal attempts,
- overdue subscription behavior,
- payment recovery opportunities,
- product-level recurring revenue,
- recurring shipment creation,
- customer retention,
- subscription lifecycle health,
- churn risk,
- AI/voice recovery performance,
- recurring payment method performance,
- Subscription Profile effectiveness.

For ecommerce businesses, Subscription Renewals are the heartbeat of recurring revenue.

---

## How Subscription Renewals Are Created

RevCent creates Subscription Renewals from active Subscriptions according to the Subscription Profile.

Typical scheduled renewal flow:

```text
Subscription exists
    ↓
Subscription Profile defines renewal schedule
    ↓
Next renewal date arrives
    ↓
RevCent processes renewal internally
    ↓
Subscription Renewal is created
    ↓
Payment attempt occurs through the Payment Profile / payment context
    ↓
Related records may be created:
        transaction / PayPal transaction / Offline Payment
        shipment
        tax
        discount
        salvage transaction
        email/AI/voice events
```

RevCent automatically handles scheduled subscription renewal billing internally.

AI/MCP clients should not manually renew subscriptions just because they are due soon.

---

## Automatic Renewal Billing

RevCent is designed to handle automatic recurring billing.

The Subscription Profile defines when the renewal occurs.

The Payment Profile determines how the renewal payment is attempted.

Customer payment data stored in RevCent's PCI Level 1 environment allows RevCent to bill renewals without requiring the customer to re-enter card information for each cycle.

Conceptual model:

```text
Subscription Profile = when to renew
Payment Profile = how to attempt payment
Customer payment data = stored payment method for billing
Subscription Renewal = the actual renewal event/attempt
```

For ecommerce subscription businesses, this allows reliable recurring billing and reduces dependency on WooCommerce/WordPress subscription plugins.

---

## Manual Renewal

Manual renewal uses:

```text
RenewSubscription
```

Important:

```text
RevCent automatically processes subscription renewals internally.
RenewSubscription should only be used when there is explicit purpose to charge the customer immediately.
```

Valid manual renewal reasons:

- customer requests immediate renewal,
- customer wants early shipment/refill,
- support has confirmed immediate payment authorization,
- an approved recovery workflow intentionally charges now,
- an overdue subscription has been reviewed and manual recovery is appropriate.

Do not use manual renewal for:

- reporting,
- status checks,
- casual retry attempts,
- bulk renewal processing,
- replacing automatic renewal behavior,
- charging a customer without explicit authorization.

Manual renewal can affect the next renewal date because the next renewal is set according to the Subscription Profile duration setting in combination with the manual renewal date.

---

## Relationship to Subscription Profiles

Every renewal is shaped by the parent Subscription's Subscription Profile.

A Subscription Profile can define:

- frequency type,
- frequency details,
- occurrence rules,
- overdue limit,
- Payment Profile,
- optional Shipping Profile override,
- advanced preferred-gateway behavior,
- whether the profile is subscription-specific/custom.

Examples:

```text
Every 30 days
Every 2 weeks
Monthly
Quarterly
1st day of the month
Custom 6-week customer-specific cycle
```

If a customer has a custom renewal cycle, use a subscription-specific Subscription Profile.

Do not edit a globally used Subscription Profile for one customer's custom cycle, because that can affect all associated subscriptions.

---

## Relationship to Products

Subscription Renewals relate back to the product being renewed.

The renewal response can include product context such as:

- product ID,
- product name,
- quantity,
- price,
- whether the product is a subscription product,
- whether the product is a trial product,
- internal ID,
- SKU.

This is important for:

- product-level recurring revenue reporting,
- subscription product performance,
- Product Group analysis,
- recurring shipment workflows,
- Email Template filters,
- AI Assistant filters,
- AI Voice Agent context,
- customer support.

---

## Relationship to Customers

Subscription Renewals include customer context.

Renewal records can include customer information such as:

- customer ID,
- first name,
- last name,
- email,
- phone,
- address,
- metadata,
- enabled/blocked state.

This makes renewals useful for:

- support review,
- payment recovery,
- Email Templates,
- AI Assistant reasoning,
- AI Voice Agent calls,
- Customer Portal guidance,
- BigQuery reporting by customer segment.

Important:

```text
Use GetSubscriptionRenewal or GetSubscription for operational review.
Use BigQueryRunQuery for metrics and reporting.
```

---

## Relationship to Shops / WooCommerce

Subscription Renewals can include third-party shop context.

For WooCommerce subscriptions, this means RevCent can report and act on renewals associated with a specific connected shop.

Correct WooCommerce model:

```text
WooCommerce = storefront
RevCent = subscription billing backend
```

WooCommerce should not handle subscription billing when RevCent is connected.

RevCent should own:

- subscription creation,
- renewal billing,
- renewal payment recovery,
- recurring shipments,
- subscription emails,
- customer support context,
- AI/voice recovery,
- reporting.

---

## Payment Types on Subscription Renewals

Renewal records can include payment type information.

Known payment types include:

- Credit Card,
- PayPal,
- Offline Payment,
- Check.

Related payment records may include:

- credit-card transactions,
- PayPal transactions,
- Offline Payments,
- check records.

This matters because recovery/refund/support behavior can differ depending on payment type.

Credit-card renewals are especially important because RevCent stores customer payment data in a PCI Level 1 environment and can process renewals automatically through Payment Profiles.

---

## Subscription Renewal Amount Fields

Subscription Renewals include multiple amount fields so RevCent can represent the real economics of a renewal.

Important amount fields can include:

| Field | Meaning |
|---|---|
| `amount` | Subscription renewal amount. |
| `amount_original_total` | Total calculated amount when first created, before discounts/refunds. |
| `amount_total` | Current total after refunds and discounts. |
| `amount_gross` | Money actually transacted, payments minus refunded payments. |
| `amount_net` | Gross amount minus payment processor fees. |
| `amount_fees` | Calculated processor fees. |
| `amount_captured` | Captured but not settled amount. |
| `amount_settled` | Settled amount. |
| `amount_remaining` | Amount remaining to be processed, including salvage/trial-related remaining amounts where applicable. |
| `amount_refunded` | Refunded amount. |

These fields help ecommerce businesses understand more than whether a renewal succeeded.

They support analysis of:

- gross renewal revenue,
- net renewal revenue,
- processor fees,
- refunds,
- remaining recoverable revenue,
- settlement/capture behavior,
- salvage recovery.

---

## Billing State

Renewal records can include billing context, such as:

- next renewal date,
- last renewal date,
- last renewal ID,
- whether the renewal/subscription context is overdue.

This connects the renewal event back to the ongoing subscription lifecycle.

Useful operational questions:

```text
When did this subscription last renew?
When is the next renewal?
Is the renewal/subscription overdue?
What was the last renewal ID?
```

For metrics, use BigQuery.

---

## Related Records on Subscription Renewals

A Subscription Renewal can link to many related records.

Related IDs may include:

| Related Record | Why It Matters |
|---|---|
| Sales | Commerce/order records connected to the renewal. |
| Product Sales | Product line items connected to renewal activity. |
| Shipping | Recurring shipment records for shippable subscription products. |
| Tax | Tax records attached to the renewal. |
| Discounts | Discounts applied to the renewal. |
| Trials | Trial records where applicable. |
| Subscriptions | Parent or related subscription records. |
| Subscription Renewals | Related renewal records. |
| Invoices | Invoice records where applicable. |
| Transactions | Credit-card transaction records. |
| PayPal Transactions | PayPal payment records. |
| Offline Payments | Alternate/offline payment records. |
| Check Directs | Check payment records. |
| Salvage Transactions | Recovery opportunities from declined/partial renewal attempts. |
| Pending Refunds | Refund workflow records. |
| Chargebacks | Dispute/chargeback records. |
| Fraud Detections | Fraud/risk records. |
| AI Threads | AI workflow execution records. |
| AI Assistants | AI automations related to the renewal. |
| API Calls | API activity related to the renewal. |

This makes Subscription Renewals a powerful hub for operational review and business analysis.

---

## Shippable Subscription Renewals

If the subscription product is shippable, a renewal may create shipment-related records.

Examples:

- monthly supplement refill,
- coffee subscription,
- subscription box,
- skincare replenishment,
- pet product refill,
- recurring physical product.

Important rule:

```text
Initial WooCommerce Sale shipping may come from WooCommerce checkout.
Subscription renewal shipping must be calculated by RevCent using Shipping Profiles.
```

Shippable subscription products should have:

- Product marked shippable,
- Fulfillment Account,
- Shipping Profiles,
- correct renewal shipping settings,
- shipment Email Templates,
- fulfillment/tracking workflows.

If shipping fails or is misconfigured, the renewal may succeed financially while fulfillment still needs operational attention.

AI Assistants and AI Voice Agents can support shipment status and recurring fulfillment questions.

---

## Failed Renewals and Overdue State

A failed renewal is a major revenue recovery opportunity.

When a renewal fails, the Subscription may become overdue or have overdue renewal context.

Failed renewal workflows can involve:

- Email Templates,
- Customer Portal payment update,
- AI Assistant review,
- AI Voice Agent outbound recovery,
- manual support,
- salvage transaction creation,
- salvage recovery after a wait period,
- suspension after overdue limit is reached.

Do not treat failed renewals as simple failures.

Treat them as structured recovery opportunities.

---

## Salvage Transactions From Subscription Renewals

Declined subscription renewals can create salvage transactions.

A salvage transaction represents recoverable revenue from a failed or partially declined payment attempt.

For subscription renewals, salvage transactions are important because:

- subscription revenue is recurring,
- failed renewals reduce lifetime value,
- customer funds may become available later,
- some decline reasons are recoverable,
- some decline reasons should not be retried,
- AI can evaluate recovery opportunity,
- voice agents can help customers update payment method,
- recovery outcomes can be measured.

Recommended salvage recovery workflow:

```text
Subscription renewal fails
    ↓
Salvage transaction is created where applicable
    ↓
AI Assistant triggered by salvage_transaction.created
    ↓
Assistant reviews subscription, renewal, customer, amount, and decline reason
    ↓
Assistant waits X days if appropriate
    ↓
Assistant chooses:
        ProcessSalvageTransaction
        Email Template
        AI Voice Agent
        Function
        note / metadata
        skip unrecoverable case
```

Important:

```text
Do not process every salvage transaction immediately.
Review decline reason and recoverability first.
```

Avoid retrying cards that are invalid, stolen, closed, restricted, fraud-related, or otherwise unlikely to recover.

---

## Email Templates for Subscription Renewals

Email Templates are critical for subscription renewal communication.

Common renewal email workflows:

| Email Workflow | Purpose |
|---|---|
| Renewal upcoming | Notify customer before renewal. |
| Renewal success | Confirm successful renewal/payment. |
| Renewal failed | Tell customer payment failed and provide recovery path. |
| Overdue renewal notice | Encourage payment update before suspension. |
| Payment update reminder | Send Customer Portal/payment update link. |
| Shipment created | Notify that recurring shipment is being prepared. |
| Shipment shipped | Send recurring shipment tracking. |
| Internal high-value failed renewal alert | Notify retention/support team. |
| Cancellation/suspension notice | Explain lifecycle change. |

Best practice:

```text
Use RevCent Email Templates for subscription renewal emails instead of WooCommerce emails.
```

RevCent has the authoritative renewal, payment, product, customer, and shipment context.

---

## AI Assistants for Subscription Renewals

AI Assistants can monitor and automate renewal workflows.

Useful AI Assistant renewal workflows:

- review failed renewals,
- classify recoverability,
- analyze decline reason,
- monitor overdue renewals,
- review salvage transactions,
- trigger recovery emails,
- trigger AI Voice Agents,
- create AI Memos for high-value failed renewals,
- create notes/metadata,
- run scheduled renewal performance reports,
- detect fulfillment exceptions for renewal shipments,
- summarize renewal history for support.

Example:

```text
subscription_renewal.updated.failed
    ↓
AI Assistant waits 2 days
    ↓
Assistant reviews subscription, customer, product, amount, and decline reason
    ↓
Assistant checks whether salvage transaction exists
    ↓
Assistant branches:
        recoverable → email / voice / salvage recovery
        hard decline → skip retry and create note
        high value → create AI Memo or trigger human follow-up
```

AI Assistants should use filters and max-runs-per-item to prevent loops and reduce cost.

---

## AI Voice Agents for Subscription Renewals

AI Voice Agents can help with both inbound support and outbound recovery.

Inbound use cases:

- customer asks why renewal failed,
- customer asks when next renewal is,
- customer asks to update payment method,
- customer asks about renewal shipment tracking,
- customer wants to pause/cancel/restart,
- customer wants a custom renewal cycle.

Outbound use cases:

- failed renewal recovery,
- overdue subscription recovery,
- payment update calls,
- high-value renewal recovery,
- trial-to-subscription conversion support,
- customer winback/retention,
- salvage transaction recovery after AI review.

Best practice:

```text
Use AI Assistants to qualify the recovery opportunity.
Use AI Voice Agents for the live customer conversation.
```

Do not call every failed-renewal customer. Filter for:

- recoverable decline reasons,
- contact eligibility,
- customer value,
- phone availability,
- opt-out status,
- time window,
- prior call attempts,
- fraud/risk concerns.

---

## Customer Portal and Payment Updates

The Customer Portal can reduce renewal failure friction.

Customers can use the portal to:

- review subscription status,
- update payment methods,
- view account context,
- review renewal/shipment history where available,
- reduce support tickets,
- continue or recover subscription relationships.

Email Templates and Voice Agents should often direct customers to the Customer Portal for safe self-service payment updates.

---

## Operational Retrieval: GetSubscriptionRenewals

`GetSubscriptionRenewals` returns a bounded list of previously created Subscription Renewals.

Input includes:

| Field | Required | Purpose |
|---|---:|---|
| `date_start` | Yes | Start timestamp in Unix seconds. |
| `date_end` | Yes | End timestamp in Unix seconds. |
| `limit` | Yes | Number of records to return. Limit is 1 to 25; default is 25. |
| `page` | Yes | Pagination page. |
| `campaign_filter` | No | Filter by Campaign IDs. |
| `currency_filter` | No | Filter by ISO 4217 currency codes. |
| `shop_filter` | No | Filter by User Shop IDs. |
| `metadata_filter` | No | Filter by metadata name/value pairs. |
| `customer_id` | No | Filter to items related to a specific Customer ID. |

Use `GetSubscriptionRenewals` for bounded operational retrieval, such as reviewing recent renewals for a known customer/date range.

Do not use it for:

- reporting,
- aggregation,
- counting,
- metrics,
- data mining,
- bulk export,
- document property search.

Use BigQueryRunQuery for those tasks.

---

## Operational Retrieval: GetSubscriptionRenewal

`GetSubscriptionRenewal` retrieves one Subscription Renewal by ID.

Input:

| Field | Required | Purpose |
|---|---:|---|
| `subscription_renewal_id` | Yes | 20-character Subscription Renewal ID. |

Use this operation when:

- the renewal ID is known,
- support needs exact renewal details,
- AI needs to inspect a specific renewal,
- Voice Agent needs context for a customer conversation,
- an automation needs related records for one renewal.

Example:

```json
{
  "subscription_renewal_id": "RRRRRRRRRRRRRRRRRRRR"
}
```

---

## Reporting and Metrics

Use:

```text
BigQueryRunQuery
```

for all Subscription Renewal reporting and metrics.

Examples of renewal reports:

- renewal revenue by day/week/month,
- renewal success rate,
- failed renewal rate,
- renewal revenue by Subscription Profile,
- renewal revenue by Product,
- renewal revenue by Product Group,
- renewal revenue by WooCommerce shop,
- renewal revenue by campaign,
- overdue renewals,
- salvage recovery from failed renewals,
- renewal refund rate,
- renewal chargeback rate,
- renewal payment type mix,
- renewal performance by Payment Profile,
- renewal shipment issues,
- AI Assistant recovery performance,
- AI Voice Agent recovery performance,
- Customer Portal payment update impact,
- renewal cohort retention,
- renewal LTV.

Do not use operational endpoints as reporting substitutes.

Correct rule:

```text
One specific renewal = GetSubscriptionRenewal
Bounded operational list = GetSubscriptionRenewals
Metrics/reporting/aggregation = BigQueryRunQuery
```

---

## Example BigQuery Report Ideas

### Renewal Revenue by Day

```sql
SELECT
  DATE(TIMESTAMP_SECONDS(created_date_unix)) AS renewal_day,
  iso_currency,
  COUNT(*) AS renewal_count,
  SUM(amount_total) AS renewal_amount
FROM `revcent.user.subscription_renewal`
WHERE created_date_unix >= UNIX_SECONDS(TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 90 DAY))
GROUP BY renewal_day, iso_currency
ORDER BY renewal_day DESC
```

### Failed / Overdue Renewal Candidates

```sql
SELECT
  id AS subscription_renewal_id,
  subscription_id,
  customer.email AS customer_email,
  product.name AS product_name,
  amount,
  iso_currency,
  is_overdue,
  billing.next_renewal_date_unix
FROM `revcent.user.subscription_renewal`
WHERE is_overdue = TRUE
ORDER BY amount DESC
LIMIT 250
```

### Renewal Revenue by Subscription Profile

```sql
SELECT
  subscription_profile.id AS subscription_profile_id,
  subscription_profile.name AS subscription_profile_name,
  COUNT(*) AS renewal_count,
  SUM(amount_total) AS renewal_amount
FROM `revcent.user.subscription_renewal`
GROUP BY subscription_profile_id, subscription_profile_name
ORDER BY renewal_amount DESC
```

Before running production queries, use `GetBigQueryTables` to confirm exact table and column names.

---

## AI/MCP Best Practices

1. Treat Subscription Renewals as recurring billing events, not subscriptions themselves.
2. Use `GetSubscriptionRenewal` for one known renewal.
3. Use `GetSubscriptionRenewals` only for bounded operational retrieval.
4. Use `BigQueryRunQuery` for reporting, aggregation, and metrics.
5. Do not manually renew subscriptions unless immediate charging is explicitly intended.
6. Review failed renewal context before retrying or calling customers.
7. Use salvage transaction workflows for recoverable failed renewal revenue.
8. Use Email Templates for upcoming, success, failed, and overdue renewal communications.
9. Use AI Assistants to classify failed renewals and route recovery actions.
10. Use AI Voice Agents for inbound support and outbound renewal recovery.
11. Use Customer Portal for payment updates.
12. Configure Shipping Profiles and Fulfillment Accounts for shippable renewal products.
13. For WooCommerce, use RevCent as the subscription billing backend.
14. Avoid using WooCommerce subscription plugins for renewal billing when RevCent is connected.

---

## Common Mistakes to Avoid

Do not:

- confuse a Subscription Renewal with the parent Subscription,
- use `GetSubscriptionRenewals` for metrics/reporting,
- manually renew subscriptions that RevCent will automatically renew,
- retry failed renewals without reviewing decline reason,
- process salvage transactions immediately without eligibility review,
- call every overdue customer without filters,
- ignore shippable renewal fulfillment,
- rely on WooCommerce subscription billing instead of RevCent,
- ignore Subscription Profile settings when analyzing renewal behavior,
- edit global Subscription Profiles for one customer's custom cycle,
- ignore Email Templates and Customer Portal for recovery,
- fail to measure renewal performance with BigQuery.

---

## AI/MCP Decision Guide

| User Intent | Correct Action |
|---|---|
| Explain renewal concept | Describe Subscription Renewal as one renewal event/attempt for a Subscription. |
| Retrieve one renewal | Use `GetSubscriptionRenewal`. |
| Retrieve recent renewals operationally | Use `GetSubscriptionRenewals` with date range, limit, page, and filters. |
| Report renewal revenue or failure rates | Use `BigQueryRunQuery`. |
| Analyze a failed renewal | Retrieve renewal, subscription, customer, payment, and salvage context. |
| Recover failed renewal | Use Email Templates, Customer Portal, AI Assistant, AI Voice Agent, and salvage workflow where appropriate. |
| Customer asks to renew immediately | Use `RenewSubscription` only with explicit charge authorization. |
| Customer asks about next renewal | Use `GetSubscription` or `GetSubscriptionRenewal` depending on context. |
| Renewal created shipment issue | Retrieve shipment with `GetShipment` and use Shipping overview guidance. |
| Renewal created salvage transaction | Retrieve salvage transaction and review before processing recovery. |

---

## Final AI/MCP Instruction

Subscription Renewals are the individual renewal events/attempts generated from RevCent Subscriptions.

They are created automatically by RevCent when a subscription reaches its renewal schedule according to the Subscription Profile. RevCent handles scheduled renewal billing internally using the subscription's payment context and Payment Profile. Manual renewal should only be used when the user explicitly wants to charge the customer immediately.

Use `GetSubscriptionRenewal` for a specific renewal and `GetSubscriptionRenewals` for bounded operational retrieval. Never use `GetSubscriptionRenewals` for reporting, aggregation, metrics, data mining, or bulk retrieval. Use `BigQueryRunQuery` for renewal reporting and business analysis.

For failed or overdue renewals, use RevCent's recovery stack: Email Templates, Customer Portal, salvage transactions, AI Assistants, AI Voice Agents, Functions, and BigQuery analysis. For WooCommerce businesses, RevCent should own subscription renewal billing instead of WordPress/WooCommerce subscription plugins.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.