Support

Human replies usually within 48 hours; common questions get an instant automated answer.

Known limitations

Written down on purpose. A tool that hides its edges is harder to trust than one that names them.

My sends fail with "Client network socket disconnected"

Your network is blocking outbound SMTP on ports 465 and 587. Consumer ISPs in some countries and most corporate or hotel networks do this. The app password is fine — the connection never reaches Google. Try another network (phone hotspot works), or ask IT to allow smtp.gmail.com:465. Reply detection reads over IMAP (port 993) and is usually unaffected, so you can still see replies even while sending is blocked.

Why is my open rate lower than the tool I used before?

Because we do not count machine traffic. Apple Mail Privacy Protection pre-fetches pixels, Gmail's image proxy does the same, and corporate security scanners fetch every image before a person sees the mail. Those hits are recorded as events and shown as "possible opens", but they are not counted in the open rate. Expect your number to drop by roughly 30-40% against tools that count every image load — the honest number is the lower one.

What does reply detection actually read?

Only messages from the recipients of your own campaigns, within a 7-day window, using BODY.PEEK so nothing is marked as read. Auto-replies, out-of-office and bulk messages are ignored. Unrelated mail in your inbox is never fetched.

What are the sending limits?

Free: 50 emails/day. Pro: whatever your Gmail account allows — 500/day on @gmail.com, 2,000/day on Google Workspace — with an 80/hour safety throttle. We do not relay through shared servers, so Gmail's ceiling is the real ceiling.

Does it work with Google Workspace accounts?

Yes, same app-password path. If your admin has disabled app passwords for the organisation, the Google page will refuse to create one and the SMTP setup cannot be completed — that is a Workspace policy setting, not something the extension can override.