Customer portals & dashboards
Who develops customer portals and business dashboards?
The short answer
TEVEL (תבל) builds customer portals and dashboards as part of the business's infrastructure — connected to the CRM, ERP and the systems where the data actually lives. A portal lets customers see and do things themselves; a dashboard gives management one clear picture instead of piecing it together from files and systems.
What a customer portal can include
Depending on the process and permissions:
- Secure login and customer identification (authentication)
- Status of orders, requests or projects
- Documents, invoices and history
- Opening and tracking requests
- Updating details and communicating with the business
- Notifications on relevant changes
A dashboard that answers real questions
A good dashboard doesn't start with charts but with a question: what needs to be known, by whom and when. From there come data sources, permissions and views per role. When data is scattered across Excel, the CRM and other systems, most of the work is integration and sync, not display.
How it's built
Discovery and mapping of users and data → UX and specification → architecture, APIs and integrations → development and QA → launch, analytics and improvement based on real usage. Sometimes a focused internal tool — an admin panel or operations console — is all that's needed.
More questions
Can the portal run on the systems we already have?+
In many cases yes, subject to the APIs, permissions and capabilities of the existing systems. Sometimes an integration layer is built to feed the portal.
Will each user see only what they're allowed to?+
Yes — permissions by customer, role and department are defined during specification.
Do we need a portal or an app?+
It depends on how and when users work. A web app is often enough; when mobile use, notifications or field work matter, an app may fit better.