CRM KitsCoach tour and group charter operators
Every stop, every seat, counted aboard.
A departure board for coach tour and group charter operators: each departure with its pickup route stop by stop, a manifest kept as head counts with a lead booker, boarding counted at each pickup, the coach and driver recorded for it, the fares each lead booker owes and a trip log once the coach is back. Stepwell never stores passenger names, dates of birth, ID numbers or health details.
See unconfirmed pickups, missing drivers, full coaches and late balances first.
Departures with booked seats over the recorded seat count, a pickup still planned within two days, no driver within three days or a balance past its due date lead. Then the board shows today and the next six days by time, each departure with its pickup route as a line of stops and a manifest block of seats booked, confirmed, held and boarded.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Departures operating view
- Pickups operating view
- Manifests operating view
- Coaches operating view
- Fares operating view
- Trip log operating view
- Insights operating view
- Three native form drafts and three editable document templates
- Editable departure checklists and preserved row history
four pipelines
- Scheduled tour departures · 8 stages
- Group charters · 8 stages
- Pickup point partners · 6 stages
- Group organizers · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- Close the manifest
- Confirm the pickups
- Trip wrap-up
- New charter inquiry
- Quote follow-up
- Head count check
- Departure ready
- New pickup point
- New group organizer
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Group trip inquiry
- Head count update
- Pickup point request
- Departure sheet
- Pickup route card
- Trip confirmation
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 10 fictional departures: six scheduled, one departed, two returned and one cancelled, with 18 pickups and 25 booking parties kept as head counts. Sample edits stay in memory and reset on navigation or reload.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set business name, descriptor and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected departure creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, refuse access codes, logins, card and ID numbers, dates of birth, passenger name lists and health details, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked departure holds the tour name and kind, the organizer and destination, departure and return dates and times, the coach label and recorded seat count, driver and guide, the status, the manifest close date and recorded miles, pickups with time, order and status, booking parties with a lead booker, seats, boarded count, fare, payment and balance due date, and an editable checklist.
Stepwell records what the office planned, booked, confirmed, counted and was paid. It makes no DOT, FMCSA, safety, insurance or on-time claim, does not check driver hours, vehicle records or coach conflicts, and does not plan routes, track vehicles, sell seats or take payments. It is not a passenger list: passenger names, dates of birth, passport and ID numbers, health and mobility details, card numbers, Social Security numbers, and depot or gate codes and passwords are refused in recorded text and in the native form drafts, while tour codes, booking references and coach numbers are kept.
Four optional pipeline templates and nine inactive workflow drafts. 10 fictional in-memory departures.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Bus Tour Operations Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Stepwell keeps its warm-grey route rail across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More hospitality, events & creative kits
Browse all 220 kits
