Advisor app | Sellers’ side
Weâve created a strategy by realizing that in order to improve our products/services we have to take control and show the supply side how they can improve their service. We are doing that with an MVP(mobile app) which will be the perfect tool to enable our users(supply) to monitor their performance and be better at what they are doing!
Task
The primary challenge was to unify and optimize a complex advisor workflow across multiple brands, balancing synchronous and asynchronous communication tools to fully support advisorsâ diverse needs. This involved overcoming fragmented workflows, inconsistent user experiences, and limited integration between platformsâwhile also driving rapid product development without a dedicated Product Manager. Coordinating multiple teams, defining clear technical requirements, and making strategic decisions to deliver a scalable, user-friendly solution required balancing usability, business goals, and technical feasibility.
adviqo Group creates products for everyone to experience life coaching. It is the market leader for more than 20 years since it has developed products serving customers in the US, Canada, Latin America, Europe, and the UK. Ever since we have been shaping the scope of live advice.
In one sentence adviqo develops apps and websites which connect psychic advisors with customers all over the world.
I would like to compare the ânatureâ of our apps with fiverr or airbnb.
Airbnb has users that are hosts, and has to teach them how to do their job properly and apartments seekers.
Fiverr, similarly, is a place for freelancers and users that are looking for their services.
adviqo products are no different, in which the advisors are the supply users and the customers the demand users. This Case Study is about the advisor(supply) side.
Â
iOS & Android app
iOS & Android app
iOS & Android app
Flutter
Flutter
iOS & Android app
iOS & Android app
iOS & Android app
Our apps share similarities with platforms like Fiverr and Airbnb.
⢠Airbnb: Hosts need guidance on managing listings; seekers find apartments.
⢠Fiverr: Freelancers offer services; users search and buy those services.
In adviqo products, advisors are our supply side (like hosts or freelancers), and customers are the demand side.
⢠This case study focuses on the advisor experience.
Sessions between customers and advisors happen via chat or calls.
⢠Products differ: synchronous vs. asynchronous communication, upsell options, service matching, and premium offerings.
Advisors need to:
⢠Promote themselves
⢠Upsell services
⢠Grow their business in our marketplace
Previously, we focused mainly on demand (customers), but advisor success is crucial for platform growth and quality.
⢠Supporting advisors helps retain customers and sustain long-term business.
Be the best platform on the market for advisors
- Back to the roots, delivering value for our advisors
- App (Mobile enable our advisors)
- Greatly improved and modern advisor interfaces/tools
One unified advisor toolset for all adviqo brands and services
â˝ď¸ đŻ Gamigication for advisors work & performance
đ Performance dashboards & instant feedback
đ¤ Automated advisor marketing capabilities (CRM)and Advisor Coaching
Platforms
- iOS
- Android
- Website
- Sychronous communications products vs asychronous communications products
- Not all services are available for all portfolio products
- Cannot do video chat and phone chat at the same time
- Cross-brand issues
After defining the vision and goal we did some benchmark research to see what solutions other products are using to achieve their goals. Products were characterized mainly from:
- 2 user roles (demand & supply)
- Gamified & fun way to âeducateâ the supply users to become better
- Sharing Perfomance metrics with the Seller side, aiming to align their efforts<>impact to alocate their actions accordingly
In order to define the structure of the MVP we first had to study the current structure so we can define the Current Technical Back-End Requirements and see how we can make the most out of it. Our development resources were limited so we had to come up with âGrowth hacksâ to reach the UX goal that was set from the benchmark research.Â
In order to start the discussion and engage the stakeholder we moved forward with designing the bussiness vision, having always in mind the benchmark explained above and of course the fact that many of these features will not be included in the MVP. The goal was to start the ideation and iterate with the developers by having some concepts to talk over them.
The main screens of the app should be
- A dashboard in which the advisors will be able to monitor their performance
- A gamification feature which will motivate them to work harder
- âIntranetâ to point them in the right direction
- A Chat screen in which they will be able to chat with customer cross-brand
- Â A way to edit their multiple profiles across all the brands OR motivate them to work for more of adviqoâs brand
In order to define the structure and functionalities of the MVP we first had to study:
- The current structure in order to define the Current Technical Back-End Requirements and see how we can make the most out of it.
- Iterate with the developers on the visualization of the Business vision which was presented above.
To achieve that faster and efficiently, I conducted a workshop session to define:
- Information coming from the Information architecture and what we already have in the Back-End
- Low-effort features for the MVP
- High-effort features for the 2nd version
After the Workshop, the Information architecture including the low-effort features was the next action I took. Itâs including the primary screens & flows which will be enough to iterate and come up with the first visualization of the Product.
Since adviqo has many products and apps they started thinking about leaving behind the native apps and move forward with Hybrid applications which will save time and resources. Itâs not only twice more work to develop for two platforms but the QA engineers have to test every bug and new feature 2 times.
Thatâs why we tested Flutter in a small app which we have as a pilot project. The experiment was successful but I wasnât satisfied from the design of the app, since we had to use material design for both of the platforms.
I wanted to explore more Flutterâs Front-End possibilities and libraries for this project but for future projects as well. I had some experience designing & developing a Hybrid app with ionic but I am more familiar designing for Native apps. Therefore I had no experience how Flutter will influence the design of our apps and I had to find a solution because material design might looked good on Android devices but on the iOS it wasnât so great.
After some research and 1on1 discussions with a Flutter developer I came with a conclusion and two approaches/proposals to the team:
- Either we could move forward with a custom design so it will look like a unique appâ¨- pros: Same code for both platforms which is the reason they chose Flutterâ¨- cons: It will take more time to launch the MVP since custom design means that the developers will have to code every UI elements
- Or we will use Cupertino SDKs for iOS exports & Material for Android. Cupertino libraries, looks like they can offer this iOS like look & feel.
pros: Native look & feel for both Android & iOS users. Faster launch of the MVP since developers will user libraries provided from Material and Cupertino SDKs.
cons: The core code would be same BUT there will be differences since we would use different UI libraries for each platform/export. Maintenance of the app might be slightly more demanding.
The Final decision was to move forward with the 1st option.
Live session in which I shared draft designs with the Vice President and we conducted:
- Whiteboard session
- Brainstorm on paper in order to iterate fast
- Brainstorm on Gamification which we wanted to have in the app with âmanual hacksâ that donât require dynamic tables in the Back-End and statistics that would achieve a customized experience BUT simple tricks that would motivate and engage our users.
Since our development resources were limited we would have to come up with âhacksâ to reach the UX goal that was set from the benchmark research
This screen aims to give some feedback to the advisor regarding his performance and what he can do better.
- Highlight other ways of income besides chatting(currently 70% of sessions are chats) like calls, services, promote features etc.
- Educate the advisors with articles on how they can improve. (ex. how to use coupons, upselling technics, etc.)
đŻ Goal
The goal is to improve loyalty of advisor’s customers.
- Ads are getting more and more expensive, so by investing on retention we could save from our expenses.
The advisor should be able to send a coupon while chatting.
- This feature would help to increase the Avg Chat duration therefore our revenue of all of our apps.
The advisor should be able to send a coupon as an âasynchronousâ message.
- That idea started because we had many issues with our CRM and we proposed to let the advisors do the CRM from their part.
- Only when the advisors are missing a call, they can reach out to customers. This feature was made that way to avoid spam.
- The advisors will be able to create pre-made messages from their Profile, which later they will use them while reaching out to customers
- Multiple Chats at the same time
- Indicator of the brand/app that the customer is coming from
- Filter per Offline(Asynchronous communication) & Online(Synchronous communication)
Enabling sending mp3/mp4 messages was vital for our products because users seemed to not like calling sessions but at the same time, we wanted to offer the possibility to have a more “humanized” chat.Â
Other reasons:
- Advisors (Supply) can have multiple chats at the same time (until 3) therefore calls are not really convenient for them.
- Users (Demand) regularly ask for proof (ex. of rituals, photo of Tarot deck, sound of shuffling) which by adding this feature it will be resolved
