How can we help?

Check the user exists in Supabase → Authentication → Users, and that it was created with Auto Confirm User ticked. Passwords are case-sensitive; you can reset one from the same screen.

Use the publishable key (sb_publishable_…) or, on older projects, the legacy anon key — from Project Settings → API Keys. Handover refuses secret and service role keys on purpose: they give full access to your database and must never be in a browser.

Supabase → Authentication → Sign In / Providers → turn off Allow new users to sign up → Save. Otherwise anyone could create an account in your project and read your conversations.

That's expected. When you click Save & grant access, Handover asks for access to exactly two addresses: your Supabase project and your n8n webhook. Nothing else.

Check your n8n workflow is saving messages: open Supabase → Table Editor → conversations. If rows are there and the panel is empty, make sure you ran schema.sql in the same project the extension is connected to. If the table is empty, the workflow isn't active yet or no customer has written since setup.

Your reply was saved, but n8n didn't accept it. Click Test connection to check the webhook is active and the secret matches, then click Retry under the message — Retry never sends it twice.

• 401 — the webhook secret in Handover doesn't match the one in your workflow.
• 404 — you used the n8n Test URL, or the workflow is inactive. Use the Production URL.
• 502 — n8n received it but the chat platform refused it (on WhatsApp: usually the 24-hour rule).

Your workflow needs the IF node that checks the conversation's mode before the AI agent runs — when it's human, the bot must stop. See step 3 of the setup guide. The ready-made workflows already include it.

Yes. Attach a file or paste a screenshot into the reply box. Images are stored in the chat-media bucket in your Supabase project and delivered by your workflow.

Click You in the conversation header so it switches back to Bot. The bot answers the customer's next message.

The n8n HTTP nodes are using the publishable key. The workflow needs the secret key (sb_secret_…), sent only as the apikey header — never in Handover itself.

Invalid JWT: the secret key was sent as Authorization: Bearer; use a Header Auth credential named apikey instead. Invalid API key: the key belongs to a different Supabase project than the URL.

Usually the knowledge base is empty or too small, or the same file was uploaded several times. Upload your FAQ, product list and policies, and remove duplicates (see MIGRATIONS.md in the workflow download).

The workflow isn't active, or another workflow uses the same bot — Telegram allows only one active trigger per bot.

Allow notifications for Chrome in your operating system's settings (and check Focus / Do Not Disturb). Handover doesn't announce the backlog when you first connect — only new messages after that.

The number of unread conversations. It turns red when a customer is waiting for a person.

In Supabase → Authentication → Users: Add user to add someone (tick Auto Confirm User), delete the user to remove them.

Click Settings in the panel footer, or right-click the Handover icon → Options. Saving updates the open panel immediately.

Chrome and other Chromium browsers with side panel support, including Microsoft Edge and Brave.

In your Gumroad receipt email and on the download page after purchase. Can't find it? Email us from the address you bought with.

Standard (free) is a Telegram AI bot with a knowledge base and human handover. Pro ($19) adds voice notes, photos, business hours, auto hand-back, alerts, a weekly report and leads. Pro Multichannel ($49) adds WhatsApp, Instagram and Messenger.

Run one extra SQL file (3-pro.sql), import the Pro workflow, and deactivate Standard. Your conversations, knowledge base and Handover setup stay as they are.

Yes — email your Pro receipt to namicilab@gmail.com and we'll send you the upgrade code.

Yes, within 30 days of purchase. Reply to your Gumroad receipt or email us.

No. Handover has no server. Conversations stay in your own Supabase project and replies go through your own n8n workflow. See the privacy policy.

Click Sign out in the panel and uninstall the extension — that deletes all extension storage. Your conversations remain in your Supabase project under your control.