Capture the problem where it is reported
A customer may report a blank checkout screen in a support conversation long before an engineer files an issue. Connecting feedback sources reduces that handoff. Use the customer's description, reproduction steps, and relevant release context to explain the failure. A text webhook also lets your own form backend send written reports without adding a new support tool.
Connect and verify each source
Set up the provider in repository settings, save the connection, and configure its generated webhook URL in the source tool. Slack uses selected channels; Intercom and Zendesk use supported customer conversation or comment events. Run the supplied connection test to check delivery before enabling the workflow. Keep webhook URLs and signing secrets on the server.
Separate reports from instructions
Incoming feedback is evidence of a possible bug, not an instruction to change the repository. Veratex classifies written reports before starting actionable work. Non-bug messages and reports that cannot be safely classified should not become fix jobs. For useful reports, an agent investigates the code and attempts a patch with review and verification.
Choose review or automatic delivery
Select Wait for human review when you want to inspect new feedback fixes before they merge. Alternatively, use repository auto-merge settings. Automatic delivery still requires verification and merge checks, and repository auto-merge must be enabled. Your deployment pipeline runs after merging. Changing the delivery setting applies to new fix jobs.
Common questions
Does every support message trigger an agent run?
No. The feedback workflow triages incoming written reports and filters messages that are not actionable bugs before creating fix work.
Can I connect a custom feedback form?
Yes. Have your server send JSON to the generated text webhook with a stable report ID and the customer's written text. Keep the webhook URL out of client-side code.
What customer data should I send?
Send only the context needed to understand the bug. Report text may be processed by configured AI providers during investigation, so remove credentials and unnecessary personal information. Review Veratex's privacy policy before connecting a source.
Try it on one repository
Start with a small, well-understood bug and inspect the resulting change. See pricing and usage limits and review our security practices and privacy policy before connecting a source.