Share product ideas and upvotes with our product team
We really need comments from users regarding articles, not just emotional feedback. We wante to know the exact reason why they leave a good/bad rate.
From inside a live knowledge article, a way to navigate directly to the editor for this article would be incredibly helpful to speed up small adjustments eg., spelling mistakes, etc. When a link is provided to an article when a correction is required, clicking through to the editor would greatly speed up workflows.
To allow my team to view their current weeks metrics to make sure they are on target, I would like to see a week to date preset date range filter, in a similar fashion as the existing month to date filter.
Requirement - 'I want to': Analyse conversation content in bulk using AI integration to identify themes and trends.End Result - 'So that': We can improve our help centre for Fin and make product enhancements through our ongoing product development.Action - 'When I do this': Access a function similar to Kraftful within Intercom, without needing to work with an API.Result - 'This Happens': The system automatically identifies trends and themes in conversations, eliminating the need for manual tagging by CS agents, which is often inaccurate or incomplete.
Context:Quite often our customers switch between channels when we talk with them, between chat and email. So, when they reach out via chat and we respond, sometimes they’ve already left and our response gets sent to them by email. When we close that conversation and CSAT is sent out to them, the CSAT email doesn’t have any context or “recap” of the conversation we’ve had with them, and skews the customer’s thoughts when leaving CSAT - typically we get comments like “not received a response” or “no one messaged me back” because they’ve missed our actual response to their query and only seen the CSAT survey. We’ve played around with the timings of CSAT surveys, but I feel there’s a more intuitive way of reminding customers. Suggestion:It would be great if a recap could be sent along with the CSAT survey to remind the customer of how the conversation went, even if it was the last reply from our agents. E.g. “Here’s a recap of your conversation!” or “Here’s the last response from [Company name]:” and then offer the CSAT survey.
Hello,Requesting the ability to easily exclude a conversation from data reporting in order to reflect a more accurate score/time on the dashboard.There may be a reason why a particular conversation should not be reflecting in the number shown.Currently in order to exclude and get new data, you have to pull the export, remove the item you don’t want and manually re-calculate the dashboard numbers for instance calculating a new first response time.If there was a way to check a box or similar to exclude from reporting that would be so helpful!Thank you for your consideration.
I would like to be able to add custom away options that meet the needs of our business. For instance, there is no bathroom/restroom option, but should be.
In an outbound series, it would be nice to log that an event happened so that the conditions can work with it.For example, when I want to log when the last time was we sent out a specific interview invitation to a user so that I can omit the user from another series or re-enrollment to the same series.
We can’t call customers and then transfer them. This means when we get voicemails after hours, we have to ask our customers to call us back themselves in order for us to get them to the right place.
With multilingual Fin, users can engage with the bot in multiple languages. However, when asking to talk to a support rep speaking a different language, it’d be beneficial for that support rep to quickly gain an understanding of what has been discussed before getting back to the user.
Although FIN supports Dutch as a language, you are not able translate a text in a conversation into dutch using the AI tool. It seems more like it has been forgotten, so please add Dutch here. Thanks!
It would be helpful to have a workflow condition based on when a CSAT was last completed that we can use to limit how frequently a customer is being asked to fill out a CSAT. The nature of our company/platform often leads to multiple conversations & inquiries from the same customer per day/week and we ideally want to avoid bombarding them with CSAT requests.Ideally something like this condition that is available for surveys so we can ensure customers aren't getting a CSAT form more than once per day/week, etc.:
It appears that there is no API endpoint that provides information about the admin’s profile language.It would be great if the /me endpoint included the admin’s language preference in the response body.
We’re a platform for collecting and reporting ESG data. While the platform interface is only available in English, we have a global user base. To make support as accessible as possible, I activated multilingual Fin in the most common languages spoken by our users. However, our help center materials are still only available in English due to resource constraints.Since the platform interface is in English, it’s crucial that users are guided using the original terms for sections, buttons, and actions. For instance, if our article on inviting colleagues says, “Go to the Configurations page and click Add colleagues,” it’s important that Fin doesn’t translate those terms. Currently, if a Swedish user interacts with Fin, they might be instructed to navigate to “Inställningar” and click “Bjud in kollegor,” which could cause confusion. It would be incredibly helpful if we could flag specific words or phrases as non-translatable within Fin (e.g., when writing help articles).
We have implemented multilingual Fin to support our users in 13 different languages. We’ve customized the welcome message for each language, but cannot customize the message sent when Fin closes the conversation or hands over to a support rep. For customizing the handover process to a human support rep, there are two main advantages:Managing language expectations:We’ve enabled multilingual Fin for 13 commonly spoken languages among our users. However, our support team doesn’t cover all these languages fluently. For instance:We've added Hindi support but don’t have Hindi-speaking reps. It would be beneficial to inform users during handover that our responses will be in English. For German, while we don’t have dedicated support reps, our German-speaking Customer Success Managers can assist depending on availability. In such cases, the handover message could inform users that they’ll hear back in either English or German.Setting expectations during holidays or other high-demand periods:With the holiday season approaching, response times may be longer due to limited staffing. The ability to customize the handover message would allow us to set clear expectations, such as specifying expected delays or providing alternative resources for immediate help.
The request is to have the ability to lock specific ‘Views’ which can only be edited by people with the required access to edit. We’re requesting this enhancement to ensure someone does not remove any details from one of our largest Views.
At the moment, I cannot use reusable workflows within worflows that get triggered at the creation of a backoffice ticket. I want that.
How now SLA works if you applying SLA not one time:As example priority of a ticket raisedOr the Ticket was reevaluatedIf a new SLA is applied later in a conversation and it is different from any previous SLA, the timer will start from the most recent user message, not from the beginning of the Conversation. For instance, if a user message at 20:30 triggers a new SLA, the timer for this SLA will start from that message at 20:30. It's important to note that if the same SLA is reapplied, the timer does not restart but continues from where it left off, adding the elapsed time from the previous SLA to the current one 😄For me correct way would be to always count SLA from time when customer has contacted at least in Tickets
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.