Web Phone

Use cases and functional specs for engineering teams

Phone.com

Process

How we work is often shaped by where we work – the players involved, the dates and deadlines we’re working towards. For the Web Phone, I worked as I did at previous companies earlier in my career. I merged user flow and wireframing efforts with design, but refrained from focusing on cosmetics in order to deliver material that would meet requirements for a minimum viable product (MVP).

Deliverables

High-fidelity wireframes focusing on key scenarios, along with the necessary specs for Engineering to develop our MVP. The final designs would come as a fast followup.

Expectations and Outcome

Transferring and Conferencing were of critical importance as they were the most complex of UX scenarios, and the features most requested by users. The two features were also labeled required for any viable release. The MVP was delivered on time and in clean fashion with all requirements met.

Design System and Component Library

Behavioral Components, Assets and Styles

Regardless of how unique or radical any new feature might be, this component library is vast and rubbery enough to scale up, while clear designations, specs and guidelines insure consistency remains intact.
View project

Talk, Text, Meet and Fax

Core Landing Page Designs

Conversational AI solutions were customized and integrated into these Phone.com customer landing pages, offering call handling features such as Virtual Reception, Voice-to-Text Call Recordings with generated Call Summaries and Action Items, and Automated Voicemail Transcriptions.
View project

Cross-sell Accessories

UX Simulation

There was a huge opportunity lost on Phone.com sales of device accessories. These products had been treated without real consideration, and discoverable only by a manual search by the user. The solution was implementing a cross-selling sales approach.
View project