Information to Collect Before Configuring Go Operator
Problem
Before Go Operator can be configured, the site must supply branding, contact, legal, payment, booking and membership details. Gathering them in advance stops configuration training stalling.
Resolution
Collect the following from the site
Area What the site must supply Branding Primary, secondary and optional tertiary colour hex codes; logo as PNG or JPEG Customer support Booking and membership help email addresses and phone numbers (one combined set or two separate sets) Legal Stable URLs for privacy policy and terms and conditions; health commitment statement if used Website Home-page URL (tenant URL) and any destination URLs used by buttons or links Direct Debit Company name, trading name, service user number (SUN) and advance-notice days for changes to amount or frequency Payments Gladstone Pay configuration and credentials (supplied through the project manager) Address lookup / bank validation GB Group account username and password, and which licences are held Marketing Consent wording; Google Analytics and Facebook pixel keys if wanted Booking Advance-booking windows, booking and cancellation cut-offs, daily limits, duplicate-booking rules and alert-list rules Memberships Product list, prices, durations, contracts, eligibility, facilities, peak/off-peak rules and which are sold online Communications Approved templates, sender name, links and schedules
Notes
- Memberships sold online are mapped in Operator; see Setting Up Go Join Tag Groups and Mapping Memberships.
- Communications are covered in Gladstone Go and 360 Email Templates.
- Related: Go Branding, Links and Contact Details in Operator; Direct Debit Mandate Details and Bank Validation in Go Operator; Go Book Booking and Cancellation Settings in Operator.