Connections
Connections Overview
Connections define how organizations within Revampd interact with one another — including communication, billing, credits, payouts, and invoices.
Each connection represents a direct relationship between two organizations. This structure allows Revampd to keep financial activity, permissions, and support channels clearly separated and traceable across your network of partners, sub-organizations, and clients.
What a Connection Does
Every connection includes:
Communication
Enables shared tickets and collaboration between two organizations.
Billing
Manages invoices, subscriptions, and add-ons specific to that relationship. Each connection maintains its own billing history.
Credits and Wallets
Each connection has its own wallet balance, where credits and affiliate payouts are stored. Credits in one connection cannot be used in another.
Payouts
Allows eligible organizations (such as Partners) to receive or credit earnings generated through their connected Sub-Orgs.
Invoices
Displays all charges, payments, and credits that apply to that specific connection.
Ownership and Roles
Determines who controls billing, subscriptions, and support visibility within the relationship.
Types of Connections
Revampd supports several types of organization-to-organization connections. Each type defines how billing and communication flow between the two sides.
Partner → Sub-Org
Used when a Partner manages one or more Sub-Organizations. The Partner handles billing, support, and plan assignments, while the Sub-Org can:
View its current plan
Approve or reject plan or add-on requests
Submit and manage support tickets
Review invoices tied to that connection
Partner ↔ Revampd
Partners have a direct connection with Revampd for managing their own subscription and payouts. This connection includes:
The Partner’s active Revampd plan and add-ons
Support tickets and billing history
A wallet for credits and payouts
The ability to credit, withdraw, or split payouts earned from Sub-Org billing
All credits and payouts in this connection apply only to invoices issued by Revampd to the Partner.
Sub-Org ↔ Revampd
Sub-Organizations also have a direct connection to Revampd for platform-level services such as phone numbers or in-app add-ons. Their main subscription remains managed by their Partner, but Revampd handles billing for in-platform items.
Credits and affiliate payouts in this connection can only be applied to Revampd invoices and cannot offset Partner invoices.
Self-Serve ↔ Revampd
Used when an organization signs up for Revampd directly, without a Partner. This connection includes:
Subscription management
Add-ons and invoices
Tickets and support history
Wallet and affiliate payouts
Self-Serve organizations do not receive Partner payouts — only affiliate earnings credited to their own wallet.
Wallet and Credit Rules
Each connection has its own wallet. Credits, affiliate payouts, or adjustments stay within that specific relationship and cannot be moved between connections.
Examples:
A Partner’s wallet credits can offset invoices from Revampd but not invoices from Sub-Orgs.
A Sub-Org’s wallet credits can only be used for Revampd-issued items such as phone numbers.
A Self-Serve organization’s affiliate credits can only be used toward its own Revampd invoices.
This design ensures billing integrity, compliance, and transparency across all relationships.
Tickets and Support Visibility
Connections also determine who can view and respond to shared support tickets.
When a Sub-Org opens a ticket, both the Partner and Revampd (if relevant) can view updates.
Partners can assign internal support owners or escalate tickets to Revampd.
Tickets can be filtered by status, priority, assigned user, or affected organization.
This structure ensures accountability and visibility across all connected entities.
Why Connections Matter
Managing all relationships through connections allows Revampd to provide:
Transparency — Every transaction, payout, and credit is tied to a specific relationship.
Control — Organizations determine how billing and support are managed within each connection.
Scalability — Partners can manage multiple Sub-Orgs, each with distinct billing and credit settings.
Compliance — All financial and communication activity remains auditable and isolated by connection.
In Summary
Connections are the foundation of Revampd’s ecosystem. They define who pays whom, where credits flow, how support is managed, and how every financial interaction between organizations is tracked and controlled.
Last updated