Forward emails to Atisbo to turn customer feedback into product signals
Forward any email to Atisbo — interview notes, support summaries, customer feedback — and it will be automatically processed as a product signal.
Email forwarding is one inbox with two uses. Use it for broad customer feedback forwarding, and use a narrower filter when a specific sender should become its own kind of evidence — the Google Meet / Gemini transcript setup below is that case.
Prerequisites
- An active Atisbo account
- Access to your corporate email (Gmail, Outlook, or any email client)
Setup
- In Atisbo, go to Settings → Sources
- Find the Email card and click Connect
- Your unique ingestion address appears
- Copy that address — you'll use it to forward emails
That's it. No API keys or additional configuration needed.
Shared Email Forwarding Model
Atisbo email sources all work the same way:
- Atisbo gives you an inbox address
- Your email client forwards matching messages to that inbox
- Atisbo parses the email body and classifies the signal based on its content and format
Generic VoC Email is for customer messages, support summaries, interview notes, and other feedback emails. Google Meet / Gemini uses the same inbox workflow with a narrower Gmail filter for transcript emails from meet-recordings-noreply@google.com. When Atisbo detects the Gemini transcript format, it tags the result as an internal meeting signal instead of treating it like generic customer email.
How to Use
Option 1 — Manual Forwarding
When you receive an email with valuable feedback, simply forward it to your Atisbo address.
Option 2 — Automatic Forwarding (recommended)
Set up a rule in your email client to auto-forward certain messages:
In Gmail:
- Go to Settings → Filters and Blocked Addresses → Create a new filter
- In the From field, enter the sender address (e.g., your support team alias)
- Click Create filter
- Check Forward it to and select your Atisbo address
- Save the filter
In Outlook:
- Go to Settings → Mail → Rules
- Create a new rule with your preferred condition (sender, subject, etc.)
- For the action, select Forward to and enter your Atisbo address
What Atisbo Captures
| Email element | Captured |
|---|---|
| Subject line | Yes — becomes the signal title |
| Email body | Yes — the main content |
Text attachments (.txt, .md) | Yes — processed as text |
| Binary attachments (PDF, images) | No |
| Quoted replies (repeated text in threads) | Automatically removed to avoid duplicates |
Best Practices
- Use descriptive subject lines — the subject becomes the signal title. "Checkout bug on mobile — 3 users this week" is better than "Fwd: RE: RE: issue"
- Forward actual customer emails, not internal summaries. Atisbo extracts more value from the customer's own words
- Set up automatic forwarding rules for your most valuable senders: support alias, NPS surveys, customer success team
- Long email threads work fine — Atisbo automatically separates original content from quoted/repeated text
What NOT to Forward
- Purely administrative emails (invoices, calendar confirmations)
- Newsletters or mass marketing emails
- Emails with sensitive information you don't want processed (financial data, passwords)
Before anything is stored, Atisbo redacts email addresses, phone numbers and national identifiers (SSN, CPF, CURP, DNI, RUT) as well as credit card and IP addresses from the text. Personal names are not redacted — a customer's name inside a quote stays there, because removing it usually destroys the sentence. If a name must not be stored, remove it before forwarding.