Portal Analytics
Measure how customers use your self-service portal — logins, activity, self-service actions and ticket deflection — so you can see exactly what the portal saves your team.
Overview
A customer portal is meant to let people help themselves. Without usage data you cannot tell whether it deflects tickets or just sits there.
Portal Analytics tracks logins, active users, the self-service actions people complete and the tickets they avoid raising — all tied to the account and contact, so the portal’s value is visible.
Explore Omnichannel Communication →- ✓ Logins & active users
- ✓ Pages & features used
- ✓ Self-service actions completed
- ✓ Ticket deflection
- ✓ Search terms with no result
- ✓ By account & user role
What Portal Analytics measures
Every signal on your own portal usage — described as what we capture, never as invented rates.
Logins & active users
See logins, active users and return visits by account.
Feature usage
Track which pages and features people actually use.
Self-service actions
Measure actions completed — pay, download, update, track.
Ticket deflection
See the tickets avoided because people self-served instead.
Failed searches
Find searches that returned nothing, so you fill the gap.
By account
Compare adoption and deflection across accounts and roles.
The signals behind self-service
Each one is captured against the account and contact using the portal.
- ✓ Logins, active users and return visits
- ✓ Which pages and features get used
- ✓ Self-service actions completed — pay, download, update, track
- ✓ Adoption by account and user role
- ✓ Tickets deflected versus raised from the portal
- ✓ Knowledge-base articles viewed and rated
- ✓ Searches that returned nothing
- ✓ Usage and deflection trend by account and date
Live in four steps
Enable the portal
Turn on the self-service portal for your accounts.
Every session logs
Logins, page views and actions attach to the account.
Usage & deflection roll up
Adoption, actions and deflection aggregate by account.
Fix the gaps
Close the content and feature gaps people hit.
See what the portal saves you
The signals that show whether self-service is actually reducing your ticket load.
Self-service actions
The actions people complete themselves instead of contacting you.
Ticket deflection
Tickets avoided because the answer or action was in the portal.
Content gaps
Failed searches and missing articles that still force a ticket.
How the agent works with Portal Analytics
The Flow-Cognition Agent runs a real loop on your data — grounded in your records, governed and logged.
Sense
Reads every login, page view, action and search in the portal.
Decide
Scores adoption, deflection and content gaps against your norms.
Act
Flags the unanswered searches and missing content to fix next — logged.
Five-tier model routing · field-level permissions · full audit trail. See the AI layer →
Where teams put it to work
Customer self-service
See which answers and actions keep customers out of the queue.
Partner & reseller portals
Track partner adoption and self-service activity.
Account & billing self-service
Measure invoice, payment and account actions people complete.
Questions, answered
Logins and active users, feature usage, self-service actions completed, ticket deflection and failed searches — by account and role.
No. It measures deflection on your own portal; any rate you see is from your data, not a benchmark.
By tracking self-service actions completed and tickets avoided against those still raised from the portal.
Yes. Searches that returned nothing are logged so you can fill the content gap.
The portal provides self-service; Portal Analytics measures how it is used and what it saves your team.
See what your portal saves you
Start free, or get a guided walkthrough — every login, action, search and deflected ticket, in one view.