DEV Community

TehProf.kz
TehProf.kz

Posted on Edited on

A helpdesk inside Bitrix24: when CRM tasks are not enough for customer support

Bitrix24 is a strong place to run sales, tasks and projects. But a team that does customer support, especially an IT service or managed-service company, often discovers that "a task per request" stops working at some point. This article explains where that point usually is, what a helpdesk adds, and what to look for when you evaluate one for Bitrix24.

This article was written by the TehProf team, the developer of TehProf Dialogs, TehProf Support and TehProf Booking, apps for Bitrix24 and amoCRM. Links and contacts are at the end.

The three symptoms

Support teams that outgrow tasks and chats tend to describe the same three problems.

Requests get lost. A customer writes in WhatsApp, another sends an email, a third calls. Each arrives in a different place. Without one log, there is no single answer to "what is open right now?" and someone's problem is quietly forgotten.

Time is not measured. The team works, but cannot show how many hours went to which client. Billing happens in a spreadsheet or by feel. When a client disputes an invoice, there is nothing to open and show.

The client cannot see the status. So they call, every half hour: "What is happening with my request?" Each call interrupts the person who is trying to solve it.

None of this is a Bitrix24 failure; it is the difference between a general business suite and a tool built around tickets, SLAs and hours.

What a helpdesk adds

A helpdesk organises work around the ticket: one request, one number, one owner, a deadline, a status, and a conversation attached. In practice you want these things:

  • One queue for every channel. Messenger, email and phone requests become tickets in a single place.
  • Statuses and priorities. Something like new, in progress, done, closed; and normal, urgent, critical.
  • Time tracking and hour packages. Time is booked against each ticket and deducted from a client's package, so billing is based on records.
  • SLA tracking. Response and resolution targets are visible to the team, and ideally to the client too.
  • A client portal. Customers create requests and follow status and history themselves, instead of phoning you.
  • Reports. Counts, response and resolution times, trends over a couple of weeks, split by status and category.

What "inside Bitrix24" should mean

A helpdesk can be a separate website that you log into, or it can live inside the CRM where your team already works. For a Bitrix24 team, the second option removes a lot of friction. Look for:

  • a tab in the deal, contact and lead cards, so a ticket can be created without leaving the CRM;
  • installation from the Bitrix24 Marketplace, so it appears as a normal application;
  • a way to use the same people and clients you already have, rather than re-entering them.

One option: TehProf Support

We develop TehProf Support, a helpdesk portal built for this scenario, available at support.tehprof.kz. Here is what its own site states, so you can compare it with your checklist:

  • Each message or call becomes a ticket with a number, a deadline and an owner. The client sees the status; the team sees hours.
  • It works with Bitrix24, amoCRM and 1C. In Bitrix24 there is a "Support" tab in the cards; for amoCRM there is an application; for 1C there is a section that opens the client's cabinet inside the accounting program.
  • Channels: WhatsApp, Telegram, email and MAX, including messenger groups, can feed one queue. WhatsApp and Telegram connect as separate lines, from 12 000 tenge per month per line; WhatsApp calls are a separate add-on on top of a WhatsApp line (10 000 tenge per month, as listed on the site).
  • Calls can be taken through Bitrix24 telephony, including SIP numbers connected to the portal, and through WhatsApp, with recording stored in the ticket history; transcripts and summaries are available on supported lines.
  • Tickets: priorities (normal, urgent, critical), statuses (new, in progress, done, closed), filters and search.
  • Hour packages per client, with time deducted per ticket, plus timers and reports for billing.
  • A client portal is included on every plan, including the free one. A widget can be embedded on an external site, and screen sharing from within a ticket is available.
  • A dashboard with response and resolution times and 14-day trends.
  • Interface in Russian, Kazakh and English; a REST API; and a way to connect your own AI assistant (such as Claude or ChatGPT) through the MCP protocol, acting within your user's rights.

About plans, as listed on the site: a Free plan at zero cost (2 operators, 50 tickets per month, 20 clients, 250 MB), and paid plans from Starter (8 250 tenge per month when billed annually) up through Pro and Business to an individual Enterprise arrangement. Check the site for the current numbers before you decide; prices change.

How to evaluate any helpdesk for Bitrix24

Use the same questions for every candidate, ours included.

  1. Where does the ticket start? Can you create it from a deal, a chat and an email without copy-paste?
  2. Does time tracking match how you bill? Packages of hours, per-ticket timers, reports for the client. If you bill per hour, this is the feature you will use daily.
  3. What can the client see? Status, history, assigned operator, deadlines. This is what reduces the "any news?" calls.
  4. How are channels connected? Check whether messengers connect officially or through a QR link, as that affects the risk of a number being restricted.
  5. What is the free tier, really? A free plan is a good way to test with a real client, but read the limits (operators, tickets, clients).
  6. What happens to your data? Look for statements about tenant isolation, secrets storage and where the data lives.
  7. Language support. If your clients write in Kazakh or Russian, check that the interface and notifications are available in those languages.

Alternatives worth looking at

You are not limited to a Bitrix24-specific tool. General helpdesks such as Freshdesk, Usedesk, Omnidesk, HappyDesk or Jivo exist in various forms: some are heavy on ticketing and SLAs, others focus on live chat. The right choice depends on how much of your process is ticketing versus chatting, and on whether you want one subscription for both. If you only need a website chat widget with a small team, a live-chat product may be all you need; a full ticket system with hour accounting is more than you require. The reverse is also true: a widget with no tickets, no SLA and no hour tracking will not fix the three symptoms described above.

A simple pilot plan

  1. Pick one client and one channel.
  2. Route their requests into the helpdesk for two weeks.
  3. Track hours on every ticket.
  4. Give the client portal access and ask whether they stopped phoning for status.
  5. Compare the hours you recorded with what you would have billed by estimate.

If the pilot answers "yes" to all three symptoms (nothing got lost, hours are known, status calls dropped), roll out to more clients. If not, you have learned what to look for in the next tool.

Summary

Tasks and chats in a CRM are a good start for support, but once you need a single log of requests, recorded hours and a portal where clients can see status, a ticket-based helpdesk pays off. Choose one that sits inside Bitrix24, matches how you bill, and lets clients see progress. TehProf Support is one such option, with a free tier to test on a real client; the checklist above will help you compare it fairly with the alternatives.

More in the TehProf Support site.

The TehProf team — developers of TehProf Dialogs and TehProf Support

Where to find TehProf

Top comments (0)