Clear support routes for beta visitors.

Support entry points are visible early so households know where to report a bug, request a feature, or check known issues.

General support

Keep support practical.

During beta, support should focus on what went wrong, what the household expected, and what context is needed to reproduce the issue without collecting sensitive family details or anything unrelated to the problem.

Beta guidance

Set expectations clearly.

ListLink is still in beta preparation, so known limitations, unfinished flows, and temporary rough edges should be easy for early testers to find before they submit a new report.

Response flow

Separate bugs from ideas.

Clear routes for bugs, feature requests, and known issues will make the beta feedback loop easier to follow as support opens up.

Support route

Request a Feature

Share what would make ListLink more useful for your household as feature feedback opens up.

Visit page

Support route

Report a Bug

Use the bug report route to flag issues, rough edges, or confusing behavior during testing.

Visit page

Support route

Known Issues

Check expected beta limitations, active fixes, and temporary workarounds before filing a report.

Visit page