Inbox

Gmail is where your attention lives; Snap is where the work happens. The inbox closes that gap: client emails and the studio’s own activity — bookings, contracts, payments, gallery deliveries — sit in one stream, so nothing waits silently in a mail folder you never open.

One timeline per client

Pick any item and the reading pane opens the conversation behind it: the client’s emails interleaved with compact event cards — “Booking rescheduled”, “Invoice paid”, “Client opened their gallery for the first time” — each with a one-click deep link to the booking, project or gallery it refers to. A client who signs a contract, replies to your email and opens their gallery weaves all three into one story you can read in ten seconds.

Opening a conversation marks its notifications read — the same rule Linear uses. Nothing is deleted by reading: the underlying booking, contract or invoice keeps its own full history on its project.

Reading email, safely

Client emails render inside a locked sandbox with scripts dead by policy, on a forced white card that never inherits your app theme. Two behaviors you’ll notice:

• Remote images stay blocked until you click Load remote images on that message — the tracking pixel an email carries never fires by default.
• Quoted history collapses. The “On … wrote” walls and signature blocks hide behind a Show trimmed content toggle — the text is still stored in full, just out of your way.

Replying

Replies send from the thread’s own address — a private t-…@snaphq.app endpoint minted per conversation, with your contact address as Reply-To — so the client’s answer threads straight back into the same conversation even if every header is stripped, and never into a no-reply void.

• Saved replies (your email snippets) resolve their merge fields for the client you’re writing to, then drop into the composer.
• The + Gallery link button inserts the client’s gallery link — v1 replies don’t carry file attachments, and a live link beats a 20 MB zip anyway.
• Your business signature (legal name, address, phone, website — whatever you’ve filled in under Settings → General) is appended automatically.
• Send a copy to your own inbox is on by default: while you build trust in the Snap inbox, every reply also lands in your regular mail, searchable and forwarded like any other email you’ve sent.

If an email fails to go out, the reply is still saved on the thread with a warning and a retry — failures are never silent.

What lands here

The toggles under Settings → Notifications decide which events mint inbox notifications — turn a branch off (say, gallery activity) and neither the email nor the inbox item appears. The stream refreshes as you work: on opening the page, when you come back to the tab, and every 30 seconds.

Triage at speed

The list has four tabs. All is everything open; Unread is what you haven’t seen; Needs reply narrows to conversations where the client spoke last; Needs triage holds the odd ones — events that matched no conversation yet. The Filter menu (press F) slices the stream by kind — emails, bookings, contracts, payments, galleries, inquiries — and the search box covers titles and previews. The divider between the list and the conversation drags to whatever split suits your screen (double-click resets it), and Snap remembers your choice.

The inbox is built to be driven from the keyboard, Linear-style: j/k move the selection, Enter opens (or closes) the conversation, U toggles read, H snoozes, Backspace deletes — Alt+U marks everything read, Shift+Backspace clears everything read, and ⌘K opens the command menu. Press ? any time for the full sheet.

Snooze hides an item until a moment you pick — later today, tomorrow morning, next week, or a custom time — then it resurfaces unread. Nothing is lost: the underlying lead, booking or invoice keeps its own history whatever you do here, and the sidebar’s Inbox badge always equals your open unread items, mirrored into the browser tab title so a backgrounded tab still signals.

How replies find their thread

Emails are messy: some clients strip headers, Outlook ignores the standard threading fields, and forwards arrive wearing someone else’s envelope. Snap’s inbound pipeline resolves every reply through five signals in order — the standard In-Reply-To/References chain, Snap’s own thread header, Outlook’s Thread-Index, the unique per-conversation reply address your mail now carries, and finally a normalized subject match with the same client within 45 days. Anything that survives all five lands under Needs triage instead of vanishing.

Two safety nets while the inbox is young. Reply mirroring (Settings → Notifications) drops a copy of every client reply into your own mail — tagged with X-Snap headers so you can filter them — and you can switch it off once the inbox is home. And mail over 25 MiB is politely refused with a note to share via a gallery link instead. Tracking pixels are stripped from stored email on arrival; remote images stay click-to-load.