Zahra ZoghiProduct Designer
← All work

Case study 03 · Classeh

Tamas Hooshmand

A business panel for setting up AI voice assistants, running call actions and reading the results, made for business owners, not engineers.

Role
Sole product designer
Company
Classeh
Period
May 2026 – now
Status
MVP handed off · panel live
Tamas Hooshmand · panel
Creating a new assistant: identity, behaviour, knowledge and voice, review
Wallet and usage
Wallet: minutes available, used this month, price per minute
Creating an assistant on mobile

Screens from the live panel in November 2026, on a demo organisation with no calls yet.

01The problem

A voice assistant is set up through many small decisions: how it sounds, what it may do, what it knows, when it calls.

The panel has to turn that into a short, guided task, and make the results of calls easy to read for someone who isn't technical.

The MVP has six areas: a home view with overall status, important results and what needs attention; assistants; contacts; actions; results; and organisation information. Settings is marked “coming soon” rather than half-designed.

02My part

I design the panel's workflows and states and hand them to development.

Assistants

  • Setup wizard
  • Personality, abilities, proactivity
  • Fallback behaviour
  • Main and backup voice

Contacts and actions

  • Import by group, file or one by one
  • Groups and call history
  • Actions: goal, assistant, group, time

Results

  • Statistics and status filter
  • Results table
  • Contact and call detail panel

Account

  • Organisation information
  • Wallet and call-minute packages

Supporting material

  • Light and dark logo
  • Ten-slide catalogue
  • Demo call conversations
  • Interactive HTML prototype of the smart call, handed straight to the backend team

Production code and the backend are the development team's work.

03Constraints

01

Many settings, non-technical users

Personality, abilities, a level of proactivity, fallback behaviour and two voices, set up by business owners and staff.

02

Language that fits the business

The product first used “Agent” and “Campaign”, which don't match how a business talks about this work.

03

Call time sold as credit

Buying, approving and using call minutes had to be easy to follow inside an MVP.

04Key decisions

01

Names that match how businesses talk

Renaming changed the product's mental model as much as its copy. Keeping old links working through redirects became a handoff requirement.

Renamed
Agent→Assistant
Campaign→Action
Old links redirect to the new names
02

A wizard instead of one long form

Setup is split into four short steps, so a business can configure an assistant without facing every option at once, and sees everything once more before it goes live.

Four steps
IdentityName, tone, form of address
Behaviour
Knowledge and voice
Review and activate
03

Fixed packages, not custom amounts

Custom call-minute amounts were removed in favour of four fixed packages. That removed a whole class of states and made the flow shorter to explain.

Before
Any amount of minutes
After
Package 1Package 2Package 3Package 4
04

Results that keep their context

A detail panel opens beside the results table, so someone can read one call without losing their place in the list.

Results
One call, in detail

05Flows and states

Buying call minutes
Choose a package
Confirm in an invoice
“Request registered”
Admin approves
Balance shows minutes left and the next package
So a package is always in one of these states
No active package→Waiting for approval→Active→Used up: the next one starts
What an action ties together
A goal+An assistant+A contact group+A time=An action

06Screens

Home
Home for a new organisation with setup progress
Home, first visit. Setup progress (0 of 6) with the next step, and a warning while no call channel is active.
Creating an assistant on mobile
On mobile. The same wizard with a bottom tab bar.
New assistant
New assistant wizard on desktop
New assistant. Name, tone (warm or formal) and how it addresses people.
Wallet and usage
Wallet and usage on desktop
Wallet. Minutes available, this month's use, the price per minute, and an empty state that explains what to do.

07Status

I designed and handed off the MVP panel's workflows. Implementation differs by area, and I don't assume which parts match my handoff exactly.

I'm not quoting call success rates, cost savings or conversion: none have been measured for this work.

I can walk through the full spec and handoff files in an interview.

08What I learned

Naming is a design decision. Agent to Assistant and Campaign to Action changed the mental model as much as the copy.
Limiting choices can be the better design. Fixed packages kept the credit flow short and its states few.