Product support
Include the page URL, approximate time, browser, expected result, and what happened.
Email product support →Questions, product feedback, support issues, partnership ideas, and early-team conversations all start here.

All messages currently route through the CapyCue support team.
Include the page URL, approximate time, browser, expected result, and what happened.
Email product support →Describe the repeated workflow, who needs the walkthrough, and what your current solution gets wrong.
Share product feedback →Tell us about your team, use case, expected volume, integration context, or partnership idea.
Start a business conversation →A useful report does not need passwords, API keys, payment details, or private customer content.
A walkthrough URL or processing request ID is useful. Credentials and raw access tokens are not.
Tell us where the workflow stopped and whether retrying changed the result.
If enhancement fails, do not delete the local draft or source recording while support investigates.
Send the context you have and the outcome you need—we will take it from there.