|
All Flow Steps Explained
|
|
Flow Step
|
Example
|
Description
|
|
|
|
Category: CRM
Description: Used to create another contact within a flow (in addition to the one created at the “Start” step). Only used if you need 2+ contacts for one user.
|
|
|
|
Category: CRM
Description: Used to match contacts in your database based on information from a form (i.e. if two users have the same first + last +name, add this form data to the existing contact)
|
|
|
|
Category: CRM
Description: Used to assign or remove a contact owner. Typically towards the start or end of a flow. Allows you to assign tasks and send communications to a dynamic person (the contact owner instead of a specified person)
|
|
|
|
Category: CRM
Description: Used to create a task for a specific or dynamic person. Often used to assign tasks to Contact Owner or group of people with a given tag (i.e. Sales Team)
|
|
|
|
Category: CRM
Description: Used to increase, decrease, or set the quality and engagement scores of a given contact. Scores can be increased/decreased by a given number or set to a specific number with this step.
|
|
|
|
Category: CRM
Description: Used to check on related tasks (either related to the contact created at the start of the flow or related to the task(s) created inside of the flow), and perform additional actions based on task completion status within a given time.
|
|
|
|
Category: CRM
Description: used to set up a new user account within the system, specifically for managing memberships or customer interactions.This account allows the user to access and utilize the features and functionalities of the CRM system to handle customer data, track interactions, and manage memberships efficiently.
|
|
|
|
Category: CRM
Description: This feature determines what happens if a purchase is made and creates a redundancy for the purchase form type.
|
|
|
|
Category: CRM
Description: This is used to set up a task/opportunity related to your pipeline records. You can set a timeout setting and time measure before moving to the next sequence flow.
|
|
|
|
Category: CRM
Description: This is used to assign a specific team member to the contact recorded in the flow.
|
|
|
|
Category: Data Services
Description: used for adding or attaching additional information to an existing contact entry in a database or system. When you append data to a contact, you are updating or supplementing the existing information with new details. This process is commonly used to keep contact records up to date, ensuring that the most recent and relevant information about a person or entity is available in the database. It is a way to enhance and expand the data associated with a specific contact without creating a new entry from scratch.
|
|
|
|
Category: Data Services
Description: Used for finding out which mobile network provider or carrier is associated with a particular cell phone number. This can be useful for various reasons, such as verifying the carrier for billing purposes, checking compatibility for certain services or promotions, or identifying the network type to ensure proper communication between different carriers.
|
|
|
|
Category: Data Services
Description:This feature allows you to upgrade the blueprint on a certain group of people in a mass update. Implementing or carrying out a pre-defined plan or set of instructions, often in the context of a project or task.
|
|
|
|
Category: Data Services
Description: This feature allows you to create your own API webhook from a third-party provider.
|
|
|
|
Category: Data Services
Description: Allows users to connect various web applications and automate tasks between them. For example, you could use a Zapier Webhook to create an automation where every time a new form submission is received on your website, Zapier sends the form data to a Google Sheet or a CRM tool.
|
|
|
|
Category: Data Services
Description: The same as Zapier, it allows users to connect various web applications and automate workflows without any coding skills. It enables the creation of automated tasks in between apps. Example, you’d like to set up a connection that automatically saves any email attachment from Gmail to a specific Google Drive folder.
|
|
|
|
Category: Data Services
Description: Used to validate a specific integration of a third party system to the CRM system making sure that all data exchanged is accurate and consistent. It also enhances data quality.
|
|
|
|
Category: Data Services
Description: Allows you to monitor any activities you want to track. Pixel fire refers to tracking pixels or code on a website or landing page. When someone visits the website or a page, a signal is sent indicating the website is viewed or an action is taken.
|
|
|
|
Category: Data Services
Description: Allows you to copy an existing system flow as an example.
|
|
|
|
Category: Data Services
Description: Allows you to copy any existing input related to any data file you chose.
|
|
|
|
Category: Data Services
Description: Used to track and report any action to Facebook’s advertising platform. It is used to measure the effectiveness of any campaign or advertisement by placing a snippet of code through a Facebook Pixel added on the website.You can review all this data including other relevant metrics within Facebook Ads Manager.
|
|
|
|
Category: Logic
Description: Tags are the basis for sorting contacts, and can be used as a primer for a lot of other flow steps. Add/remove tag is used to mark a user with a tag that can be used to trigger a flow (or not trigger a flow) at a later time.
|
|
|
|
Category: Logic
Description: Used to assign the contact to additional flows. Typically on the end of another flow. For example, if the contact confirms an appointment through a text sequence, put them on the appointment confirmation flow. This step helps you keep flows separate when one flow may have multiple triggers (i.e. someone can trigger the “Appointment Confirmed” flow either by filling out a form on your website, by calling your IVR, or by sending a series of text messages)
|
|
|
|
Category: Logic
Description: Used to split test flow steps (email/text sequences, assigning the contact to different salespeople, etc). Can also be used in combination with other steps (redirect to URL) to A/B test steps in a funnel. Split tests can either be completely random or based on specified percentages.
|
|
|
|
Category: Logic
Description: Conditions are used to take a contact through different steps based on given criteria. For example, “if {{contact}} has the tag ‘red shirt’ do ____. If they do not have the tag ‘red shirt’ do ____.” Typically relies on contact data.
|
|
|
|
Category: Logic
Description: If normal conditions typically check tags and contact data, this step checks on system data.
|
|
|
|
Category: Logic
Description: Used to run custom JavaScript code in a step
|
|
|
|
Category: Logic
Description: Used to put windows of time between flow steps. The amount of wait time can be a specified amount of time or a specific time on a given date, when used in combination with the date/time field on a form.
|
|
|
|
Category: Logic
Description: Required at the end of every flow. Basically, all roads must lead to Rome (Deactivate Contact From Flow step). Can assign a parameter to this to indicate which reasons the flow ended (i.e. call picked up or went to voicemail)
|
|
|
|
Category: Logic
Description: Used to trigger another step in the same flow
|
|
|
|
Category: Logic
Description: Limits the number of how many records are processed in a flow. The records will queue in this step waiting to continue to the next step. You can also specify the interval for each limit set.
|
|
|
|
Category: Logic
Description: Can be used to create more complicated redirect sequences after form submissions. Typically, FlowTrack forms allow you to show a message or redirect the user to a specified URL. Used in combination with other steps like Random Route / Split Test, you could use this step to A/B test different Thank You pages.
|
|
|
|
Category: Logic
Description: Waits for criteria based on email or text. Can track email views and internal link clicks (in email body). Can track SMS link clicks. Useful for sending reminder texts or for separating engaged and disengaged email contacts in your flow and/or database, before further flow steps.
|
|
|
|
Category: Logic
Description: Used to fire steps based on whether the flow is initiated inside or outside a given time window. For example, if a call comes in during business hours.
|
|
|
|
Category: Logic
Description: Mainly used to create interactive text conversations with contacts. This step waits for a “timeout” (no response), a “no match” (response outside given parameters), or a condition match — in this example, “Time Provided” — (response matches given parameters) to fire additional flow steps.
|
|
|
|
Category: Logic
Description: Allows you to send data or information to external applications or systems through API. Example, after a customer registration, the API output configuration will instantly transmit the information to an email marketing platform, project management tool etc. It’s important that open API integration is available on the 3rd party system.
|
|
|
|
Category: Messaging
Description: Used to send emails to a contact. Has three email builders inside this step: text email builder (sends like a regular gmail email), raw HTML (for advanced use cases), and visual email builder (similar to MailChimp)
|
|
|
|
Category: Messaging
Description: Used to send texts to contacts. Allows for split-testing of message content and links within messages. Can specify times for this step to fire (i.e. only fire on weekdays, or fire daily at 9:00 AM)
|
|
|
|
Category: Messaging
Description: Used to change the opt-in status of a contact to receive marketing emails/texts/calls. Can be used in conjunction with a “Send SMS” or “Send Email” and a “Wait For Email/SMS Click/Open” step to make a double opt-in sequence whenever someone submits a form and checks your opt-in checkbox field.
|
|
|
|
Category: Phone
Description: Used to transfer a caller to a conference room setup within your dashboard. This will make everybody in the conference room’s phone ring.
|
|
|
|
Category: Phone
Description:Used to trigger a process of requesting to have a phone number added to a database that prohibits any telemarketer to contact the number. Once the caller confirms that they don’t want to receive any future marketing calls, then you can use this sequence to confirm the changes.
|
|
|
|
Category: Phone
Description: Used to transfer a call to someone else. Mainly for forwarding calls from call tracking numbers to cell numbers, but can also be used within IVRs to lead callers to the right party.
|
|
|
|
Category: Phone
Description: Used to capture a voice message from a caller. Typically used in conjunction with “Hangup Call” to simulate a missed call (what would happen if you called your cell phone and didn’t pick up).
|
|
|
|
Category: Phone
Description: This allows the caller to leave a rating from the previous call they had.
|
|
|
|
Category: Phone
Description: This is used for creating a welcome message or other recorded message depending on the client’s request.
|
|
|
|
Category: Phone
Description: Used to capture any digits from the caller, example the phone number they use.
|
|
|
|
Category: Phone
Description:Used to set up different choices for the caller. You can set specific conditions connected to each branch.
|
|
|
|
Category: Phone
Description: Hangs up the call automatically. Required at the end of a phone flow that does not result in a transferred call.
|
|
|
|
Category: Phone
Description: Once you set an extension for each company team members, you can add their data from here and allow the caller to choose from the directory.
|