Case study · Bitrix24 Box + RoboREST

How to unify hotel, restaurant and equestrian ops in one Bitrix24 system

Answer in short: for a 50+ person multi-service country resort we replaced WhatsApp hand-offs and a siloed booking tool with Bitrix24 Box - 10+ service pipelines, smart processes for stables and facilities, and RoboREST guest-journey automation. Manager time on routine hand-offs dropped about 40%; core live in ~3 months.

Industry: Hospitality · country resort Size: 50+ employees · 7 departments Stack: Bitrix24 Box + RoboREST Region: Eastern Europe Timeline: ~3 months to core live

Book a Free Consultation See what we built

One CRM, many service funnels: hotel, restaurant, equestrian, SPA, events and more.

Results

Measured after go-live of core pipelines and guest automations vs the previous chat-driven process

-40%

Manager time spent on routine hand-offs

10+

Service pipelines in one CRM

50+

Staff on a single operations portal

The challenge

A growing multi-service resort - hotel cottages, restaurant, stables, SPA, bowling and events - outgrew WhatsApp

Call-centre staff forwarded each guest request into 5-7 department chats. A legacy equestrian / booking system covered horses and some resources, but not hotel, F&B, SPA or facilities. Guest history vanished between shifts; cross-sell almost never happened; leadership had no live view of load across services.

Guest requests hopscotched across WhatsApp department chats
No shared guest profile across hotel, restaurant, stables and SPA
Legacy booking tool covered only part of the estate
Facilities / engineering work lived in chat - tickets got lost
Marketing had no clean data for timely offers

Before: siloed resource booking - strong for one vertical, weak as a club-wide OS.

What we did

Audit of 7 departments -> Bitrix24 Box as the digital core -> pipelines, smart processes and guest automations

Map the estate

Workshopped hotel, F&B, equestrian, SPA, rentals, events and facilities - who owns each request and what "done" means.

10+ service pipelines

Built dedicated CRM funnels per service line with shared contacts, so a corporate stay + banquet + rides stay one guest story.

Ops smart processes

Boarding horses, vet journal, feed intake, and a facilities ticket board with photo reports - out of Excel and chat.

Guest journey automation

Payment links, passport form before check-in, day-before reminders, post-stay feedback - wired with Bitrix24 + RoboREST.

CoPilot: call transcript + summary landed on the deal for the next shift.

Automated guest messages: booking confirm, check-in day, stay memo with offers.

Built with RoboREST + Bitrix24

Native pipelines and smart processes for structure; robots, cron and a widget for the logic that chat could never keep

Booking & payment stages

Robot · activity. On unpaid booking deadlines, moves the deal to cancel-hold, tasks the manager, and stops silent drop-offs between call centre and hotel.

Day-before check-in digest

Cron · daily. Finds stays arriving tomorrow, sends the guest memo, and creates a prep task for housekeepers and front desk.

Guest services panel

Widget · deal card. Shows stay dates, open add-ons (rides, SPA, restaurant) and last guest message - so cross-sell is visible without leaving the card.

Before & after

Same estate, same services - one operating system instead of a dozen chats

Before

5-7 WhatsApp chats per complex request
Guest history lost between shifts
Near-zero structured cross-sell
Facilities work invisible until someone chased it
No estate-wide load view for leadership

After

10+ service pipelines + shared contacts
Call summaries and stay memos on the deal
Automated payment / check-in / feedback steps
Facilities tickets with photo reports on a kanban
One portal for 50+ frontline and back-office staff

Staff web form -> facilities kanban (New -> In progress -> Done).

After: one portal - CRM, tasks, and department workgroups.

How we measured

Figures compare manager self-reported weekly hours on hand-offs and the count of live service pipelines / portal users after core go-live.

Routine time (-40%): call-centre and hotel managers' hours/week spent forwarding and chasing requests (week 4 vs pre-launch average).
10+ pipelines: count of active CRM funnels covering guest-facing services.
50+ staff: active portal users across front desk, F&B, equestrian, SPA, events and facilities.

About the client (anonymised): a country resort complex with ~20 wooden cottages, multi-hall restaurant, equestrian centre, SPA, bowling, rentals and outdoor events - seven operating units, one guest journey.

FAQ

Questions buyers ask when hospitality ops outgrow chat and niche booking tools

Can Bitrix24 CRM run hotel, restaurant and SPA together?

Yes. Use separate CRM pipelines (or smart processes) that share contacts and companies. Hotel stays, restaurant banquets, equestrian bookings and SPA appointments stay linked to one guest profile while each team keeps its own stages, fields and owners.

How do you set up multiple Bitrix24 pipelines for a multi-service resort?

Map each guest-facing service line to its own deal pipeline - hotel, restaurant, events, SPA, rentals, equestrian and so on - then share the contact record. Sales tunnels or robots can copy or hand off related deals between departments without retyping guest data. In this case we ran 10+ live funnels.

Can Bitrix24 replace WhatsApp for hotel and resort operations?

For internal hand-offs, yes as the system of record: every guest request becomes a CRM deal or facilities ticket with an owner and stage, and notifications replace "check the Hotel chat". Keep informal chat if useful; connect WhatsApp Business to Contact Center when guest-facing threads must land on the CRM timeline.

Is Bitrix24 a hotel PMS or a CRM?

Bitrix24 is the guest relationship and operations layer - pipelines, tasks, portal, automation - not a full property-management system for room inventory. Many resorts keep a PMS or legacy booking tool for stock and use Bitrix24 for sales, guest journey and cross-department work; later bridging via API or 1C is a separate scope. We chose Box when deeper process control and a future PMS/1C bridge mattered.

Where does RoboREST fit vs native Bitrix24 automation?

Native robots cover many stage rules. RoboREST adds custom payment/cancel logic, scheduled digests (day-before check-in, recurring maintenance tickets) and deal-card widgets - without shipping a separate custom PHP module on the portal.

How long does a multi-department hospitality Bitrix24 rollout take?

For ~50 staff and 7 departments, a phased 2-4 months is typical: audit and pilot pipelines first (hotel + inquiries), then remaining services, facilities tickets and guest automations. Core live here was about 3 months. Launching every department on day one usually fails adoption.

Running hospitality on chats?

We help hospitality and multi-service teams put Bitrix24 at the centre - pipelines, portals and RoboREST automation from audit to go-live.

Why contact us?

✓Free consultation and project assessment
✓Response within 24 hours
✓8+ years of Bitrix24 expertise
✓Support in English, Spanish, and Russian
✓GDPR-aware solutions for EU businesses

Email b24@msite.top

Phone +34 614 33 27 85

CRM form will load here