Sayify.pro / Docs
Docs / Product Guides / Troubleshooting

Common issues and solutions for Sayify.pro, plus how to get support.

🛠️ Troubleshooting

Run into an issue? Most problems have a quick fix. Start here — and if you're still stuck, create a support ticket and our team will help you out. 💬

🎙️ Voice Recording Issues

"Microphone not found"

  • Check browser permissions — Click the 🔒 icon in the address bar and make sure microphone access is set to Allow.
  • Check system settings — Ensure your microphone is enabled in your operating system's sound settings.
  • Try a different browser — Chrome and Edge work best. Safari may have limited support.
  • Unplug and replug — If using an external mic, reconnect it and reload the page.

Recording doesn't start

  • HTTPS is required — Browsers block microphone access on insecure (HTTP) pages. Make sure the URL starts with https://.
  • Corporate firewalls — Some firewalls block WebRTC. Check with your IT team if you're on a corporate network.
  • Clear cache and retry — Try clearing your browser cache, then reload the intake page.

Recording quality is poor

  • Use a quiet environment — Background noise significantly impacts transcription accuracy.
  • Position the mic close — Stay within 30 cm of the microphone for best results.
  • Close other apps — Make sure no other application (Zoom, Teams, etc.) is using the microphone at the same time.

Link shows a "Not Found" page

  • Check the slug — Make sure the URL matches the slug you set when creating the link.
  • Check if the link is active — Disabled or archived links won't load for respondents.
  • Verify your subdomain — The full URL should be https://your-company.sayify.pro/i/your-slug.

Respondents see a blank page

  • Check browser compatibility — Sayify requires a modern browser (Chrome, Firefox, Edge, or Safari 15+).
  • Disable ad-blockers — Some aggressive ad-blockers interfere with voice recording scripts.

📊 Dashboard & Inbox

Responses aren't appearing

  • Wait a moment — Audio transcription and AI analysis take a few seconds after submission.
  • Refresh the page — New responses may not appear until you reload the Inbox.
  • Check filters — Make sure you haven't filtered out the status or priority of the incoming response.

AI insights are missing

  • Short recordings — Very brief recordings (under 2 seconds) may not generate meaningful insights.
  • Low clarity audio — If the recording quality is too low, AI analysis may be limited.
  • Processing delay — AI evaluation runs after transcription. Give it 10–15 seconds after submission.

🔗 Webhooks

Webhooks not delivering

  • Check your endpoint — Make sure your server returns a 2xx status code. Non-2xx responses trigger retries.
  • Accept JSON POSTs — Your endpoint must accept POST requests with Content-Type: application/json.
  • Check firewalls — Ensure your server allows incoming requests from Sayify's IP range.
  • Review delivery logs — Go to Webhooks & Integrations in the sidebar and check the delivery status and error details.

Webhook delivering duplicate events

  • Use the Delivery ID — Each delivery includes an X-Sayify-Delivery-Id header. Use it for idempotency checks.
  • Check retry behaviour — If your server responds slowly (>30s), Sayify may timeout and retry. Return 200 immediately and process asynchronously.

🌐 Domain & Branding

Subdomain shows "Not Available"

  • Try a variation — Subdomains must be unique across all Sayify workspaces. Try adding a suffix (e.g. acme-feedback).
  • Check slug format — Only lowercase letters, numbers, and hyphens are allowed. No spaces or special characters.

Logo or favicon not showing

  • Check file format — Logo: PNG, JPG, WebP, or SVG (max 5 MB). Favicon: PNG, ICO, or SVG (max 1 MB).
  • Clear browser cache — Favicons in particular are heavily cached. Try a hard refresh (Ctrl+Shift+R).
  • Wait for propagation — After saving, changes may take a few seconds to appear on live intake pages.

🔑 API

401 Unauthorized

  • Check your API key — Verify it hasn't been revoked or regenerated.
  • Use the Bearer prefix — The header must be: Authorization: Bearer YOUR_API_KEY.
  • Check workspace match — API keys are scoped to a specific workspace.

404 Not Found

  • Check the base URL — All endpoints use https://sayify.pro/api/v1/.
  • Include trailing slashes — Django requires trailing slashes on all endpoints.
  • Verify UUIDs — Make sure the resource UUID exists and belongs to your workspace.

429 Too Many Requests

  • You've hit the rate limit — Wait a few seconds and retry with exponential backoff.
  • Contact support — If you consistently need higher limits, create a support ticket.

🎫 Support Tickets

If the troubleshooting tips above don't solve your problem, create a support ticket and our team will help you directly.

Creating a Ticket

  1. Click the floating support button at the bottom-right of the dashboard, or navigate to /support in the sidebar.
  2. Click + Create Ticket.
  3. Fill in the form:
    • Description — Describe your issue in detail (minimum 10 characters). The more context you give, the faster we can help.
    • Attachments (optional) — Upload up to 4 files (screenshots, error logs, etc.) by clicking or dragging into the upload area.
  4. Click Submit Ticket.

You'll receive a ticket number (e.g. #1042) and be taken to the ticket detail page.

Tracking Your Tickets

Go to Support → Tickets to see all your tickets in a table with:

Column What it shows
Ticket # Unique ticket number — click to open details.
Status Pending → Working In Progress → Completed.
Priority Low, Medium, High, or Urgent — set by the support team.
Messages Count of replies in the conversation thread.
Created When the ticket was created.
SLA Resolution timeline — shows On Track, ⏰ Xh left (at risk), or Breached.

Replying to a Ticket

Open any ticket to see the full conversation thread. You can:

  • Send a reply — Type your message and click Send. Attach files if needed (up to 4 per reply).
  • Download attachments — Click the download button on any attachment from you or the support team.
  • Track status — The current status and priority are always shown at the top.

Our support team responds within the SLA window shown on each ticket.

💡 Quick Tips

  • Search the docs first — Most questions are answered in these docs. Use the search bar at the top to find what you need.
  • Include details in tickets — The more context (screenshots, URLs, error messages), the faster we can resolve your issue.
  • Check browser console — For technical issues, open the browser console (F12) and include any error messages in your ticket.
  • Try another browser — If something isn't working, a quick test in a different browser can help isolate the issue.

🎓 What's Next?

  • Inbox — Learn how to manage and review responses.
  • Webhooks — Set up real-time notifications.
  • Branding — Customise your intake pages.
  • Key Concepts — Review all platform building blocks.
Was this page helpful?
Report an issue →