Built for travel sales and operations
Connect the channels where clients already write, then run landing, booking, and payments in one platform.
Chat connectors
Instagram, Facebook, Telegram and WhatsApp — plug in every messenger and reply from one TRYOPS inbox without switching apps.
One sales funnel — no duct-taped stack
Site, CRM, Telegram bot, Instagram Direct, Stripe, and analytics in one product. A lead from a seat card, micro-landing, or event lands in a deal with product, UTM, and channel attached — no CRM export, Zapier, or separate billing.
Instagram Direct as a full CRM channel
Inbound Direct messages create or resume a deal; manager replies go from CRM to Instagram. Event and landing CTAs route to an Instagram funnel entry point. Booking platforms offer a link at most; CRMs rarely offer two-way chat tied to offer and funnel.
Visual Telegram funnel editor inside CRM
Canvas blocks: Message, Tag, Pause, If tag, Another funnel; deep-link per published funnel; tags written to the CRM deal. Like SendPulse or ManyChat, but natively tied to deal, product, and sales stages — no separate chatbot subscription.
Stripe payment in Telegram funnel with auto-continue
An inline Pay button creates a Checkout Session on the linked deal; after the webhook the funnel continues on the post-payment branch. Chatbots often take payment but skip automatic CRM stage moves and camp/event context in one deal.
Send payment from deal card to Telegram with link renewal
Manager sets amount in Product, creates a Checkout Session, link goes to the same Telegram CRM chat; cron renews the session for the remainder (~24h). Cuts losses from expired links — rare out of the box in CRM + messenger + Stripe.
Telegram broadcasts by CRM segments from one admin
Broadcast to Telegram with history and CRM audience — no export to email or chat tools. Closes the loop for camp organizers: ads → lead → chat → payment → follow-up and announcements in one tool.
Online payments
Stripe, Mollie, and cash — take deposits and full payments online, or mark cash payments received directly in TRYOPS.
Offer micro-landings with Telegram funnel handoff
Each offer gets a short page at /m/{slug} — auto-filled from the camp card, CTA into a published funnel, and server-side view and click stats (unique and total, per CTA). Landing builders lack CRM-deal and Telegram-scenario links; event platforms lack ad micro-pages per offer.
Tour landing builder
Itinerary, dates, pricing, gallery, and booking CTA — build a branded tour page without code, with SEO and your visual identity.
Isolated language catalogs — not translated cards
Each language (ru / en / pl) is a separate catalog of offers, events, and micro-landings: different products, prices, and slugs per market. Typical i18n is one product with translations; here — separate storefronts for different audiences.
Events module with multichannel funnel CTAs
Public showcase of upcoming and past events; CTAs to Telegram and Instagram (connected channels) with CRM context. Online registration runs through a funnel, not a direct Meet/Zoom link. Event platforms register attendees but lack camp-linked Telegram sales scenarios.
Auto move to “awaiting camp” after full payment
When Stripe closes the deal amount, the deal moves to camp_waiter and the event hits the timeline. CRMs need manual rules or integrations; payment-only tools lack camp-specific stage funnels.
AI Sales
AI Lead Qualifier and AI Sales — reply 24/7 in connected chats, grounded in your product knowledge base, with no made-up answers.
