In the flow designer, anywhere it is possible to write text (descriptions, titles, buttons, checklists, conditions, etc.), you can use variables that exist in your flow and other advanced variables. If you have a panel where it asks for the person’s name, for example, and the identifier for that information is NAME, you can reference that identifier in any subsequent panel.
FLOW ENVIRONMENT VARIABLES
In addition to the variables you create within the flow, you can also use advanced variables. Let’s start with the flow environment variables.
$FLOWPARAMETER
This variable contains the value that is passed in the URL with “par”. Suppose you are running a paid ad campaign on Facebook and Google at the same time and you want to know the origin of the click. You can include in the URL that calls your conversational site the origin in the parameter “par”. If your URL is https://cs.tyo.ai/meuanuncio, you would have in the Facebook ad https://cs.tyo.ai/meuanuncio?par=FACEBOOK and in the Google ad https://cs.tyo.ai/meuanuncio?par=GOOGLE. In your flow, you can use this variable to add a tag to the lead, for example.
$FLOWSESSION
This variable contains a unique identifier (UID) for the flow session. Each time someone accesses the conversational site, a new session is created. You can control the creation of sessions in the conversational site’s configuration panel. The FLOWSESSION can be used to transfer a session from one conversational site to another (as long as the two conversational sites are in the same account). This is useful when you want the visitor to move to another conversational site, but you want to use the information they provided on the initial site. To use FLOWSESSION, you must create a URL redirection action in your flow and pass the variable with the “ses” parameter. Example: https://cs.tyo.ai/meusite2?ses=$FLOWSESSION.
$FLOWPOINTS
FLOWPOINTS accumulates the number of points that are assigned in the responses of the interactions. It is very useful for making a quiz, for example, and providing a result at the end based on the total points.
CRMDATA VARIABLES
CRMDATA variables are very useful for use in content that needs lead data from the CRM. These variables can even show data that has not yet been effectively saved in the CRM. It is even highly recommended to use CRMDATA whenever possible because of its flexibility.
$CRMDATA.NAME
Contains the full name of the lead when available.
$CRMDATA.FNAME
Contains the first name of the lead when available. Even if you capture the lead’s name with an identifier like NOME, for example, and the lead provides the full name, CRMDATA.FNAME will bring only the first name. This is important for cases where you want to address the lead only by the first name in conversations, emails, etc.
$CRMDATA.LNAME
Contains the last name of the lead when available.
$CRMDATA.EMAIL
Contains the lead’s email when available.
$CRMDATA.PHONE
Contains the lead’s phone number when available.
$CRMDATA.BUSINESS
Contains the lead’s company name when available.
$CRMDATA.ADDRESS
Contains the lead’s address when available.
$CRMDATA.CITY
Contains the lead’s city when available.
$CRMDATA.STATE
Contains the lead’s state when available.
$CRMDATA.ZIPCODE
Contains the lead’s postal code when available.
$CRMDATA.BIRTHDATE
Contains the lead’s full birth date when available.
$CRMDATA.BIRTHDAY
Contains the lead’s day of birth when available.
$CRMDATA.BIRTHMONTH
Contains the lead’s birth month when available.
$CRMDATA.BIRTHYEAR
Contains the lead’s birth year when available.
$CRMDATA.MEMBERNAME
Contains the name of the team member (salesperson or person responsible for the lead) when available.
$CRMDATA.MEMBEREMAIL
Contains the email of the team member (salesperson or person responsible for the lead) when available.
$CRMDATA.MEMBERPHONE
Contains the phone number of the team member (salesperson or person responsible for the lead) when available.
$CRMDATA.QUALITY
Contains the quality of the lead when available.
$CRMDATA.STAGE
Contains the stage of the lead when available.
$CRMDATA.TAGS
Contains the tags associated with the lead when available. The tags will be separated by commas.
$CRMDATA.SNAPSHOT
Contains the summary of the CRM “snapshot” field when available.
$CRMDATA.UID
Contains the unique identifier of the lead when available. This value can be used to pass the lead’s UID to a flow with the “ctt” parameter and avoid having the lead provide contact information again. An example would be when the lead registers in one of your lead capture flows and then you send an email offering to schedule a consultation with you. To schedule the consultation, you will need the lead’s contact details. In this case, in the link you include in the email, the contact’s UID is passed along:
https://cs.tyo.ai/myschedule?ctt=$CRMDATA.UID
When the email is sent, the variable $CRMDATA.UID is replaced by the lead’s identifier and you can include logic in your scheduling flow to check if the lead already exists in the CRM.
In this case, you will have access to all the lead data in the CRM to use in your flow as desired.
TAYON ACCOUNT VARIABLES
Some data from your Tayon account is also available in variables. This information can be useful when you create flows that can be copied to other accounts, such as accounts for agency clients. It is a way to personalize flows with contact details, email signatures, etc., without having to edit the flow after copying it to a new account.
$ACCOUNTNAME
Full name associated with the account.
$ACCOUNTFIRSTNAME
First name associated with the account.
$ACCOUNTLASTNAME
Last name associated with the account.
$ACCOUNTEMAIL
Email associated with the account.
$ACCOUNTPHONE
Phone number associated with the account.
$ACCOUNTSMSCREDITS
Amount of credits available for sending SMS or WhatsApp messages via the official API. It can be used for logic in the flow, such as, if there are not enough credits, do not schedule the sending of the message to avoid sending errors.
UTM VARIABLES
UTM-type variables are sent by advertising platforms such as Google Ads or Facebook Ads (Meta). UTMs are an industry standard and Tayon allows you to receive these values in your conversational sites and use them to add tags or perform other actions with your leads.
The available UTM variables are:
$UTM_SOURCE
$UTM_CAMPAIGN
$UTM_CONTENT
$UTM_MEDIUM
$UTM_TERM
FLOWASSIGNED VARIABLES
FLOWASSIGNED variables represent the data of the Team Member that the lead is associated with. You can use them, for example, to personalize message sending or text panels in your flow.
The available FLOWASSIGNED variables are:
$FLOWASSIGNED.FNAME
Contains the first name of the team member.
$FLOWASSIGNED.LNAME
Contains the last name of the team member.
$FLOWASSIGNED.EMAIL
Contains the email of the team member.
$FLOWASSIGNED.PHONE
Contains the phone number of the team member.