Project done during my time as a Product Designer at Pontaltech: https://pontaltech-rcs-app-rbm.pontaltech.com.br/en
Login/Landing Page and Home Screen
The Problem
Rich Communication Services (RCS) is a technology that enhances the messaging experience by offering more advanced features than traditional SMS. Google is one of the main promoters and developers of this technology. RCS allows sending text, images, GIFs, videos, files, audio, and other types of media, as well as interactive buttons.
However, in order to send RCS campaigns, a brand or company needs an RCS Agent registered with Google, and Google itself did not have a very intuitive process for this.
As an official broker, Pontaltech took the lead in RCS in Brazil, and if we wanted to stay ahead, we needed to streamline the creation of RCS agents for our customers' platform.
No other competitor had such a solution at the time, so we had to move quickly in building this platform.
RCS by Google
Hypothesis
After some refining and discovery, we decided to set the flow like this:
1 - Our client user creates his fully customized RCS Agent through a 3-step wizard;
2 - This RCS Agent is sent to a Pontaltech user, who is responsible to check and launch pending agents. This will require a 4 step wizard to get it done.
3 - This agent is going to be sent to the carrier approval via Google API.
The RCS Agent status could be checked by our clients at the home screen. Once it gets all the approvals by the Telecom carriers, this RCS Agent is ready for use (in an external SaaS).
User flow 1 - Agent Creation
User flow 2 - Agent launch
Opportunities
- Create an intuitive flow for our clients (trying to keep it simple for the devs but at the same time, 'wow' the clients);
- Build simple but modern components;
- Develop an internal process for data validation, so the home screen for pontaltech users gets to be slightly different, highlighting pending agents first;
- Use a design that reflects Pontaltech’s official colors to further strengthen our SMS and RCS platforms' branding;
- Build everything quickly and in two languages: English and Portuguese;
Site map/flow
Results
After validating the main user flows, I've worked on the following style guides and prototypes:
Style Guide
Main prototyped flows - 1: Client user flow / 2: Pontaltech's user flow
Conclusion
Unfortunately, this product only started being used after I left Pontaltech, so I don't have any metrics here with me. However, I believe it will certainly require some tweaks and fixes based on client feedback. I'm also confident that this platform will help Pontaltech attract more and more RCS customers over the coming year.
Finally, I'm glad to have been part of this project.
