Sys.email
ChatBot.com

luiza jurczyk

Last update:

Get leads and do more after the chat ends using the email system entity.

There are plenty of situations where email wins the game. Sending confirmations, creating accounts, distributing a newsletter and much more are still situations where we prefer to receive an email to be able to access it in the future, rather than an instant message.

With the email system entity you can quickly create a step in the story that recognizes email addresses entered in the query field. The bot can verify the accuracy of the address and memorize it so you can reuse it within the story or pass it on to your database.

Chatbot example with the sys.email entity

If you run an online shop, you’re definitely aware of how important it is to stay in touch with your clients. You may need to confirm their data, send the delivery tracking code or allow to set up an account. Thanks to the Ask a Question action and sys.email entity you can gather the email address in a few simple steps.

Type double curly brackets ... to trigger the entity window and select the one you you need.

  1. Let’s start from creating a very short story. I named mine Sys.email example to easily identify it on my dashboard. Add two interactions: Select product and Get email.
  2. Add a few products to the Select product interaction using Cards.
  3. Apply the Go to action for the Order button to navigate the user to the next interaction. Remember to complete also User Says fields so users can enter this part of the story.
  4. Go to the Get email interaction. Select Ask a Question action from Bot responses.
  5. As a Validation type choose from the dropdown menu the system entity sys.email. Name the attribute to save the value of the attribute to. Complete the other fields according to your preferences.
  6. Add a Text to the same interaction that will confirm adding the email address. Use two curly brackets to call the attribute. Save your work.
  7. Let’s test our story now.

  8. It looks that our sys.email entity works fine! Good job!

Go to next article arrow_forward