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
Personal Booking Links
Resolving conflicting shift patterns
Staff
Creating staff members
Editing and removing staff members
Creating availability for multi-location staff
Creating and managing staff availability
Configuring availability by method
Services
Creating and editing Services
Configuring the reservation workflow
Categories
Creating service schedules
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
Google Analytics - New Customer Journeys
Using the lead time dashboard
Booking journeys
Appointment automation
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
Events
Branding
How to translate your content
Account Settings & Administration
How to reset or update your JRNI password
Understanding user roles and permissions
Creating and managing user access
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
Release notes
V7.23.0 (July 31 2023)
V7.22.0 (July 24 2023)
V7.21.0 (July 18 2023)
V7.20.0 (July 5 2023)
V7.19.0 (June 29 2023)
V7.18.0 (June 26 2023)
V7.17.0 (June 14 2023)
V7.16.0 (June 8 2023)
V7.15.0 (June 1 2023)
V7.14.0 (June 7 2022)
V7.11.0 (April 24 2023)
V7.10.0 (April 20 2023)
V7.9.0 (April 12 2023)
V7.8.0 (April 5 2023)
V7.7.0 (March 30 2023)
V7.6.0 (March 29 2023)
V7.5.1 (March 20 2023)
V7.5.0 (March 16 2023)
V7.4.0 (March 11 2023)
V7.3.0 (March 9 2023)
V7.2.0 (March 8 2023)
V7.1.0 (March 6 2023)
V7.0.0 (February 9 2023)
Table of Contents
- All Categories
- Connectors & API
- Calendar
- Exchange
- Customize outlook appointment body
Customize outlook appointment body
Updated
by Tara
Emails are triggered upon creation of creation / modification of a booking. Data in the email template is synced with Exchange.
Default template
By default, there is a base email body set up for all new and existing connection. It contains the basic information that clients would expect to see in a confirmation email, which are also synced to Exchange.
This is what the default body looks like using liquid objects:
Subject: {{slot.service.name}} with {{slot.member.name}} Body: Date: {{slot.date}} Time: {{slot.just_time}} Duration: {{slot.duration}} Location: {%- if slot.location.address.single_line != "" -%} {{- slot.location.address.single_line -}} {%- else -%} {{- slot.company.address.single_line -}} {% endif %} Attendee Details: Attendee Name: {{slot.member.name}} Attendee Email: {{slot.member.email}} Attendee Phone: {{slot.member.phone}} Additional Service Details: {%- for space in slot.spaces -%} {%- for question_and_answer in space.booking_question_and_answer_objects -%} {{question_and_answer.name}}: {{question_and_answer.pretty_value}} {%- endfor -%} {%- endfor -%} |
Custom body
Customising email bodies is done through the use of Liquid objects in journey. This allows you to configure what information you would like to send out in emails and what to sync with Exhange, if you need to diverge from the default body.
Start using liquid objects to customise email bodies (link coming soon)