Bots and mini apps

In a messenger, a person can quickly repeat an order, learn about a change, receive material or ask for help. Together, we choose a task that your audience can conveniently handle in a familiar channel.

A bot suits short exchanges of messages. If people need to compare options or manage a large set of data, we consider a mini app. We check how many actions each format requires of a person.

Repeated questions, unclear confirmations and notifications without the necessary details get in the way of using a bot. We design conversations and screens so a person understands what has happened and what they can do next.

We check repeat actions, returning to a task and transfer to an employee. When handing over a conversation, we preserve its history and the purpose of the request so the specialist can help immediately.

We connect a confirmation in chat to an action in the operational system. We define where information comes from, where the current state is stored and what employees control. We check what a person sees and what the team receives at the end of the same journey.

Notifications, orders and materials use shared service data. Employees see requests from the bot in the operational system they already use.

We separate the core logic and business data storage from the platform interface. We record what information stays under the company’s control and what the external service receives.

This provides a foundation for another channel when one is needed. For the move, we adapt the interface and integrations to the chosen platform’s capabilities. Operating rules and business data remain the foundation of the new channel.

We calculate messages, processing, integrations and maintenance for the expected usage pattern. Before launch, we check the chosen platform’s terms and agree who monitors changes and handles operating situations.

With the future owner, we practise updating content, investigating an error and transferring a request to an employee. We distinguish everyday management from technical changes. The team understands what it can do itself and when a developer is needed.

We hand over source code, access, an integration map, employee permissions and instructions. We explain why one case needs a screen, another only a message, and which actions require confirmation.

The team can develop the familiar channel or add another one with an understanding of what makes the service convenient for people.