- Welcome to the Knowledge Base
- Supported browsers
- Landing Pages
- HTML Editor
- Welcome Messages & Bulletins
- Exporting Data
- Multi Language
- Notifications & Reminders
- Workbooks Mobile Client
- Forecasts & Quotas
- Introduction to Importing
- Preparing your Import Data
- Workbooks Import Wizard
- Managing your Imports
- Introduction to Marketing
- Marketing Campaigns
- Mailing Lists
- Upload Library
Workbooks Web Insights
- Tracking Code
- Setting up the Plugin
- Viewing Web Insights Data on your Form Layouts
- Domain Names and Online Activities
- Gator Popup
- Reporting incorrect Leads created through Web Insights
- Reporting on Web Insights data
- Using UTM Values
- Why aren’t Online Activities being created in the database?
- Why is GatorLeads recording online activities in a foreign language?
- Using HubSpot with Workbooks
- Introduction to Event Management
- Enabling the Event Management Module
- Using Event Records
- The Event Management Portal
- Installing the Event Management Portal
- Amending Event Portal Parameters
- Compliance Records
- Setting up the Integration
- Sending Mailshots using GatorMail
- GatorMail - Dynamic Content
- GatorMail Domain Setup
- GatorMail Field Mappings
- Managing your GatorMail Account
- Setting up GatorMail Workflows
Electronic Signing Tools
- DocuSign Functionality
- Setting up the DocuSign Integration
DocuSign - Worked Examples
- DocuSign Example - Taking Payments
- DocuSign Example - Updating Related Records
- Docusign Example - Multiple Document Sends
- DocuSign Example - Creating a Template for Cases
- DocuSign Example - Creating a Template for Organisations
- DocuSign Example - Creating a Template for People
- DocuSign Example - Unified PDF
- DocuSign - Reporting
- Adobe Sign Integration
- Docusign Integration
- Creditsafe Integration
- Introduction to Zapier
- Available Triggers and Actions
- Linking your Workbooks Account to Zapier
Setting up Zaps
- Posted Invoices to Xero Invoices
- Xero payments to Workbooks Tasks
- New Case to Google Drive folder
- New Case to Basecamp Project
- New Workbooks Case to JIRA Ticket
- Jira Issue to new Case
- 123FormBuilder Form Entry to Case
- Eventbrite Attendee to Sales Lead and Task
- Facebook Ad Leads to Sales Leads
- Wufoo Form Entry to Sales Lead
- Posted Credit Note to Task
- Survey Monkey responses to Tasks
- Multistep Zaps
- Exchange Server Sync
- Outlook Connector
People & Organisations
- Introduction to People & Organisations
- De-duplication and Merge
- Using PCA Predict
- Data Enrichment
- Introduction to Reporting
- Using Reports
- Exporting Reports
- Advanced Reporting
- Introduction to Transaction Documents
- Credit Notes
- Customer Orders
- Supplier Orders
- Contract Management
- Introduction to System Administration
Users & Security
- User Groups
- Account Settings
- Licences & Modules
Email & Integration
- Email Settings
- API Keys
- Web to Case and Web to Lead
- Preference Centre
- MailChimp, Constant Contact & dotMailer
- Postcode Lookup
- SharePoint Integration
- Bank Account Validation
- Creating & Modifying Picklists
- Creating Custom Fields
- Report-based Custom Fields
- Record Templates
- Form Layouts
- Customising relationships between parties
- Opportunity Stages
- Custom Records
- PDF Configuration
- Contact Support
- Releases & Roadmap
- Workbooks Glossary
In this section, we will go through each of the sections and their fields on the Event Record, explaining what each of them does and how they are reflected within your Event Portal.
As covered in How to Create Events, the only fields that are populated when you select “Add a blank event” are the Name and Campaign Fields, the rest of the Fields and Tabs can be configured as required.
Name: The name of your Event as it will appear to customers in the Portal.
Sub Header: A single line summary of your Event to help potential registrants understand what the event will be. This will be shown in the Portal. The Portal can be configured to show the Event Dates instead if the Sub Header has been left blank;this is controlled through the Plugin Parameters.
Description: An overview of your Event; this will be pulled through to the Portal and give people an understanding of what you are hosting.
Registration Start & Until: It is possible to control when Tickets can be sold for the event via the Portal. This is useful if you want to cut off registrations in advance of the event so that you can confirm final numbers and plan accordingly, or if you want to publish the Event to start advertising it before the tickets are available. If the fields are left blank, registration will be open for the full duration that the event is published on the Portal.
Published: Once this checkbox has been ticked the Event will be visible on the Event Portal immediately; once the Event has been Published then people are able to view the Event Details, and sign up to your Event if registrations are open.
Agenda: A more detailed overview of what your Event will contain, especially useful if you are hosting an event with multiple separate sessions running at different times in different areas.
Customer type: This Picklist allows you to select the type of Customers that will be coming to your Event, whether they are People, Organisations or both. This then changes the text and fields on the Orders Details page within your Portal, which then controls whether the Orders and Invoices will be made out to individuals or their Employers.
Event Code: Every Event is given a unique Event code. This is used by the Check In Process as an identifier, along with a similar unique identifier on the related Event Tickets, to ensure that people are attending the correct event when being checked in.
Event type: This Picklist is controlled by the Picklist “Event Types” in order to help with the categorisation of Events and help with Reporting.
Own Organisation: The Own Organisation the Event is associated with. This controls which Own Organisation the Transaction Documents are created against later on.
Online: Check this box if your Event is going to be hosted online. This will control the time zone that is displayed in on the portal. In-person events will always display in the timezone of the place where the event is being held, whereas webinars can be attended from anywhere in the world and will therefore be displayed to registrants in their current browser timezone.
Ticket Currency: You are able to choose the Currency that Tickets are paid in. This is useful for Customers hosting international Events. This is the currency that will be used on the portal and must match up to the currency of the Products that are going to be published on the portal. If the currencies do not match, the products will not show on the Portal. Once Transaction Documents have been created for this event (Opportunities, Orders or Invoices), it will not be possible to change the currency.
Event Timezone: Select the time zone that your Event will be hosted in. This will control the time zone that the Event Date and Time will be displayed in on the Portal, to ensure that it shows in the actual time zone of the event and not the timezone of the user’s browser. The time zone picklist is the same as the time zone picklist in your preferences, and displays the capital cities of the countries, not the time zones themselves (except for US time zones, where it is split into Eastern, Central, Mountain and Pacific time). This is so that it can automatically convert between summer time and standard time e.g. GMT and BST.
Start & End Dates: These are the Start & End times of the Event itself, these may differ from the Campaign Start & End Date, especially if you plan to market the Event to your Customers.
Custom CSS: You are able to create your own stylesheet and reference this to use your own colours and font styles to give attendees a seamless transition from your website to the Event Portal. The CSS stylesheet may be something that your IT Team will be able to provide you with, alternatively more information can be found here.
Logo: Upload your company logo to ensure your Event is properly branded
Banner: You are able to upload a Banner which can be used to inform Customers about information such as “Only 100 tickets remaining!”
Wallpaper: The background image that helps keep the Event inline with company branding.
Note: Images will stretch on larger Screens as needed. We recommend testing various resolutions of Logos, Banners and Wallpapers.
Exit URL: Once an attendee has registered and confirmed their details, specify the URL that they will be redirected to, if left blank they will be taken back to the ‘Select Tickets’ page.
Compliance Statement: as a part of your GDPR policy you may want to put out a Compliance Statement as you will be holding attendees’ personal information.
Email Details: The Email address used to send out the Email Templates for this Event. The Email must exist as an Email Account in Workbooks - details on how to set this up can be found on our Knowledge Base.
Email Templates: You are able to create a number of Templates that are sent out after an Attendee has registered. More details on how to create Email Templates is found on our Knowledge Base.
Venue name: Name of the venue that will be hosting your event.
Venue description: A brief summary of the Venue, why you chose to host your event there etc.
Venue directions: Provide attendees directions on how to get to the venue when using various means of travel.
Venue Address: These fields allow you to put in the exact address of your venue, this can then be used with our Mapping Module to determine a map position.
Map Position: For Customers that use our Mapping Module, this field will display the Longitude and Latitude coordinates of the Venue and output the map on the Portal for attendees to see.
This section allows you to decide whether specific ticket information needs to be collected for an Event, as this may not be relevant for all Event Types. Having the checkbox selected for a requirement option will mean that when filling out their Ticket details these options will appear for Attendees to fill in if required.