SayspokeSupport

Testing guide

Help test Sayspoke

Thanks for testing. You do not need a checklist or special skills — just use Sayspoke normally and tell us when something feels broken, slow, or confusing. This page covers what to watch for and how to send a report Support can act on fast.

Report something

What to look for

  • Anything that looks broken: overlapping text, buttons off screen, layouts that jump around.
  • Anything that feels wrong: tag suggestions that do not match a post, feeds that repeat, counts that look off.
  • Anything slow: pages that spin for a long time, videos that will not play, uploads that stall.
  • Anything confusing: places where you were not sure what to tap next, or what something meant.
  • Dead ends: buttons or links that do nothing, errors that will not go away.

What to include

  • Device — iPhone 15, Pixel 8, MacBook, Windows PC...
  • Browser — Safari, Chrome, Firefox, Edge...
  • Where it happened — which page or screen; paste the link if you have one.
  • What you did — the taps or clicks right before it happened.
  • A screenshot or screen recording if you can grab one — it is often the fastest way to show the problem.

How to report a bug

Open the support form and pick the topic Bug or broken feature. Optional technical-detail fields will appear — fill in whatever you know, and use the Use this device's info button to fill the device basics in one tap. Nothing there is required.

When you are logged in you can attach up to 3 screenshots or a short screen recording right in the form — often the fastest way to show what went wrong.

For ideas, impressions, and things you wish worked differently, pick Beta feedback instead.

Good to know

  • You can send a report without logging in — you will just need to include your contact email.
  • Logged-in reports get a private support timeline, transcript downloads, and in-app reply notifications.
  • One problem per report is easier to track than a list — send as many reports as you like.
  • If something feels urgent or unsafe, say so in the subject line.