Customer Portal
Customer Portal
Self-service, support and account management for customers.
A customer portal is the self-service surface an organization gives the people who buy from it. It covers account information and entitlements, support cases, documentation and product learning as one place customers can answer their own questions from.
- Example 01
- Account home
- Example 02
- Support and cases
- Example 03
- Knowledge and enablement
- Example 04
- Learning paths
- Example 05
- Billing and renewals
Key takeaways
What the ZINFI Customer Portal delivers
- See entitlement usage, open case age, and learning progress for every account
- Spot accounts drifting toward churn before a renewal conversation, not during it
- Step into a customer's own view to confirm exactly what they see and can do
- Check entitlements, contacts, and renewal dates without emailing an account manager
- Raise a support case and track it through to resolution in one place
- Find documentation and complete learning paths at their own pace
CUSTOMER PORTAL
Everything a customer needs, without opening a case.
A customer portal is the self-service surface an organization gives the people who buy from it. Account and entitlement information, support history, product documentation and learning paths sit together, so a customer can answer most of their own questions and escalate only what genuinely needs a person.
4 portal types. 1 architecture. Customer management is one of the three core pillars ZINFI URM was built around.
How each example works
Example 01
Confirm what the account is entitled to, in one look
Subscriptions, entitlements and account contacts in one place, scoped to the signed-in account. A customer administrator confirms exactly what's active and who's named on it, without emailing an account manager.
- Active entitlements, contacts, and plan details in one header strip
- Renewal date and plan tier shown alongside current usage
- Update named contacts directly, no request form needed
A customer never has to ask what they're entitled to — they can see it themselves.
zinfi.app · Customer · Account Home
Unified Revenue ManagementPlan
Enterprise
Renews 14 Mar
Licenses in use
248
of 300
Open cases
3
Named contacts
9
Entitlements
| Contact | Status |
|---|---|
| r.nunez@example.com | Active |
| j.okafor@example.com | Active |
| p.mensah@example.com | Active |
| s.iqbal@example.com | Pending |
Example 02
Raise a case and watch it move, without a phone call
Raise, track and resolve support requests with status visible at every step. A customer support contact submits an issue and sees exactly where it sits in resolution.
- Submit case, add attachment, and track status in one flow
- Priority, owner, and age shown on every open case
- Resolution history stays attached to the case permanently
A case never disappears into an inbox — its status is always visible to the person who raised it.
zinfi.app · Customer · Support
Unified Revenue ManagementOpen cases
3
Awaiting your reply
1
Median first response
3.4h
Resolved this quarter
27
| Subject |
|---|
| Single sign-on redirect loop |
| Export missing custom fields |
| Add seats to learning plan |
| Invoice address change |
Example 03
Find the answer before you'd think to open a case
Product documentation and how-to material organized by topic. An end customer searches for what they need and finishes the task without waiting on a reply.
- Search documentation, browse by topic, and save article in one view
- Article freshness and relevance shown on every result
- Related articles surface automatically from what's being read
Most questions get answered before a case ever needs to be raised.
zinfi.app · Customer · Knowledge Base
Unified Revenue ManagementTopics
- Getting started
- Account
- Data
- Integrations
- Security
Related articles surface as you read
Search documentation — "single sign-on"
| Article |
|---|
| Configure single sign-on with your IdP |
| Understanding entitlement usage |
| Export formats and field mapping |
| Adding and removing named contacts |
Example 04
See which learners are behind before it becomes a problem
Courses, progress and certification status for everyone at the account. A customer success manager sees who's stalled and intervenes before onboarding stalls with them.
- Course progress, certification status, and assign path in one view
- Completion percentage and last-activity date on every learner
- Stalled-learner filter surfaces who needs a nudge
Onboarding gaps get caught while there's still time to fix them, not at renewal.
zinfi.app · Customer · Learning
Unified Revenue ManagementEnrolled learners
46
Certified
19
41% of enrolled
Stalled 14+ days
7
Needs a nudge
Paths assigned
5
| Learner |
|---|
| R. Nunez |
| J. Okafor |
| P. Mensah |
| S. Iqbal |
Example 05
Know what's due before the invoice is a surprise
Invoices, renewal dates and plan changes in one reference view. A billing contact checks what's due and when the term ends without calling accounts receivable.
- Invoice history, renewal date, and change plan in one view
- Amount due and payment status on every invoice
- Plan-change requests submitted directly, no separate ticket
Nobody finds out about a renewal by way of a surprise invoice.
zinfi.app · Customer · Billing
Unified Revenue ManagementNext renewal
14 Mar
Auto-renew on
Term remaining
94 days
Open balance
1 invoice
Plan changes
2
This term
| Description |
|---|
| Annual platform subscription |
| Additional learning seats |
| Premium support add-on |
| Annual platform subscription |
WHAT THIS UNLOCKS
What Customer Portal unlocks for the program
A working customer self-service surface in one system — account and entitlement visibility, support case tracking, documentation, learning progress and billing — replacing the account-manager emails and scattered support tickets most customer programs still run on.
The examples above are illustrative — built to show the portal's core screens and how they work together, not a full walkthrough of every feature. For a detailed look at the platform, schedule a live demo.
Built on ZINFI URM
- Content
- Learning
Frequently asked questions
Straightforward answers about ZINFI's Customer Portal — how it's built, who uses it, and how it differs from handling customers over email and spreadsheets.
- What is a customer portal?
- A customer portal is the system a company gives the people who buy from it to manage their own account in one place. It typically covers subscriptions and entitlements, support cases, product documentation, learning paths, and billing and renewals. Rather than a customer emailing an account contact to ask what they are entitled to or when a term ends, they can see it directly. In ZINFI's architecture, a customer portal runs on the same Experience, Connectivity, Orchestration and Harness layers as every other portal type.
- Who is a customer portal built for?
- Two audiences use a customer portal day to day. An end customer — the person at the buying organization — logs in to check entitlements, raise and track support cases, find documentation, and work through learning material. A customer success manager uses the same portal, or an admin view of it, to see which accounts are engaging, where learners are behind, and which renewals or open cases need attention before they become problems.
- How does a customer portal fit into ZINFI's URM architecture?
- A customer portal is built entirely on ZINFI's URM architecture — it doesn't have its own separate stack. The Experience layer renders its screens; Connectivity carries data in and out through MCP, Zapier, or ZINFI's native connector; Orchestration holds the shared account, case and learning data; and the Harness governs what any automation or agent is allowed to do inside it. Nothing about a customer portal is bespoke at the infrastructure level — only the screens and the data model are specific to customers.
- What can a customer success manager do in a customer portal?
- A customer success manager uses a customer portal to see the health of the accounts they own: which entitlements are in use, which support cases are open and ageing, which learners have stalled, and which renewals are approaching. Rather than assembling that picture from separate support, billing and learning systems, they get one view scoped to their accounts and can decide where to intervene.
- What can an end customer do in a customer portal?
- An end customer uses a customer portal to serve themselves — confirming what the account is entitled to and who is named on it, raising a support case and tracking where it sits, finding the documentation needed to finish a task, and checking what is due before a renewal. It's the same portal a success manager works in, approached from the account side rather than the program side.
- How does a customer portal connect to other systems?
- A customer portal connects outward through the same three channels every ZINFI portal uses: Zapier for CRM, marketing, and finance systems most organizations already run; MCP for structured exchange with AI agents and tools; and ZINFI's own native connector for platform data. Which channel a given integration uses depends on what's on the other end, not on anything specific to customer portals.
- How is a customer portal different from handling customers over email and spreadsheets?
- When account details live in email threads and internal spreadsheets, a customer has to ask a person for information the organization already holds, and two internal teams can answer the same question differently. A customer portal replaces that with one live record the customer and the account team both read from, governed by the same Harness that applies across the rest of ZINFI's architecture, so entitlements, case status and renewal dates mean the same thing to everyone.
- Can a customer portal be customized for our organization?
- Yes — the screens, personas, and account-specific fields in a customer portal are the customizable layer. What doesn't change is the underlying architecture: every customer portal ZINFI builds still runs on the same Experience, Connectivity, Orchestration, and Harness foundation, which is what keeps a customized portal from becoming a one-off system nobody else can maintain.
- Is a customer portal AI-native?
- Yes, in the same sense the whole architecture is: agentic AI is built into the platform, but it operates inside the Harness, which governs what any agent is allowed to do before it acts. A customer portal doesn't bolt AI on top of a static system — the governance is structural, not an add-on.
- Is a customer portal part of ZINFI Unified Revenue Management (URM)?
- Yes. A customer portal is one of the portal types built on ZINFI's Unified Revenue Management (URM) architecture, alongside partner, sales, and alliance portals. ZINFI URM now runs four portal types on one architecture; partner, sales, and customer remain the three portals closest to URM's original definition, with the alliance portal extending the same architecture to brand-side relationships.
- How long does it take to stand up a customer portal?
- Because the Experience, Connectivity, Orchestration and Harness layers already exist, the work is configuration rather than construction — defining entitlement rules, support case types and what a customer can see versus escalate. Organizations typically start with one segment of accounts and one support queue, then widen scope once the first cohort is live, rather than migrating every customer at once.
- How much autonomy do the AI agents in a customer portal have?
- Exactly as much as you set. The autonomy ladder runs Foundation, Assist, Act and Autonomous, and each step is chosen by you rather than by the platform. At Foundation nothing acts on its own; at Assist an agent drafts and a person approves; at Act an agent completes bounded tasks inside the Harness; at Autonomous it runs an end-to-end flow within the same guardrails. Starting at Foundation is a legitimate place to run a program from.
See how this architecture handles your other portal types.
Every portal type in this showcase — partner, sales and customer — runs on the same foundation.
Browse all portal types