- Welcome to the Knowledge Base
- Supported browsers
- Landing Pages
- HTML Editor
- Welcome Messages & Bulletins
- Exporting Data
- Multi Language
- Notifications & Reminders
- Forecasts & Quotas
- Introduction to Importing
- Preparing your Import Data
- Workbooks Import Wizard
- Managing your Imports
- Introduction to Marketing
- Mailing Lists
- Marketing Campaigns
- Upload Library
Workbooks Web Insights
- Tracking Code
- Setting up the Plugin
- Viewing Web Insights Data on your Form Layouts
- Domain Names and Online Activities
- 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
- GatorMail Integration
- Creditsafe Integration
- People & Organisations
Electronic Signing Tools
- People, Organisations & Cases with DocuSign
- Setting up the DocuSign Integration
- Taking Payments with DocuSign
- Creating a Document with a DocuSign Template
- Creating a Document with a Workbooks PDF
- Managing DocuSign Documents
- Adobe Sign Integration
- Docusign Integration
- Introduction to Reporting
- Using Reports
- Exporting Reports
- Advanced Reporting
- Compliance Record
- Data Enrichment
- Introduction to Transaction Documents
- Credit Notes
- Customer Orders
- Supplier Orders
- Contract Management
- 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
- Outlook Connector
- Exchange Server Sync
- Workbooks Mobile Client
- 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
Tickets are generated automatically once a Product has been selected and purchased through the Portal.
Once the purchase has been completed the Attendees are able to start populating the information on their Tickets from within the Portal; providing information such as the Attendee’s name, Job Title, Employer and any additional information you may require such as dietary requirements.
Note: Tickets can also be created or edited within Workbooks if for example a sale was made over the phone or you were asked to amend / update tickets.
You can create a Ticket from the Tickets tab of the Event or Session by selecting Add Ticket.
Once the Ticket has been created a unique Ticket code will also be created, which can then be used to check in attendees at the event. This is used to confirm that they are eligible to attend and that they have attended. This can be followed up by the Sales & Marketing Team as a part of post campaign management.
Like Sponsors and Speakers, Tickets have customisable Form Layouts so new Fields can be added to the Ticket that may be more appropriate to the Events you are running.
Person: This needs to include at least the basic information required in order to create an attendee’s badge, however if an email address is provided then the Process will look up People and Leads and relate the Ticket to them.
Event: The name of the Event that the Ticket entitles the User to access.
Product: The Product they have purchased, such as General Admission or seats at a table
Badge: The Information under the Badge section can then be printed out to form your Attendee’s badge information. This contains general information about the Attendee such as Name, Job title, their Employer and can even include a photo.
Dietary Requirements: If you are providing catering at the event you will need to be sure that you are catering for all Attendees’ dietary requirements. This is a Standard Picklist called “Dietary Requirements” which is unrestricted so new values can be added in the Portal.
Accessibility requirements: Similar to Dietary requirements, this provides you whether you will need to provide guests with anything specific for their requirements. It is controlled by a Picklist called “Accessibility Requirements”.
Tickets and Product Bundles: If you have created a Product Bundle, once the Product has been purchased a unique Ticket will be created for each attendee. For example if you sell a Product Bundle which is 5 Tickets at a discounted rate, the Bundle will create 5 Tickets and the Attendee can then fill out their information for themselves and the other four people.