The narrator explains how to build an email list and get more leads using ManyChat's system. When someone enters the Messenger flow, it greets them by name and tells them about a specific offer, like a compliance guidebook. It asks them to enter their email to receive the offer, noting it will also send related promotions.
The email is saved to ManyChat's built-in system to send emails. If they don't respond within 2 hours, it checks if they are still interested. If not, it lets them request the offer later with a keyword. If they do provide their email, it confirms the offer was sent and then automatically sends them the offer email. The email contains a button to access the offer, like a PDF guidebook hosted somewhere.
The narrator also notes that if leads are coming from Facebook ads, an additional opt-in needs to be added in the flow. There are also tips on retrying if the contact enters an invalid email, and a recommendation to include a "by the way" message with a relevant YouTube video for those not wanting the offer.
Here is a condensed summary of the main points from the text in HTML format:
The narrator wanted to share YouTube videos with chatbot users but many chat platforms don't allow video embedding. The options were to send large video files which caused slow load times or simply link to YouTube videos, neither of which were satisfactory.
Chatbot Builder AI allows embedding YouTube and other videos directly into chats using the video's embed code. The narrator demonstrates going to YouTube, getting the embed code, and pasting it into a Chatbot Builder AI chat flow. The video then shows properly embedded and playable within the chat.
Benefits include no file size limits, views count towards YouTube view counts, and it works across messaging platforms like Facebook Messenger and Instagram where Chatbot Builder is available. The narrator calls this a "game changer" compared to legacy chatbot platforms with restrictions.
The narrator invites viewers to check out Chatbot Builder and to like and subscribe for more chatbot videos in English and Spanish.
The narrator states that you can use Chapot Builder to check if someone commenting on your Instagram posts actually follows you. This allows you to target your responses and grow your following faster.
In Chapot Builder, go to Conditions and select "Follows business on Instagram" to check if a commenter is a follower. If yes, send them one message. If no, send them a different message encouraging them to follow you to enter a contest or access exclusive content.
There is also a free Grow Your Instagram template in the Chapot Builder GPT store that has this follower checking flow already built. You just customize the messages. This ensures you comply with Meta's rules.
By checking if commenters follow you, you can identify and target potential new followers instead of responding blindly. Use this power wisely to grow your Instagram following.
Here is a condensed summary of the main points from the text in HTML format:
The narrator shows how to use Chatbot Builder to set up an AI assistant to manage comments on a Facebook business page. This allows the AI to reply to comments so the business owner doesn't have to manually respond to every comment.
Key steps include:
The goal is to have the AI assistant manage interactions and reply to commenters directly so the business owner doesn't have to.
ChatbotBuilder.ai has three types of fields for storing data: custom fields, account fields, and system fields.
Custom fields store individual user data, like answers to qualifying questions. The get user data element captures user input to save to custom fields.
Account fields store bot-level data that doesn't change between users, like business contact info or number of tickets left. Useful for templates.
System fields store data specific platforms provide, like email and phone number from Messenger. Essential but less flexible than custom fields. To export system field data, first save it to a custom field.
The key is picking the right field type for your needs. Custom fields for per-user data, account fields for bot-wide data, and system fields to tap built-in platform data.