Challenge
Guest interest was spread across too many entry points
BCC's guests can arrive from Facebook, Instagram, website visits, comments, booking questions, and payment-related follow-ups. Each channel can carry a different kind of intent: a quick room question, a promo inquiry, an event request, a payment confirmation, or a niche question about what the club offers.
The risk is not only slow response time. It is inconsistency. If answers about rooms, inclusions, payment instructions, promos, or policies depend on whoever happens to reply, the guest experience becomes harder to trust.
Because the project is still in build after kickoff, we are not claiming outcome metrics yet. The public story is the scope: a cleaner guest engagement system that BCC can launch, train, and improve from real conversations.
Solution
Strata Connect, a public website, and a booking/payment path
The build combines three surfaces that need to work together: BCC's public website, Strata Connect across guest-facing channels, and the booking/payment support flow. The website gives guests a clearer place to understand rooms, amenities, dining, events, promos, FAQs, and contact options.
Strata Connect answers approved guest questions across Facebook, Instagram, website chat, and supported public comments. It can share images, links, quick replies, booking paths, payment instructions, and relevant context when the channel supports it.
For booking and payment support, the system can guide guests through the next step, collect references or proof for BCC review, and hand off conversations that require human confirmation or judgment. Payment support is framed as gateway and reference workflow support, not Bscale holding or reconciling guest funds.
- AI agents trained on BCC-approved room, amenity, promo, policy, and booking knowledge
- Facebook Messenger, Instagram DM, website chatbot, and supported public comment handling
- Booking inquiry routing and payment gateway support
- Reference collection and manual review workflow for BCC staff
- Unified inbox with tagging, staff assignment, notes, search, and escalation status
Build Status
In implementation after kickoff
The BCC implementation is currently in build. The responsible way to publish it is as an implementation story: what is being built, why it matters, and which guest workflows the system is designed to support.
Once BCC is live and the team has real usage data, this page can be updated with outcome metrics, staff feedback, and any approved testimonial. Until then, the copy avoids performance claims.
Have a workflow like this?
Know what to build before you spend on custom software.
Bring us one messy process. We'll map the bottlenecks, quick wins, and what should stay human, get automated, or become software.