How To: Registration - Customer Journey

Elise Fletcher
Elise Fletcher
  • Updated


Steps to set up the customer journey for the Registration process. 


  • Create a Tenant
  • Create a Event 


Step 1: Create User Account

Delegate must first create a User Account.

Once the delegate has created their account, they will receive a Trigger Notification, thanking them for creating an account, and prompting them to continue the journey and Register.

The Trigger Notification is register_account. You will need to ensure this is enabled for users to receive this email. 

It is worthwhile including a hyperlink in the email to the Registration page.

Step 2: Register Now

The next step for the Delegate is to Register.

On the Home Page of the Platform, a Register button is usually positioned in at least one of three places:

  • In the Top Menu
  • As a Button on top of the Home Page Hero
  • In the Left Side Menu



When the Delegate clicks this button, it will take them to the Registration Intro page.

URL slug is /registrations/page/intro


This page typically includes information such as;

  • The date registration opens and closes
  • A short and sharp summary/synopsis of the event
  • The registration options/categories
  • Any deadlines
  • Any workshop capacities
  • Pricing (often broken down in a table)
  • A link to FAQs
  • A link to the Contact Us page

And finally, a Register Now button at the bottom, to allow the delegate to continue the process.


Step 3: Delegate Group Types (optional)

Where applicable, delegates will proceed to Step 3 if the platform is using Delegate Type Groups.

Common examples of Delegate Type Groups are;

  • Member
  • Non-Member
  • Government/Corporate
  • Not For Profit

The delegate would select the group applicable to them.

URL slug is /registrations/page/type_groups


Step 4: Delegate Type 

Delegates proceed to select their Delegate Type.

Each of the Delegate Types will be listed, their descriptions (if you have input descriptions), and their corresponding fees.

Common examples of Delegate Types are;

  • Full Access/Registration
  • Day 1 Only
  • Day 2 Only
  • Etc..

The delegate would select the type applicable to them.

URL slug is /registrations/page/type if the delegate group step does not exist.

URL slug is /registrations/page/type?group=id if the delegate group step does exist.


Step 5: Add Ons (optional)

Delegates proceed to select any Add Ons.

This is commonly used to allow delegates to register for specific Session/Workshop (they can tick multiple if they want).

URL slug is /registrations/page/addons



  • It’s not a foolproof system, so we tend to avoid offering it to clients.
  • The major functionality flaw is we don’t currently have the ability to set capacity limits. Therefore, clients would need to manually check the backend to see how many they’re up to, and then shut off registrations accordingly.


Step 6: Registration Details (Optional)

Delegates proceed to fill out their details.

Clients can choose to add this step if they’d like to collect information not already gathered by the User Account fields.

URL slug is /registrations/page/custom_page



  • For the mandatory fields with drop-down boxes, it can be handy to add a generic first option such as “Please Select” or “Please Specify”. This is a good fail-safe just in case the delegate skips it, and by default, the option is something not applicable to them – a generic incomplete response would be better than incorrect information.
  • For example, if the delegate skips the Pronoun step below, they will by default submit “She/Her” as their response.


Step 7: Registration Confirmation (Summary of Registration Details)

The delegate then arrives on the Confirmation page. It includes a summary of what they are purchasing.

This is where they can insert a discount code if applicable (they would insert the code, then click “Verify” to apply it – the total price will update accordingly).

URL slug is /registrations/page/confirm


Step 8: Complete Payment

The delegate then proceeds to complete their billing details and selects their payment method.

URL slug is /registrations/page/payment



  • With Credit Card payments, the delegate is charged a 1.75% credit card admin fee.


  • If a delegate comes through on Helpdesk and is struggling to complete this page, it is often because they haven’t selected their Country.




  • In the screenshot above, the Platform Specialists have hidden “stripe” with CSS. It can cause confusion because it looks like a duplication/another option.


Once the delegate has completed payment via;

  • Credit Card, they will receive the Trigger Notification
    • registration_invoice_paid_notifier with their receipt attached
  • Invoice, they will receive the Trigger Notification;
    • registration_invoice_confirm_notifier with the invoice to be paid attached
    • registration_invoice_paid_notifier when payment has been confirmed as received, with their receipt attached

Step 9: Registration Finish

This page is the final step and is shown to delegates when they have completed their registration. It will thank them etc., and prompts them to return to the Home Page.

URL slug is /registrations/page/finish


One the Customer/User/Delegate/Attendee has stepped through all of the above steps, they will have a completed registration 

Further Reading



Please sign in to leave a comment.