It is time for all the latest updates in FG Funnels from the week of August 1st through August 8th, 2024. If you have questions about any of these updates, or FG Funnels in general, please reach out to [email protected] or live chat in the app and our team will be happy to help.
Communities
New payment methods, paid into free course, weekly subscriptions, and group status change
Enhancements:
New Payment methods available: For euro currency in stripe integration new payment methods of sepa debit , ideal & banconnect are now available to make group and course payments.
Paid course to free courses conversion: The issue of paid course not being converted into a free one is now fixed
Weekly subscription options: Weekly subscription option is now available for group subscriptions too.
Group Status Change: Fixed the issue where users were not able to mark groups active/inactive.
New Groups not visible on builder side: Fixed Bug of newly created groups not visible immediately on builder side
Group List not refreshing: Fixed issue with group list not updating with change in location
Invite Via email flow fixes: Now user cannot re-accept the invite link, it will be expired after the user joins the group
Android Webview Issue fix: Fixed the issue where opening community magic link from another app didn’t redirect the user properly to communities in mobile view.
Aspect ratio fixes: GIF, Attachment preview and thumbnails dimensions and aspect ratio fixes.
What’s next:
Chats
Transfer group owner
Gamification workflow actions/triggers
Sub-Account Dashboard
New Widgets: Average Sales Duration, Total Sales Value, and Sales Velocity
What’s New?
We are thrilled to introduce a powerful new widget designed to enhance your sales efficiency, now available under general widgets on your dashboard. Here’s what you can look forward to:
Average Sales Duration: Monitor the average time taken for all opportunities to close, helping you identify areas for improvement.
Total Sales Value: Keep track of the total value of your sales to measure overall performance.
Sales Velocity: Measure the speed of your sales processes to ensure efficiency and quick conversions.
These metrics are filterable by users, providing more granular insights into individual performance and allowing for better tracking and optimization of your sales processes.
Automations
New GPT Models
We have introduced 2 new models in the GPT action along side 3.5 Turbo and 4 Turbo.
4o – Most advanced and efficient
4o mini – Affordable & Intelligent
How to use:
Click the “+” icon and search for “GPT powered by OpenAI”
Click on the “Model” field and select the model of your choice
Pricing:
GPT 4o mini and GPT 3.5 Turbo – $0.015 per execution
GPT 4o and GPT 4 Turbo – $0.03 per execution
Points to be noted:
The default value for the models will be GPT 4o
The “History” feature will work with the three GPT 4 models and not with GPT 3.5
History for GPT actions (AI Memory Key)
The GPT action in workflows can now retain and utilize history, enabling it to produce more relevant and personalized responses based on past interactions.
There are 5 types of History that can be stored:
This Sub Account – Remembers all GPT conversation across all workflows in the sub account where the History type is “This Sub Account”
This Workflow – Remembers all GPT conversation within the workflow where the History type is “This Workflow”
Per Execution – Remembers all GPT conversation within the workflow for a single execution where the History type is “Per Execution”
This Step – Remembers all GPT conversation for the specific action across multiple executions where the History type is “This Step”
Custom – Let’s the user create a custom History type that can be used within the same workflow or multiple workflows
How to use:
Enable the option in Labs
Select the “GPT Powered By OpenAI” action
Switch on “Enable history”
Select the “History for” from the dropdown
Add system instructions
Advanced Options:
System Instructions – User can add Instructions if required to give more information to GPT action to get more specific and desired output.
Exclude instructions from history – This toggle can be used when user wants to exclude the System Instructions from the “history”
Exclude responses from history – If this is turned on then responses of this action will not be stored in the history. This is useful when the responses are sentiment (positive or negative) or any analytics that were received as output.
Important Note: If Enable History is switched on then by default GPT 4 models will be selected.
New Workflow Statuses For Invoices
You can now filter your workflows for invoices with new statuses:
Viewed
Partially Paid
Void
How to use:
Head over to Workflows
Add filters to the Invoice trigger based on the condition that you want
Configure different action items using if/else conditions based on these filters
E-Commerce Stores
Packing Slips
Store owners can now streamline their order fulfillment process by generating shipping labels and packing slips for any e-commerce store order. This new feature allows you to print labels for entire orders or for specific items during fulfillment. The generated labels and slips will include:
Order ID
Order Date
Store Name
Shipping Address & Billing Address
Itemized List of Products with:
Variant Name
Product Image
Quantities
Sender’s Address (Store Address)
How to use:
Store owners can access the print shipping labels or packing slips feature at: Payments > Orders > Select any Store order > “Print Packing Slips”.
Packing Slips can be generated from two places:
Order details page: Click the “Print Packing Slips” button to download a PDF with all unfulfilled and fulfilled orders on separate pages.
Fulfillment of order: During fulfillment, selected items and quantities will be listed, and clicking the “Print packing slips” button will generate the packing slips for those items.
Notes:
Packing slips can only be generated for e-commerce store orders.
For orders with multiple partial fulfillments, each fulfillment will list the items on a separate page when generating shipping labels.
Currently, the billing and shipping addresses are the same on packing slips. This will be editable once the billing address field is released on the checkout page.
Documents & Contracts
UX Bug Fixes
Signature shrinkage issue – Whenever a document had multiple signature elements of different sizes, the signature inside it used to shrink in size – making it hard to read. The issue has now been resolved.
Issue with page size in PDF – (8.5 by 12 instead of standard 8.5 by 11): The document in editor and viewer was created on 8.5 by 11 inch size but the PDF generation was happening according to a 8.5 by 12 inch size. The discrepancy has now been resolved.
Document status issue on Contact Page – Discrepancy in status shown on Contact page and Document Dashboard is now resolved.
Date field strike out in PDF – Dates would strike off whenever a document was being downloaded. This is now fixed.
UX Improvements – Template Builder
While creating a template, whenever a fillable field was dragged it could only be assigned to the creator of the template or left unassigned. Now, this will be shown as assigned to a Contact.
How to use:
Head over to the template builder within Documents and Contracts
Fetch a fillable element from the element drawer: Signature, Text field etc.
By default, the element will be assigned to Contact
While using this template in a workflow, the contact in that workflow is dynamically assigned to it.
Calendars
Razorpay In Calendar Payments
In addition to Stripe, Authorize.net and NMI, users can now integrate Razorpay to collect payments for their bookings.
How to use:
Integrate Razorpay under Payments>Integrations.
Once integrated, go to the Payments > Integrations tab and set Razorpay as your default payment provider.
Navigate to Calendar Settings and turn on the Accept Payments option.
Enter the desired payment amount for bookings and click Save.
Important Notes:
If you are using any currency other than INR, only the ‘Card’ payment option will be available on the booking widget.
Wallet, Net Banking, and UPI options are supported only in INR.
Email Systems
Email Thread Handling
Replies used to create new emails instead of threading under the original message. This is now fixed! All replies will be correctly threaded under the original message in the inbox.
Email Bot Detection
This feature identifies and mitigates the impact of bots interacting with emails. When a bot is detected opening or clicking an email, the following actions are taken:
Preventing Statistics Increment – The email open or click counter will not increment, ensuring engagement metrics reflect only genuine user interactions.
Preventing Automation Execution – Any automation events triggered by email opens or clicks will not execute if a bot is detected, maintaining the integrity of automated workflows.
By default, the Bot Detection Preventing Statistics Increment and Automation Execution feature is turned off. Navigate to Settings -> Business Profile, under the “General Section” you will find the settings to enable and disable the settings.
Conversation AI
Enhancements to our web crawler training for multiple languages
We are excited to introduce enhancements to our web crawler training for multiple languages, including Hindi, Urdu and others.
Key Update: Training Chunking
Previously, chunking was based on a limit of 400 tokens to maintain context. Starting today, we will also support chunking based on word count. If the token count for a chunk exceeds 400, we will now chunk based on word count, with a current limit set at 200 words.
Benefits:
Improved support for different languages
Enhanced context maintenance
Enhanced Responses Handling
What’s New?
We’ve addressed an issue where some users received confusing messages containing tool names instead of the expected Q&A responses.
The Problem: In certain instances, OpenAI mistakenly included the tool name in the content field rather than in the tool_calls object. This led to users seeing unexpected tool names in their chat conversations, particularly during the QnA action.
The Solution: We’ve implemented a fix that uses a regex match to detect these cases and ensures the conversation follows the correct branch. The tool name will no longer appear in outbound messages. This improvement is specifically for custom user-defined branches in the “Conversation QnA” action.
