Roadmap
Changelog

Have something to say?

Tell Synthflow how they could make the product more useful to you.

Implement Get Call API filtering options

Customer wants to be able to filter and receive partial information from our get call API endpoint. Currently, all calls are returned. They would like to be able to retrieve or filter with a time filter - eg - last 24h of calls only Payment tier: Starter Severity level: 3 - Medium (P3) - Non-critical bugs impacting specific users or minor features with workarounds available.

An Anonymous User 2 days ago

💡 Feature Request

Get call summaries after the call.

Use AI to extract key points from call transcripts. Ensure summaries focus on actionable insights, e.g., customer concerns, follow-ups, and commitments. Payment tier: Enterprise Severity level: 1 - Urgent (P1) - Severe issue that disrupts essential functionality or availability of the service for multiple Users or for one Enterprise customer.

An Anonymous User 3 days ago

💡 Feature Request

Customer needs "From Number" in API to change the number they are calling from

Customer has over 150+ numbers that they cycle through to make sure they never get "Scam likely" On their caller ID, They are heavy API Users and are trying to get this done as soon as possible. Payment tier: Enterprise Severity level: 1 - Urgent (P1) - Severe issue that disrupts essential functionality or availability of the service for multiple Users or for one Enterprise customer.

An Anonymous User 3 days ago

💡 Feature Request

[Feature Request] Allow appointments created via RTB on Widgets to be created for the user

Right now we can attach RTB to Widgets, but the process means that the appointment isn't booked with the actual user 'calling' the widget. In GHL specifically, the appointment is simply created-for and attached to the first contact it can find. We need a way to allow customers to set it up so the widget creates an appointment and attaches it to the email address provided during the call. Payment tier: Enterprise Severity level: 2 - High (P2) - High-impact issues affecting functionality for multiple users, but with available workarounds.

An Anonymous User 3 days ago

💡 Feature Request

[Feature Request] Allow Agency customers to provide additional links

The customer would like to be able to replicate the 'Documentation' link we have (where they can provide a link to their own docs), and expand this to provide a link to their own Zapier app they have created - so when visiting 'Zapier' under 'Deployment', we would display a link to their own Zapier app. Payment tier: Enterprise Severity level: 2 - High (P2) - High-impact issues affecting functionality for multiple users, but with available workarounds.

An Anonymous User 5 days ago

💡 Feature Request

Customer needs to change the phone number they are calling with using the API

The ability to pass a "FromNumber" Variable so that they can assign the From number from their system on Twilio to the assistant to make the calls. Payment tier: Agency Severity level: 1 - Urgent (P1) - Severe issue that disrupts essential functionality or availability of the service for multiple Users or for one Enterprise customer.

An Anonymous User 10 days ago

💡 Feature Request

In Progress

Minutes Usage API for Subaccounts Summary

Enable the ability to retrieve minutes usage per subaccount through the API. Feature API Endpoint for Subaccount Minutes Usage Add an API endpoint or add to an existing endpoint to fetch minutes usage data for individual subaccounts. Justification: This feature will align with the dashboard functionality, providing users with programmatic access to detailed usage data for better account management and reporting.

pate4409 16 days ago

💡 Feature Request

In Progress

API Key UI Improvements

Feature Request: API Key Enhancements Summary Enhance the functionality of API keys by adding the ability to name/describe keys and track their usage. Features Naming and Descriptions for API Keys Allow users to assign names and descriptions to API keys for better identification and organization. Justification: This is a straightforward fix that significantly improves usability. API Key Usage Tracking Provide visibility into the usage of API keys, including details such as: Last used timestamp Justification: This feature helps users manage their keys effectively, reducing uncertainty about key usage and enabling informed decisions on deletion or rotation.

pate4409 16 days ago

💡 Feature Request

[Feature Request] More elegant call ending based on duration limit

Request/message from customer: > I set limit call duration to 2 or 5 mins and when time up, the call was stopped suddenly. Is there anyway I can make the ai agent to hang up the call smoothly at the end of call limit duration instead of a sudden hang up in the middle of conversation with customer? User: zawyvs@gmail.com Payment tier: Growth Severity level: 3 - Medium (P3) - Non-critical bugs impacting specific users or minor features with workarounds available.

An Anonymous User 27 days ago

💡 Feature Request

Desperately Searching For Solutions!!!

Hey all, my team and I are desperately searching for a solution to allow one agent to book into multiple different calendars. (Example: AI receptionist needs to book appointment with different employees for different reasons OR one person might need a 15 minute discovery call, while the other needs a 30 minute consultation.) This seems like such a crucial feature. Does anybody have a solution to this, or is Synthflow just unable to do this??

influx.shops About 1 month ago

2

💡 Feature Request

Enhance Shopify Integration: Cancellation Action Feedback

Hi Synthflow Team, Firstly, I want to commend you on the great work with the Shopify Integration, this is an excellent step forward, and I’m thrilled to see it in action! I recently set up a workflow to Cancel an Order, and while the process worked successfully, I noticed an improvement opportunity. Currently, the action doesn’t check conditions like Fulfillment Status (as far as I’m concerned) or whether the order is already canceled, it just receives the request and acts on it. It would be fantastic if the cancellation action could: Check the fulfillment_status or cancelled_at field before attempting the cancellation. Return feedback indicating: Yes, the cancellation is possible and has been processed. No, the cancellation is not possible because of fulfillment status or prior cancellation. This enhancement would make the workflow much more accurate and user-friendly, allowing to relay precise information to customers. Is this something that could be considered for future updates? Thank you for all your hard work, and I look forward to hearing your thoughts!

ella.edwards About 2 months ago

🐛 Bugs