SupportSyndicate + Gmail
Route support emails from Gmail into SupportSyndicate's AI inbox — without leaving your domain.
SupportSyndicate's Gmail integration routes inbound email from any Gmail or Google Workspace address into the SupportSyndicate AI inbox via email forwarding and SMTP relay. Replies go out from your domain (support@yourcompany.com), DKIM and SPF signatures are preserved, and the AI handles first response using your knowledge base — all without requiring a Gmail add-on or changing your email provider.
What data flows between the two systems
Every event, record, and update that passes between SupportSyndicate and Gmail.
Gmail forwards inbound messages from your support address to SupportSyndicate via a forwarding rule. Each email creates a ticket thread with the full HTML body and attachments preserved.
Replies send via SupportSyndicate's SMTP relay using your Google Workspace credentials, so the From address shows support@yourdomain.com.
Reply-to headers are preserved so Gmail and SupportSyndicate threads stay in sync — no duplicate threads or orphaned emails.
Images, PDFs, and file attachments in inbound Gmail messages appear inline in the SupportSyndicate conversation for agent review.
How to set up the Gmail integration
Most teams are live in under 15 minutes. No developer required.
Create a Gmail forwarding rule
In Gmail Settings → Forwarding and POP/IMAP, add SupportSyndicate's inbound email address as a forwarding recipient and confirm the verification code.
Configure reply-from credentials
In SupportSyndicate Dashboard → Integrations → Email → Gmail, add your Google Workspace SMTP credentials and your support@ address as the reply-from.
Verify DKIM and SPF
SupportSyndicate displays a DKIM record to add to your domain's DNS. Once propagated (up to 48 hours), outbound deliverability is verified.
Set AI handling rules
Configure the AI to reply automatically, reply with a confirmation and queue for agent review, or queue silently. Most teams start with AI auto-reply and tune after 7 days.
What teams use this integration for
Team inbox migration from Gmail
Teams managing support from a shared Gmail inbox migrate to SupportSyndicate in under an hour — same email address, same domain, with AI handling first response.
After-hours AI coverage
Outside business hours, the AI replies to inbound Gmail tickets automatically. When agents return, they see a queue of AI-handled conversations and the remaining escalations.
Hiver migration path
Teams leaving Hiver set up Gmail forwarding to SupportSyndicate in minutes. Historical Gmail threads stay as a reference archive; new tickets route to SupportSyndicate from day one.
Multi-address support routing
Route support@, returns@, and billing@ to SupportSyndicate simultaneously, with routing rules that tag and assign each address automatically.
Frequently asked questions
Do I need Google Workspace or does a free Gmail account work?
Both work. Gmail free accounts support email forwarding. Google Workspace accounts additionally allow custom SMTP relay for more reliable outbound delivery and full DKIM/SPF configuration. Free Gmail is fine for getting started.
Will customers notice any change in the From address?
No — replies continue to come from your support@ address. The only visible change to customers is faster first-response times once the AI is handling first replies.
What happens to emails that arrive before I set up forwarding?
Emails that arrived before forwarding was configured stay in Gmail. SupportSyndicate only processes messages forwarded after setup. For historical import, export your Gmail inbox as MBOX and contact our team.