A useful customer-facing journey
Present the service, collect relevant trip information and give the guest an appropriate next step.
Island Time BVI · Client Case Study
Connecting search visibility with a live booking workflow.
SEO, custom WordPress plugins and connected workflows for a marine transport business. The work links service discovery with the office process behind booking enquiries, quotes, authorisation and confirmation.
Island Time BVI · Tourism & marine transport · Development, SEO and automation
The business requirement
Support the journey from finding a route to confirming a trip.
A guest needs clear service information and a way to supply travel details. The office then needs to assess the trip, prepare a quote, obtain authorisation, record the payment and issue the confirmation.
The project covered both sides: the website information supporting discovery and the custom tools supporting the operational handoff. The objective was a defined process with usable booking records and clear staff decisions.
An organised office workflow
Keep outbound and return details, pricing, authorisation and confirmation information connected to the booking record.
Delivered scope
Custom development around the operating process.
The core water taxi workflow, Make-to-QuickBooks connection and Evervault authorisation forms were confirmed live in October 2026. The broader ERP/CRM described later remains separate from this production baseline.
Search architecture & content
Service-page structure, metadata, internal links, content production, indexing review and technical performance work supported the website’s search presence.
Booking, quote & confirmation tools
Custom WordPress functionality handles one-way and round-trip information, quote preparation, customer response and travel confirmation.
Make & Google Sheets handoff
Webhook-driven data flows connect booking information with supporting records. Matching by entry identifier determines whether a sheet row is updated or a new record is added.
QuickBooks Online connection
The live workflow connects booking information with configured customer and transaction records in QuickBooks Online, using the agreed mapping and process.
Evervault-connected authorisation
Dedicated authorisation forms support the relevant card-authorisation stage. The office retains responsibility for manually processing the charge and reviewing payment details.
Technical documentation & handover
The handover describes custom modules, field mapping, connected accounts, operating responsibilities, maintenance requirements and the separate development roadmap.
WordPressCustom PHP pluginsWPForms bridgeMakeGoogle SheetsQuickBooks OnlineEvervault
The booking process
Connected stages, with explicit human decisions.
The workflow supports the team’s decisions about pricing, payment and confirmation. Submitting an enquiry is not the same as accepting a quote, authorising a charge or confirming travel.
- 01
Enquiry
Collect contact details, passenger counts and the requested trip arrangements.
- 02
Quote
Prepare and review the appropriate pricing and fees for the trip.
- 03
Authorisation
Complete the relevant authorisation form for the booking.
- 04
Manual charge
The office processes payment and records the agreed payment details.
- 05
Confirmation
Issue the travel confirmation using the reviewed trip and payment information.
The integrations support their configured record and accounting handoffs. This case study does not describe a fully autonomous payment or booking system.
Implementation detail
Represent the trip accurately at each handoff.
The booking tools distinguish outbound and return arrangements, passenger categories and the selected pricing method. That information needs to remain consistent as the office prepares a quote and confirmation.
The same care applies to financial records: separate cash charges, previously included fees and recorded card payments should not be confused or counted twice.
- Separate outbound and return dates, locations and flight details.
- Support per-person and fixed-rate pricing options.
- Represent applicable fees and discounts consistently.
- Distinguish cash land-taxi costs from card charges.
- Match booking records before adding or updating connected data.
Custom WordPress modules
Focused components with different responsibilities.
The handover identifies the custom modules behind the workflow. Listing a component here does not imply that every optional capability or future business use is deployed.
Water taxi paperless booking
Custom booking records, quote and confirmation pages, customer acceptance steps and office notifications. The workflow includes an office relay option for the email process.
WPForms water taxi bridge
A custom bridge normalises submitted enquiry information, creates the booking record and triggers the configured Make and Google Sheets handoff.
Boat charter booking module
Custom functionality supports boat rental and charter enquiries. Its role is distinct from the water taxi workflow; additional payment capabilities depend on their deployment and configuration.
Authorisation forms
Dedicated forms connect the relevant booking operation with Evervault-based authorisation handling. Authorisation and the office’s manual payment action remain separate.
Document collection module
The handover documents a passport-upload component with file-type checks, booking-reference association and restricted administrative access. Sensitive document handling remains an operational maintenance responsibility.
Authorisation and document-handling features require appropriate configuration, access control and ongoing maintenance. This project description is not an independent security audit or a certification of payment compliance.
Search evidence · October 15, 2026
A dated snapshot of the domain’s search footprint.
The supplied Semrush desktop Domain Overview for islandtimebvi.com, with Worldwide selected, reported these rounded figures on October 15, 2026.
1.4KReported organic keywords
7.2KReported backlinks
2.1KReported referring domains
Other snapshot figures: estimated organic traffic 1.8K; Authority Score 23; AI Visibility 16; 23 reported AI mentions; 39 reported cited pages.
These are third-party tool metrics. Estimated traffic is not a measured GA4 session total. Backlink totals describe the observed domain profile, not a verified count of links personally built for this project. AI visibility, mentions and cited pages follow Semrush’s coverage and definitions.
The historical chart shows a larger reported footprint from 2025 than in earlier periods, with subsequent fluctuations. The snapshot also shows downward comparisons for estimated traffic and keywords; its comparison period is not visible. It is presented as dated evidence, not a claim of uninterrupted growth or a new performance result.
Delivery status
Keep production work separate from the wider prototype.
| Area | Status | What that means |
|---|---|---|
| Water taxi booking, quote and confirmation workflow | Live baseline | Confirmed in October 2026; office decisions remain part of the process. |
| Make, Sheets and QuickBooks connection | Live baseline | Configured records and accounting handoffs; not every possible API action. |
| Evervault authorisation forms | Live baseline | Authorisation step; office manually processes payment. |
| Additional custom booking/document modules | Documented components | Responsibilities and deployment details belong in the technical handover. |
| Wider multi-department ERP/CRM | Prototype / roadmap | Local development and future deployment work; not a claim of a live enterprise platform. |
ERP & CRM · Prototype / roadmap
A broader platform was designed as a separate phase.
The handover describes a locally developed ERP/CRM prototype spanning several service departments, administrative views and guest-facing tools. It is distinct from the confirmed live booking integrations.
Remaining work includes staging and database migration, final integration and field mapping, access review and testing before any broader rollout. Prototype features are not presented as production outcomes.
Handover & maintainability
Document how the system should be operated and extended.
A connected workflow needs a technical owner after launch. The handover records the components, dependencies and remaining work so the next person can maintain the established process.
That includes the distinction between an implemented function, an account configuration and a future enhancement. Account access and private operating instructions remain in the internal handover.
- Custom module responsibilities and integration boundaries.
- Field mapping, booking identifiers and record-matching rules.
- Workflow monitoring, error handling and office fallbacks.
- Backup, staging and deployment responsibilities.
- Remaining ERP/CRM work and priorities for the next phase.
Related services
Apply the approach to your own process.
Website & custom functionality
Build the pages and WordPress features around the business process.
Web Design & Development →Workflow & system connections
Scope forms, record handoffs and supported tool integrations.
Automation Workflows →Search & site foundations
Connect useful service information with technical search work.
Technical SEO →Discuss your next project
Connect the website with the work behind the enquiry.
Share your current process and the handoff that needs attention. Let’s define a practical scope for your website, search work or connected workflow.