Blip Desk App

Custom breaks

Custom breaks

Custom breaks

Context

Context

Custom pauses already existed in the Web product and were designed to support the journey of the Support Manager.

Quando um atendente entrava em Pausa no atendimento, não era possível ao Gestor gerenciar para qual finalidade estava sendo tirada esta pausa. Se o atendente fosse um usuário do Blip Desk App, o gerenciamento das pausas não funcionava, já que existia essa especificação na Web e no Mobile não. Assim, o banco de horas do atendente não parava de rodar até que este acessasse Blip Desk pela Web.

Problem

When an agent went on a break during a support session, the Manager couldn’t manage or identify the reason for that pause. If the agent was using the Blip Desk App, pause management didn’t work properly, since this specification existed only on the Web — not on Mobile. As a result, the agent’s time bank continued running until they accessed Blip Desk via the Web platform.

Goal

Align the custom pause functionality with the Web version to enable pause management for the Support Manager.

As pausas personalizadas já eram existentes no produto Web, e foram criadas para impactar na jornada do Gestor de atendimentos.

Solution

A new flow was designed for agents to go on pause during support sessions. To help with time management, we added a timer on the support screen showing the elapsed time since the pause began. Agents can also select the specific type of pause they are taking.

Feature flow

Feature flow

Once the agent chooses to go on pause, they can select the type of pause. After making a selection, a timer is activated to help track the duration of the break during the support session.

Acceptance criteria and trackings

Since this functionality already existed in the Web product, we added a property to MixPanel to identify the type of device used when the user performs the action.


The pause list includes all custom pauses from every chatbot the agent is associated with. Additionally, pauses with the same name across different bots should appear only once for the agent.

Final delivery

Final delivery

A prototype followed the final design handoff to development, as well as to other departments such as Sales and CX. This made it possible to anticipate the pain points of certain users who relied on these features to perform their work.

Next steps

Next steps

  • Add notifications to remind agents to return to online status after a pause.

  • Display to users the time limit set by the Manager for each custom pause.

  • Cross-analyze feature usage data with the adoption rate of companies that required this functionality to start using the app.

© 2023-2025, Roberta Glass

© 2023-2025, Roberta Glass

© 2025, Roberta Glass

Create a free website with Framer, the website builder loved by startups, designers and agencies.