Have you considered other UI elements (and placement) than a floating action button? FABs are intended often as the primary action on a page. Task completion is the primary focus, feedback is tertiary at best here.
Are you relying on a feedback button as the sole means to understand what's not working in the UI, or do you also have access to user testing and observation? You can also use tools to track interactions like Google Tag Manager.
If a user is focused on giving feedback, it often means they cannot complete a task.
Caution about breaking convention on patterns (and user expectation)
You're using a Material component which is often used for the creation (or addition) of new entities.
With Material's prominence across applications, you're competing with patterns that are reinforced by the widespread use of basic UI elements providing functions (primary actions for an FAB) that are different than what you're using it for in your example.
Users are building up expectations about what these elements do.
Only one floating action button is recommended per screen to represent the most common action.
Floating action buttons are used for a promoted action.
Your current application
In your example above, it appears you have a step through. The focus is on getting them through the sequence of actions, creating a focus that keeps them on task.
As you have it right now, Feedback has more contrast and prominence than the other buttons on screen, and looks the most active.
A Material alternative: in the navbar
From the material guidelines: help & feedback
This lumps help & feedback together:
To make it easier for users to find help for urgent issues, such as payments and refunds, place a Help icon in the app bar.
Desktop applications may also place a Help icon in the app bar, as there is more space in the desktop UI.
Here's an example from Google Cloud application; in the upper right in the navbar. It's always visible, yet doesn't distract from any other actions.
Here's a chat app example, with icon plus text: