Skip to main content

SC Platform Rebilling & Markup Standard

Purpose​

Defines how Symphony Core rebills usage-based platform costs (calls, SMS, email, AI) to managed client sub-accounts, at what markup, and how every sub-account should be configured so pricing is consistent, profitable, and explainable. This is the policy layer; the concrete per-service numbers live in the companion SC Rebilling Rates Reference.

The platform is white-labeled GoHighLevel (GHL); this doc is internal-team, so GHL/LeadConnector/Twilio terms are used freely. Never carry them into client-facing docs — see the client usage-billing explainer template.

Scope​

  • Applies to: every managed client sub-account SC operates (Client Delivery).
  • Covers: the wallet + complimentary-credit model, the standard markup, which services are rebilled, what SC absorbs, the standard wallet configuration, and the procedure to standardize across sub-accounts.
  • Out of scope: the productized self-serve SaaS plans in 03-sales/pricing-strategy/v2/ (Starter/Growth/Professional), which assume a different (1.05×) markup and are a separate track — see §7 Exceptions.

1. The model (how usage billing works)​

Every sub-account has a wallet. Usage-based services deduct from it in real time. The wallet holds two buckets:

  • Complimentary credits — a monthly allowance SC grants the client (set in the SaaS Configurator). Separate from paid balance; rollover is disabled by default so they don't accumulate.
  • Balance — real money the client's card funds via auto-recharge when the wallet runs low.

GHL charges SC's agency wallet for the underlying usage; rebilling passes that cost (plus SC's markup) to the sub-account's wallet. When SaaS payment is configured the client sees an agency-branded (Symphony Core) charge — never Twilio/GHL.

Grounded in GHL's own model: Rebilling, Reselling & Wallets Explained, Wallet Auto-Recharge & Smart Adjustment, SaaS Wallet Credit Management.

2. Standard markup — 1.5×​

The Symphony Core standard markup is 1.5× (i.e. a 50% margin) on every rebillable usage service, for all managed client accounts. This is the canonical figure — it is what the live sub-accounts run today and supersedes any earlier "1.05×" or "no markup" figure for managed accounts (see §7).

Derivation rule, applied per service:

charged-to-customer = underlying cost × 1.5
profit = charged-to-customer − underlying cost (= cost × 0.5)

Actual per-service cost and resulting charged rates: SC Rebilling Rates Reference. Rates vary by region (Twilio) and by LLM/tokens (AI), so the numbers live there, not here.

3. Rebillable-service posture (standard = ALL on at 1.5×)​

Standard posture: every usage-based service is turned ON for rebilling at 1.5×. Leaving a service off means SC absorbs 100% of its cost the moment a client uses it — a silent margin leak (this is exactly what happened with Reviews AI on Rotary). Turn them all on so nothing leaks when a feature is later enabled.

Rebill ON at 1.5×:

  • Phone System — outbound/inbound calls (per minute) + SMS (per segment)
  • Email (LeadConnector) — per email
  • Conversation AI — per message
  • Voice AI — per minute
  • Content AI — per 1,000 words / per image
  • Reviews AI — per review response
  • Email Verification — per verification
  • Workflow — Premium Features — per execution
  • Workflow — External AI Models — per execution/token
  • WhatsApp — per Meta conversation rates

4. What SC absorbs (not rebilled)​

  • A2P 10DLC registration + monthly campaign fees — passthrough carrier/TCR fees; SC absorbs, not rebilled to the client. Track separately if the client count grows (per the pricing-assumptions open item).
  • Call transcription — nuance: on Twilio-provider phone the transcription charge is not rebilled; on LC Phone it can be. SC standard: absorb transcription unless a client's usage makes it material, then revisit.

5. Standard wallet configuration​

Every managed sub-account should be configured to this baseline (align existing accounts to it — see §6):

  • Complimentary credit / month — by plan tier: Starter $15 · Growth $25 · Professional / managed $50. (Rotary = $50.)
  • Rollover credits — OFF (credits reset monthly; don't accumulate).
  • Auto-recharge — ON with a positive threshold: recommended recharge $25 when balance falls below $10. Do not leave the threshold at $0 — recharging only after the wallet hits zero risks a mid-conversation service interruption. (Flag: several live accounts, incl. Rotary, are on $10 when < $0 — fix during the §6 audit.)

6. Standardization procedure​

Do not configure sub-accounts by hand one at a time. Standardize:

  1. Bulk Rebilling — Agency Dashboard → select sub-accounts → set per-service markups to 1.5× in one pass (Bulk Rebilling Setup). Use per-service sliders so every service (incl. Reviews AI) lands at 1.5×.
  2. SaaS Configurator defaults — set the complimentary-credit amount, rollover-off, and auto-recharge threshold per tier so new accounts inherit the standard automatically.
  3. Snapshot per tier — attach one snapshot per billing level so onboarding is consistent.
  4. Test on 1–2 accounts before a bulk apply.

Sub-account alignment audit checklist (run on every existing managed account; catches drift):

  • Markup = 1.5× on all rebillable services (no service left off / at 1.0×)
  • Complimentary credit matches the account's tier; rollover OFF
  • Auto-recharge threshold is positive (not $0)
  • A2P + transcription treatment matches §4
  • Client sees Symphony Core-branded charges (SaaS payment configured), never Twilio/GHL
  • The paid plan is bound to the working sub-account: saasMode is activated there, with the subscription and paying contact in planDetails. It is not setup_pending or not_activated, and not held on a separate "billing" shell sub-account. If it is held elsewhere, credits and rebilling never reach the account the client actually uses

7. Exceptions & separate tracks​

  • iBoost Online (first client) — signed at no markup (iboost-service-package-details.md Schedule A). Grandfathered; do not silently change a signed agreement. Revisit only at renewal.
  • Productized self-serve SaaS plans (03-sales/pricing-strategy/v2/, incl. the SPD template Schedule A) assume 1.05× and are not yet launched. They are a separate track; this standard does not rewrite them. Reconcile when those plans go live — flagged items to reconcile then: the 1.05× margin models, the $0.0079 vs live $0.0083 SMS base rate, and the faq-page-copy.md overage copy (1.1¢/2.8¢).

Revision History​

DateVersionChangeAuthor
2026-11-051.1§6 audit checklist: added the plan-binding check. The 2026-11-05 audit found most client plans unbound or held on billing shells, and no wallet auto-recharge in 2026.Symphony Core Systems Team
2026-07-031.0Initial standard. 1.5× canonical markup for managed accounts; all-services-on posture; standard wallet config; Bulk-Rebilling standardization + audit checklist; iBoost + productized-plan exceptions. Closes the sc-platform-rebilling-markup-standard.md action item.Symphony Core Systems Team