Kelir
Feature · Admin portal

Run the system from a browser.

Every multi-user Kelir setting lives in the web admin portal at app.kelir.io. User management, eSIM assignment per user, visual IVR builder with phantom-call testing, hunt-group configuration, per-department routing, recording downloads, billing, role-based access. Audit log on Team Pro tracks every admin action. Built for the office manager who runs the system from a desktop while the team takes calls on their phones.

Available on Team StarterAvailable on Team Pro
What it is

Admin portal on Kelir.

The Kelir admin portal at app.kelir.io is the web surface for managing a multi-user Kelir account. It's where the office manager, IT lead, or operations person configures everything that affects more than one user — user assignments, routing rules, hunt groups, IVR menus, departments, working hours, recording policies, billing, and (on Team Pro) the audit log of who-changed-what.

The split between "mobile app" and "admin portal" is intentional. Day-to-day team members do their work on their phones — calls ring on their cellular eSIM lines, they answer on the native dialer, they read voicemail transcripts in their email, they manage their personal DND from the Kelir mobile app. They rarely need the portal. The portal is for the admin role — the person who configures how calls route across the team.

Twelve primary surfaces on the portal: Dashboard (org-wide call activity), Calls (CDR view across users), Messages (team SMS history), Voicemail (per-user and shared department voicemails), Team (user management — add, remove, suspend), Routing (IVR builder + hunt groups + working hours), Analytics (volume, missed-rate, peak hours, on Team Pro: per-department breakdowns), Recordings (download, retention controls), Settings (organization-wide policies), Billing (invoices, seat changes, payment method), Departments (per-department configuration), Numbers (port status, number assignment, additional numbers).

Role-based access controls the surface. Three roles: admin (full access), member (own user data only), and billing (invoices and payment method only). Audit log on Team Pro records every admin action with actor, timestamp, prior state, and new state — exportable for compliance reviews.

RingCentral, Dialpad, 8x8, Vonage Business, and Nextiva all ship a comparable admin web app. Functionally similar surfaces — IVR builder, hunt-group config, user management. Differences are: Kelir's portal is a control panel for a system that runs primarily on cellular eSIM lines, not a softphone-app management surface. "Continue on Web" deep links from the mobile app open the relevant portal page directly — useful when an admin starts setup on phone and finishes on desktop. The visual IVR builder includes a phantom-call test tool to walk through every menu option before activating, with versioned configs and one-click rollback.

How to configure

Setup walkthrough.

Configured from Admin portal at app.kelir.io. The setup below assumes a working Kelir account and an active eSIM.

  1. 1

    Sign in at app.kelir.io with your admin credentials.

  2. 2

    Dashboard: see at-a-glance org-wide call volume, missed-rate, peak hours.

  3. 3

    Team → add a user: enter name, email, role; the user gets an email invite with a magic-link signup; they install the eSIM on their phone in <5 minutes.

  4. 4

    Routing → New hunt group: pick distribution strategy, add members, set ring timeouts and catcher voicemail.

  5. 5

    Routing → New IVR: drag-and-drop tree builder, type or upload greetings, configure each option's destination, run phantom-call tests before activating.

  6. 6

    Departments → New department: assign a number, add members, set working hours and routing.

  7. 7

    Recordings → set retention policy (per user or company-wide), download recordings as MP3, manage retention bounds.

  8. 8

    Settings → role-based access: edit which users have admin / member / billing roles.

  9. 9

    Billing: see itemized seat costs, change payment method, switch monthly/annual cycle, download invoices.

  10. 10

    Audit log (Team Pro): filter by actor, time range, action type. Export CSV for compliance.

Use cases

Where admin portal earns its keep.

Office manager runs the system

Office manager at a 12-person firm runs the entire phone system from a desktop. Adds new users, configures hunt groups, sets holiday hours, downloads recordings for QA. Team takes calls on their phones; manager handles the routing.

IT-led setup for a new office

IT lead spins up a new department for a satellite office. Assigns a new number, ports in 4 existing user numbers, configures the new working-hours schedule, sets up the office's hunt group. Done from the portal in 30 minutes.

Compliance review trail

Audit log on Team Pro shows every IVR change, every recording download, every user suspension. Compliance officer reviews monthly, exports CSV for the audit binder. Required for regulated workflows.

"Continue on Web" deep links

Admin starts editing the sales hunt group on their phone in the Kelir mobile app, hits "Continue on Web" — the portal opens directly to the sales hunt-group config page on the desktop. Drag-and-drop tree editing is easier on a screen with a mouse.

Quarterly seat reconciliation

Operations person reviews seat usage quarterly. Removes seats for staff who left; adds seats for new hires. Pro-rated changes appear on the next invoice. Done in 10 minutes from the portal.

vs softphone UCaaS

The same feature.A real cellular line.

Admin portals are universal in UCaaS. The differences are: what the portal manages (cellular eSIM lines vs softphone accounts), how the configuration surface feels, and what's gated to which plan tier.

  • Admin portal manages cellular eSIM provisioning and reset — push a fresh eSIM to a user, transfer between devices, reset on lost-phone. Softphone competitors manage softphone-account credentials and device pairings instead.
  • Visual IVR builder includes phantom-call testing — walk through every menu option before activating, no live-customer experimentation.
  • Versioned config with one-click rollback for routing changes. If Friday's update breaks the menu, roll back while you debug.
  • Mobile app "Continue on Web" deep links open the portal directly to the relevant page — for admin tasks that benefit from a desktop UI.
  • Audit log on Team Pro tracks every admin action with actor and prior state. Useful for compliance reviews where regulators ask who changed what.
  • Role-based access is granular — admin / member / billing — with member access scoped to the user's own data only. Useful when the office manager handles billing but doesn't need full admin.
  • 12 primary surfaces, all under one URL — no separate "call analytics dashboard" subdomain or "recordings vault" sub-product.
Admin portal · FAQ

Common questions

  • Solo doesn't need the multi-user portal — there's no team to manage, no hunt groups to configure, no department-routing to set up. Solo is configured entirely from the Kelir mobile app. The web portal is a Team-plan tool for managing multi-user routing and admin tasks.

  • Anyone with the admin role on a Team account. Member-role users can sign in for their own user data only (own call history, voicemail, settings). Billing-role users can sign in for invoice and payment management. Roles are configurable per user from the admin → settings page.

  • A deep-link shortcut from the Kelir mobile app to the admin portal. Tap it on the IVR builder page in the mobile app and the portal opens directly to the same IVR config in the browser — useful for tasks that benefit from a desktop UI like dragging-and-dropping IVR tree nodes or downloading multiple recordings.

  • On Team Pro, the audit log tracks every admin action: user added, user suspended, IVR configuration changed (with prior and new state), recording downloaded, retention policy changed, hunt group reordered, billing changes. Each entry has actor (admin user), timestamp, prior state, and new state. Exportable as CSV for compliance reviews.

  • Yes. Multiple admins can be signed in simultaneously. Conflicting changes (e.g. both editing the same IVR menu) are versioned — last-save-wins, but the prior version is preserved in version history with a one-click rollback. Audit log records both attempts.

  • No. Day-to-day phone work happens on the user's phone — calls ring on the cellular eSIM line via the native dialer, voicemails arrive by email with transcripts, the Kelir mobile app handles personal settings. The portal is for admin tasks (managing the routing across the team) and for the rare member-level data deep-dive ("give me my own call history for last quarter").

The phone system, on the SIM.Five-minute install.