Skip to content
SemCue

Art Quest · Horror Cinema · MORPHEUS

Four messengers.One window, payment in a click.

Customers of the quests, the cinema and the theatre write on MAX, Telegram, VK and Avito. The conversations ran in the chats of the previous CRM, and managers tracked payments themselves. We brought all four channels into one window of the company cabinet. Each conversation attaches to the client and the deal automatically or by the manager’s choice, a prepayment link comes from one button, and the payment reminder reaches the customer by itself.

Live · conversations in four channels, links and templates, automatic prepayment reminders · since October 2026

Customer writes

  • MAX
  • Telegram
  • VK
  • Avito

One manager window

The client and the deal sit next to the conversationReply with Enter, refresh every 5 to 10 seconds

Payment in a click

“Payment link” button16 templates that auto-fill the amount, deadline and link

The cabinet reminds

In the same messenger30 and 10 minutes, or 24 hours and 2 hours before the end

Four channels, one screen

VK asks about a children’s party, Telegram confirms a time, MAX wants an address, Avito waits for an answer about a listing.

All four streams flow into one list. The client and the deal sit next to the conversation. The manager replies without opening a messenger, and the customer gets the answer where they wrote.

The “Waiting for a reply” list with MAX, Telegram, VK and Avito icons, next to an open conversation with “Template” and “Payment link” buttons.
The cabinet on desktop: the “Waiting for a reply” queue on the left, the conversation on the right. Demo data. Interface translated for this page.
  • 747conversations in the cabinetVK 515, MAX 138, Telegram 72, Avito 22
  • 7 sfrom an Avito message to the cabinettest message, 20 October

Replying like in an ordinary messenger

The manager types and presses Enter. The window refreshes itself every 5 to 10 seconds, so new messages appear without a reload. On a phone the conversation opens full screen.

The conversation finds the client on its own, and the deal is picked automatically or linked by the manager. If the customer writes for the first time, the manager creates the deal right from the conversation. If the deal is wrong, a search swaps it.

A conversation window on a phone: the client, a “waiting for a reply” status and “Template” and “Payment link” buttons above the reply field.
A conversation on a phone. Demo customer. Interface translated for this page.
  • First

    Write by phone number

    The manager enters a number and the MAX or Telegram conversation is already linked to the client and the deal. We built and released this in about 2 h 10 min (including the wait in the release queue).

  • Order

    Spam and “No reply needed”

    Spam and messages that need no answer leave the queue. The list keeps only people who are waiting for an answer.

  • Duplicates

    Merge clients

    One person ended up in the database twice. Duplicate cards merge into one.

Three weeks, almost four thousand messages

Between 9 and 29 October, the cabinet recorded 3,998 messages. Managers sent 799, the bot sent 2,471, and customers wrote 700.

Bot and manager messages sit in one conversation thread.

  • 3,998messages9 to 29 October 2026
  • 2,471sent by the bot
  • 799sent by managers
  • 700written by customers
A further 28 messages are system messages.

For comparison: the previous CRM recorded 77,668 messages in 10,483 conversations over 2.8 years, across all its channels.

The cabinet reminds the customer by itself

The link is out and the customer has put the phone down. Now the cabinet decides whom to nudge and when. Once the manager has really sent the link, the system sends reminders in the same messenger.

For a one-hour window, reminders come 30 and 10 minutes before the end. For a children’s party with a 48-hour window, they come 24 hours and 2 hours before.

1-hour windowbooking through a manager

  1. Link sent
  2. Reminder 30 minutes before
  3. Reminder 10 minutes before
  4. Payment deadline

Children’s party48-hour window

  1. Link sent
  2. Reminder 24 hours before
  3. Reminder 2 hours before
  4. Payment deadline

Quiet hours22:00–09:00 Omsk time: the reminder moves to 09:00

Stays silentFor paid bookings, closed deals and spam. Checks the payment status before every reminder

The reminder grid depends on the length of the payment window. Quiet hours follow Omsk time.

The cabinet stays quiet at night. A reminder that falls between 22:00 and 09:00 Omsk time moves to 09:00. It does not write about paid bookings, closed deals or spam conversations, and it checks the payment status before every reminder.

The chat shows the manager’s message with the link and the automatic payment reminder.
The payment reminder went out by itself. Demo customer. Interface translated for this page.
  • 19:01 and 19:21two reminders sent in the test runOmsk time, test deal, the link was valid until 19:31
  • ≈1 h 05 minto build the reminders up to releasethen about 2 h of test runs
Reminders have been on since 20 October 2026, 19:29 Omsk time.

What stops a stray message

Messages to customers do not forgive mistakes. If a manager presses send twice on a bad connection, no duplicate goes out: every action carries a key and a repeat is recognised. A reminder exists once as well, and a server restart cannot multiply it.

Until the manager sends the first message, no empty conversation is created. An abandoned window leaves no clutter in the lists or in the “Waiting for a reply” queue. The phone number shows masked in the window and never appears in the address bar.

  • Duplicates

    Pressing the same button again sends nothing twice

    After a dropped connection a manager can press again without risk.

  • Reminders

    One reminder per deadline and link

    A second worker or a restart does not create a second reminder.

  • Privacy

    Number masked and kept out of the address

    The customer’s phone never reaches the browser address bar.

How it was built

Three features in one working day

On 20 October, during an outage of the previous CRM, replies, links and reminders were needed in one place. We shipped the features one at a time and tested them.

“Write first” took about 2 h 10 min, links and templates about 1 h 20 min, and reminders about 1 h 05 min up to release. About 2 more hours went on test runs on a test number, and the reminders went live the same evening.

  • The companySet the rules: who pays and how much, payment windows, quiet hours, what to say to the customer.
  • SemCueFour channel adapters, the conversation window, payment links, templates, the reminder scheduler and pre-release checks.
  • ManagersWork from one window and use ready texts instead of typing them.

For technical readers

For technical readers

Channels
MAX, Telegram, VK and Avito adapters share one interface: polling for reads, a queue for sends, per-channel limits.
Linking
A conversation finds the client by channel identifier and phone number, and links the deal automatically or on the manager’s choice.
Payment
The sales service issues the link through YooKassa with a short Link Builder address. Pressing again returns the same live link.
Reminders
A worker job plans each deadline from the window length and quiet hours, and asks for the payment status before sending. One row per link and deadline.
Reliability
An idempotency key on every send, a lock per number on the first message, and separate switches for reading, replying and reminders.

Where the numbers come from

Sources

Next system

Staff portal →

SemCue / Let’s talk

What would you like to work on?

Tell us about your project and what you need. A rough idea is enough.

Get in touch on Telegram

We’ll discuss your goals, where things stand and the right next step.

Discuss your project on Telegram
In developmentThis site is still being built, so things may change.