Using JRNI
Appointments
Calendar overview
Creating appointment bookings
Locating bookings and customers
Blocking out time on the calendar
Rescheduling and canceling bookings
Adding attendees to existing and upcoming bookings
Changing the staff member or resource on an upcoming booking
Creating pre and post appointment questions
Using Check In for appointments
Creating and managing bookings via Call Center
Parent and Child level overview
Locations overview
Resolving conflicting shift patterns
Staff
Creating staff members
Editing and removing staff members
Creating availability for multi-location staff
Creating and managing staff availability
Services
Resources
Analytics
Analytics overview
Using the Basic Dashboard
Using the HQ Dashboard
Using the Appointment Dashboard
Using the Event Dashboard
Using the Conversion Dashboard
Using the Capacity Dashboard
Exploring the library of Dashboards and Reports
Sending, scheduling, and downloading Reports/Dashboards
Creating and modifying a Dashboard
Creating your own Reports
Setting up KPI targets and alerts
Filtering Dashboard and Report data
Using Table Calculations
Drilling down into your data
Virtual Queuing
Overview of JRNI Virtual Queuing
Setting up a virtual queue
Overview of the Concierge page
Setting up and managing a display board
Managing live queues via the Concierge page
How customers can join a live queue
Booking journeys
How to translate your content
Connectors & API
Calendar
Video
CRM
Salesforce
Guide to Salesforce Integration with JRNI
Set up the data sync
Map customers, appointments and events
Link JRNI staff to Salesforce users
Standard and Custom object mapping
Use Studio inside Salesforce
Manage user permissions and profiles
Set up a booking journey in Salesforce
Add BookingBug updates to Chatter
Integrating with Yext for JRNI Appointments
Account Settings & Administration
- All Categories
- Connectors & API
- Calendar
- Exchange
- Configure SSL certificate verification
Configure SSL certificate verification
Updated
by Tara
In versions of Microsoft Exchange Server prior to Exchange Server 2007, a server could be deployed into an organisation and, by default, would not require HTTPS (SSL) for any of its client-server or server-server communications. Network communications would be secured by installing an SSL certificate for the IIS instance on the Exchange Server and use SSL for user access to services such as Outlook Web Access.
However, this was not mandatory and it isn’t unusual to encounter legacy Exchange environments that allow external access over insecure HTTP connections. This option should only be enabled if the Exchange server has the correct SSL certificates, if not this should remain disabled otherwise JRNI will not be able to connect to Exchange.
Log in to Studio. Depending on the hierarchy you should either select Administer Parent or log in to the preferred company, and go to Settings > Integrations on the left side panel. Select Exchange on the left side panel. Click on Add Integration on the right hand side.
Input the Username, Endpoint and Password of the target Exchange server. If the server version is 2013 and up, enter the Autodiscover endpoint. Select the Server Version. Select the Access Type. Select Verify SSL Certificate (this should normally be set to None).