Marketing & EmailEUYour Viber bot and business account are connected to your CRM: a client's message becomes a request, and the status of the order reaches the client in Viber
For many businesses in Ukraine and Eastern Europe Viber is the channel where clients actually write and read. Rakuten Viber gives a business two doors: a bot, which clients subscribe to and talk with, and business messages, which go to a client's phone number through official messaging providers. We connect your bot and your business messaging to your CRM, so that a message in Viber creates a request with the client's name and history, the manager answers from the CRM card, and the order status, the delivery number or the appointment reminder go to the client in Viber from your system. Viber stays your channel and your account; we make it part of your workflow.
Before messages in the Viber bot are read from a phone by whoever has it, and requests get lost between shifts.
After each message creates or updates a request in the CRM with the client's name and the full chat history, the manager answers from the card, and nothing is left unanswered.
Before the client writes «where is my order?» three times a day, and the manager looks it up and answers by hand.
After when the order moves to «shipped», the CRM sends the client a Viber message with the shipment number, and the delivery status shows the manager it was read.
Before the administrator calls every client the evening before to confirm the visit, and half do not pick up.
After the CRM sends a Viber message with the time and the buttons «confirm» and «reschedule»; the client's tap comes back into the CRM and the schedule updates itself.
Before the same person wrote in Viber, called and left a form on the site, and the CRM has three different records.
After the connection matches the Viber subscriber with the client by phone number or by the identifier the bot asked for, and all conversations land in one card.
For those who want to check: each point links to the official documentation page it comes from.
The client's bot connects through the REST Bot API: each bot has its own authentication token passed with every request, and incoming messages and events arrive at a webhook address on the client's side.
Source: developers.viber.com ↗ checked 2026-09-28A bot can message a user only after that user has subscribed by writing first; text, images, files, contacts, locations and keyboards with buttons are supported.
Source: developers.viber.com ↗ checked 2026-09-28Viber reports the status of each message — delivered to the device and seen — and every callback is signed with HMAC-SHA256 using the bot token, so the client's server can verify its origin.
Source: developers.viber.com ↗ checked 2026-09-28Since 5 February 2024 Viber bots are created on commercial terms only; a webhook is accepted over HTTPS with a valid certificate; broadcast is limited to 300 subscribed recipients per request.
Source: developers.viber.com ↗ checked 2026-09-28Viber Business Messages cover service notifications such as delivery status and appointment reminders, one-time passwords and two-way conversations with clients by phone number.
Source: www.forbusiness.viber.com ↗ checked 2026-09-28A Viber business account is created to promote goods and services and to communicate with clients directly; the service is operated by Rakuten Viber (Viber Media S.à r.l., Luxembourg).
Source: www.viber.com ↗ checked 2026-09-28A bot can only write to people who subscribed to it first, and Viber does not hand out the list of subscribers later — the connection has to remember every subscriber at the moment they appear. Since 2024 bots are created on commercial terms, and messages to clients by phone number go through official messaging providers, so both need to be arranged with Viber or the provider before the launch. Mass sending through the bot is limited to a few hundred subscribed recipients per request, and a message that cannot be delivered is retried for up to two weeks and then dropped without a status. Viber's own addresses for incoming messages are accepted only over a secure connection with a valid certificate, and a client's profile data can be requested only a couple of times per half-day. Viber is your channel and your account: we connect it to the CRM, but do not send messages to your clients on our own behalf.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →
Marketing & EmailUSThe company's Telegram bot takes requests and answers clients, every conversation lands in the CRM, and the team gets alerts about new leads and overdue tasks in its own chat.
See scenarios →
Marketing & EmailUSClient messages from the company's WhatsApp Business number land in the CRM, the manager replies from the CRM, and order updates go out as messages approved by Meta.
See scenarios →
IP telephonyUAA text to the client goes out on its own the moment something happens in your CRM — and the delivery status comes back to their card
See scenarios →
Marketing & EmailUAEmail, SMS and messenger chatbots that start from what just happened in your CRM
See scenarios →
CRMUAUkrainian CRM that pulls orders from your site, marketplaces and chat apps into one pipeline
See scenarios →
Marketing & EmailEUOne connection for email, SMS and WhatsApp that keeps every channel talking to the same contact record
See scenarios →Implementation · Development · Integrations →
Viber is a trademark of its owner. CoreviaFlow is not affiliated with it unless stated otherwise. Screenshots are taken from public vendor materials; the source is shown under each one.
