TL;DR: Most inbox sync explainers stop at "connect your Gmail account." This one breaks down the OAuth handshake, reply-thread matching, and CRM write-back sequence that make Evox's two-way sync work, then shows how that architecture cuts email-to-CRM lag to under 2 minutes. You'll also get a direct comparison to how HubSpot and Salesforce handle the same problem.
What two-way inbox sync means and how Evox implements it
Two-way inbox sync means every email sent from your CRM goes to Gmail, and every reply from Gmail comes back to your CRM automatically. No manual logging. No copy-paste. The sync runs in both directions, which is what separates it from one-directional logging tools that capture outbound sends but miss inbound replies entirely.
Most Gmail CRM integrations stop at outbound. Your rep sends a sequence email, the CRM records it, and that's where the trail ends. When the prospect replies, that reply lives in Gmail and nowhere else. Your team has to check two places, and leads fall through the gap.
Evox Gmail sync works differently. When you connect Evox to Gmail via OAuth, Evox monitors your inbox for replies to tracked threads. An inbound reply triggers an automatic write-back to the matching lead record in the CRM. The sync captures reply content, sender, timestamp, and thread ID, not just the subject line. That's a complete conversation record, updated without anyone touching it.
This matters for IT company owners running multi-rep teams. When a lead replies at 11pm, the CRM reflects it by morning, and the rep who picks up the thread has full context. For teams already using Evox for sequenced campaigns, this connects directly to how inbox sync feeds into multi-step email campaigns to reduce response time.
What data Evox automatically captures from Gmail conversations
When Evox connects to Gmail via OAuth, it doesn't just log that an email was sent. Every thread writes a structured record to the CRM automatically. Here's what gets captured:
Sender and recipient addresses — both directions, so inbound replies from leads are logged alongside your outbound messages
Timestamp — sent time and received time, not just the date
Subject line and thread ID — Evox ties every reply to the original thread, so a six-email conversation appears as one continuous record, not six disconnected entries
Reply content — the full body of each message, not a truncated preview
Lead record match — Evox matches the sender's email address to an existing CRM contact automatically; if no match exists, it flags the conversation for manual review rather than silently dropping it
This matters because manual email-to-CRM sync typically introduces a lag of hours or days between a reply landing and a rep seeing it logged. Automated sync removes that gap entirely.
The email reply tracking CRM record also captures open and click events from Evox-sent messages, so the lead's engagement history sits in one place alongside the raw conversation.
What Evox does not capture: Gmail labels, filters, or folder assignments. Those stay local to your inbox. If your team uses labels to triage leads, you'll want to factor that into how you configure the Gmail and Outlook inbox integration before go-live.
For how this two-way inbox sync feeds downstream automation, see how Evox inbox sync connects to multi-step email campaigns.
How to set up and authorize Evox Gmail sync: step-by-step
The entire setup takes under five minutes, and the authorization sequence is the same whether you're connecting a personal Gmail account or a Google Workspace address.
Open Evox settings and navigate to Inbox Sync: From your Evox dashboard, go to Settings > Integrations > Inbox Sync. You'll see Gmail and Outlook listed as available providers. Select Gmail.
Authorize via OAuth: Evox uses Google's standard OAuth 2.0 flow. A Google consent screen opens and asks you to grant two scopes: read access to your inbox and permission to send on your behalf. Both are required for two-way inbox sync to work. Grant both, then return to Evox.
Confirm the inbox connection: Evox will display a green confirmation banner and show your connected address. If it stays on "pending," your Google Workspace admin may have restricted third-party OAuth apps — your IT admin needs to allowlist the Evox app ID in the Google Admin Console before re-authorizing.
Set your sync scope: This is the step most teams skip. By default, Evox syncs only threads that match an existing lead record. If you want Evox to also create new lead records from unmatched inbound emails, toggle "Auto-create leads from unmatched senders" on. Leave it off if you want manual control over new record creation.
Test with a live thread: Send a test email from your connected Gmail account to a lead already in your CRM. Within 60 seconds, that thread should appear logged against the lead record in Evox. If it doesn't, check that your CRM lead record uses the same email domain as the sender.
For a broader walkthrough of connecting Evox to your sales stack, the full Evox setup guide for IT teams covers SMTP configuration and the multi-provider sending infrastructure alongside inbox sync.
How Evox tracks a lead reply from Gmail to CRM record
When a lead replies to one of your campaign emails, here is exactly what happens inside Evox.
Gmail receives the reply and assigns it a thread ID. Evox's two-way inbox sync, running via the Gmail API, picks up that inbound message within minutes. It reads the thread ID, matches it against the outbound message stored in Evox, and identifies the associated lead record.
Once the match confirms, Evox writes the reply back to the CRM automatically. The lead's activity timeline updates with the full message, the timestamp, and the campaign step that triggered the original send. No manual logging. No copy-paste into a notes field.
Here is a concrete example. Your team sends a five-step nurture sequence to 200 IT decision-makers. On day four, a prospect named Sarah replies: "Can we schedule a call this week?" Evox catches that reply, matches it to Sarah's lead record via thread ID, logs the message, and triggers the next automation step — in this case, a task assigned to your rep to book the call. The rep opens Evox and sees the full context: every prior email, every open, and now the reply.
That reply-to-record path is what makes email reply tracking CRM accurate at scale. Without thread-ID matching, replies from forwarded addresses or aliased inboxes break the chain.
For teams running multi-step sequences, how Evox inbox sync feeds into multi-step email campaigns shows how this email to CRM sync triggers downstream steps automatically.
Gmail labels, filters, and folders: what Evox syncs and what it skips
Evox Gmail sync respects thread structure, not Gmail's organizational layer. That distinction matters when you're configuring a Gmail CRM integration and expecting your folder logic to carry over.
Here's what syncs and what doesn't:
What Evox reads and writes:
Email threads, matched by Gmail thread ID
Inbound replies and outbound sends within those threads
Read/unread status on synced threads
Sender and recipient metadata attached to lead records
What Evox skips:
Gmail labels (including custom ones you've built for pipeline stages)
Nested folder structures
Filters that auto-sort incoming mail into sub-folders
Starred or snoozed states
This means a reply that Gmail auto-labels "Prospects Q3" lands in Evox as a plain thread match against the lead record. The label doesn't transfer. If your team relies on Gmail labels to signal deal stage, that logic needs to live in Evox's lead scoring or campaign triggers instead — not in Gmail.
The practical fix: during Evox inbox sync setup, map your existing label categories to Evox tags or pipeline stages. That way both systems stay organized independently, without one breaking the other.
For how synced threads then feed into sequences, see how Evox inbox sync connects to multi-step email campaigns.
Evox Gmail sync vs. HubSpot and Salesforce: the integration comparison matrix
Dimension | Evox | HubSpot Gmail integration | Salesforce email sync |
|---|---|---|---|
Sync direction | Two-way (sent + received) | Two-way, but inbound logging requires BCC or extension | One-way by default; two-way needs Inbox or Einstein add-on |
CRM write-back method | OAuth-authenticated, automatic on reply | Extension-dependent; manual log option available | Requires Einstein Activity Capture or third-party connector |
Setup time | Under 10 minutes via OAuth flow | 15–30 minutes; extension install adds steps | 30–60 minutes minimum; enterprise orgs often longer |
Label/folder support | Reads Gmail labels; maps to Evox pipeline stages | Ignores Gmail labels entirely | Ignores Gmail labels; folder mapping requires custom config |
Reply-thread matching | Matches by thread ID; keeps conversation history intact | Matches by subject line; breaks on subject changes | Matches by Message-ID header; gaps appear with forwarded threads |
Verdict by team size and workflow:
Small IT teams (1–10 reps) who want a working two-way inbox sync without a dedicated admin: Evox fits best. OAuth setup takes one session, and the CRM write-back is automatic.
Mid-market teams already on HubSpot CRM: the Gmail integration works, but plan for the BCC dependency and accept that Gmail labels won't carry over.
Salesforce shops: native email sync is genuinely limited without Einstein Activity Capture. The email to CRM sync gap is real and worth budgeting for.
The core difference is write-back method. Evox uses OAuth to log every reply automatically. The others rely on browser extensions or paid add-ons to close the same gap, which adds setup friction and failure points. If multi-step email campaigns are part of your workflow, that automatic write-back matters more than it looks on a feature list.
Common Evox Gmail sync issues and how to fix them
Four issues account for most Evox Gmail sync problems, and each has a direct fix.
OAuth token expiry is the most common. Gmail's authorization token silently lapses if Evox hasn't sent through that account in 30 days. Fix: reconnect the account under Evox's Gmail and Outlook inbox integration settings and re-authorize the required scopes.
Missing reply threads happen when a lead replies from a different address than the one Evox originally contacted. The email reply tracking CRM logic matches on thread ID, not sender address, so add the alternate address as a secondary contact record to restore matching.
Duplicate lead records appear when a manual CRM import runs after Evox inbox sync has already created the lead. Fix: run the deduplication merge in the CRM before enabling sync, not after.
Label conflicts occur when Gmail filters move outbound Evox emails into a non-inbox folder before sync reads them. Fix: exclude Evox's sending domain from any existing Gmail filters.
For a clean starting point, the full Evox setup guide for IT teams walks through the Evox inbox sync setup sequence that prevents most of these before they start.
Closing
Two-way inbox sync closes the gap between where your reps send emails and where leads reply. With Evox, every inbound reply lands in your CRM within minutes, complete with full thread history and engagement data. Your team stops context-switching between Gmail and your CRM, and leads stop falling through the cracks because a reply sat unlogged overnight. If your team runs Gmail-based sales workflows, you can connect Evox in under 30 minutes and see reply-thread logging active the same day. Ready to start? Head to the Evox Gmail and Outlook inbox feature page to begin the OAuth authorization.
FAQ
What is two-way inbox sync and how is it different from one-way email logging?
Two-way sync captures outbound emails sent from your CRM and automatically logs inbound replies back to the lead record. One-way logging only records what you send, leaving prospect replies stuck in Gmail with no CRM record.
Does Evox Gmail sync work with Google Workspace accounts or only personal Gmail?
Evox works with both personal Gmail and Google Workspace addresses. If your Workspace admin has restricted third-party OAuth apps, they'll need to allowlist the Evox app ID in the Google Admin Console first.
How long does it take to set up Evox Gmail sync?
Setup takes under five minutes. Authorization via OAuth is standard, and reply-thread logging runs automatically once you confirm the connection.
Will Evox sync emails I sent before connecting my Gmail account?
No. Evox syncs only emails sent and received after you authorize the connection. Historical threads remain in Gmail but won't be retroactively logged to CRM records.
What happens if my Gmail OAuth token expires — does sync stop automatically?
Yes. When your OAuth token expires, Evox stops syncing new replies until you re-authorize. Evox will alert you before sync halts so you can refresh the connection.
Can multiple team members connect their Gmail inboxes to the same Evox workspace?
Yes. Each rep can authorize their own Gmail account separately. Evox will match inbound replies to lead records based on thread ID, so multi-rep teams can all sync to the same workspace without conflicts.
Get tactical playbooks every Tuesday
One email. 5-min read. Tactical reads for B2B operators who actually run the business.
Join 48,000+ B2B operators · Unsubscribe anytime
Kayla Morgan is a Growth Marketing Strategist & Automation Expert who has built and scaled marketing engines for SaaS brands and digital agencies across North America and Europe. She writes about campaign automation, audience segmentation, and how businesses can grow their pipeline without growing their headcount.
