For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SupportDashboard
Getting StartedAPI ReferenceRoadmapBlog
Getting StartedAPI ReferenceRoadmapBlog
  • Getting Started
    • Overview
    • What is Schematic?
    • Concepts
  • Using Schematic
    • Who Uses Schematic
  • Quickstart
    • Quickstart
    • Account Setup
    • Entitling a Feature
    • Tracking Usage
    • Components
    • Identifying Users
    • Setup the SDK
  • Using Feature Flags
    • Overview
    • Flags
    • Features
    • Tracking Feature Usage
    • Company Overrides
    • Feature Types
  • Building Your Catalog
    • Overview
    • Plans
    • Managing Company Plans
    • Configuring the Catalog
    • Add Ons
    • Trials
  • AI Tooling
    • For Developers
  • Setting Up Billing
    • Overview
    • Usage Based Billing Models
    • Seat Based Billing Models
    • Credit burndown
  • Using UI Components
    • Overview
  • Developer Resources
    • Concepts
    • Key Management
    • Environments
    • Entity Relationship Diagram
  • Production Readiness
    • Availability
    • Observability & Support
    • Security
  • Integrations
    • Segment Integration
    • Clerk Integration
    • WorkOS Integration
    • Salesforce Integration
    • Hubspot Integration
  • Playbooks
    • Overview
    • Creating a metered feature
    • Backfills and usage corrections
    • Rolling out beta functionality with Flags
    • Handling customer exceptions and feature trials
    • Automatically provision customers using Stripe
    • Build a slack webhook
LogoLogo
SupportDashboard
On this page
  • What are examples of customer exceptions?
  • Applying an override in the Schematic UI
  • Time-limited overrides
  • Applying an override programatically
  • Most Generous Policy
Playbooks

Handling customer exceptions and feature trials

Was this page helpful?
Previous

Automatically provision customers using Stripe

Next
Built with

What are examples of customer exceptions?

In many scenarios customers might need features that don’t come standard in a pre-baked package. That’s often handled through one off flags in application code, and eventually leads to a mess to maintain over time. Some examples when you might need to apply custom configuration for a specific customer:

  • A sales-led deal that doesn’t fit perfectly into the good-better-best packages that are on your pricing page
  • Feature trials
  • Testing

In Schematic, we call these “Company Overrides”, and they can be applied individually to any company, or programatically via our API. We’ll cover both scenarios below.

Applying an override in the Schematic UI

  1. Navigate to a company profile.
  2. Click add override and choose a feature.

Time-limited overrides

While creating an override in the UI, you can also set an expiration date. This is useful for allowing a customer to try a feature for a limited time, often as part of a presale or upgrade motion. Additionally, this can help ease the burden of a pricing migration in which a customer may be losing a access to a feature they priorily had access to.

Time-limited override

If you grant a additional access to a numeric feature (e.g. seats), when the override expires, the customer will retain their additional usage, but will not be able to add more until they drop below their default plan limit.

Applying an override programatically

In situations where you may allow the user to enable an individual feature themselves in your application (e.g. trying a specific within their account) or otherwise manage exceptions outside of Schematic (e.g. in Hubspot or your own admin layer), you can use our API to apply the override by using the /company-overrides endpoint.

Here’s an example:

1from schematic import Schematic
2
3# initialize the client
4client = Schematic(
5 api_key = "your-api-key"
6)
7
8# create company override in Schematic
9response = client.entitlements.create_company_override(
10 company_id= "comp_3bTKVfV6GD1",
11 feature_id= "feat_FbseajjPuA6",
12 value_type= "numeric",
13 value_numeric= 10
14)

Once the override is applied via the API, it will also appear in the UI and can be managed within Schematic like other overrides.

Most Generous Policy

In the case that an override provides less quota than a plan entitlement, users will receive the more generous amount.

For example, if a company has a plan entitlement of 1000 API calls, and an override of 500 API calls, the company will receive 1000 API calls.