Put it in the workflow
Render the form as real controls in a drawer, card, settings route, or post-action state instead of sending people to another site.
- Your route and layout
- Keyboard and focus continuity
- No iframe resize boundary
In-app feedback
Put a short feedback form on the route where the experience happened. Keep your product's UI and account context; Fillo handles the form rules and response workflow.
Inside /settings/billing
Pass coarse route and account context explicitly, then review the score and note together in the response workspace.
Render the form as real controls in a drawer, card, settings route, or post-action state instead of sending people to another site.
Attach the product context you already know so the team can understand the answer without asking the respondent to repeat it.
Review feedback with files and delivery state, export it, or send signed events into the systems that own follow-up.
Yes. Your server can sign respondent identity and traits for the SDK. Use that context for attribution and review, never as a substitute for your app's authorization checks.
Yes. Restyle the default renderer, replace individual fields, or compose the whole layout from Fillo's headless hooks.
No. Fillo collects structured answers and keeps them with response context. Keep behavioral events, cohorts, and session analysis in your product analytics tool.
Yes. Conditional visibility can reveal a follow-up from the same schema the server validates.
Start with the schema and route you need. Review the generated form before it goes live, then test the exact path a respondent will use.
Build a feedback form