Product Documentation — Email
Email becomes part of the conversation, not just the inbox.
Meetric adds email as a conversation source alongside meetings and other business conversations. Once connected, relevant email threads are imported into the platform and represented as evolving conversations, giving Meetric the context it needs to connect what happened in meetings with the follow-up, decisions, and relationship-building that happen afterward.
This creates a more complete view of the customer and business conversation — helping teams understand the full story instead of isolated messages or meeting moments. Import controls and blocking rules ensure organizations can decide which email belongs in Meetric and how it should be handled.
Purpose
Email is supported as a conversation source. This document explains what is imported, how users control import behavior, how email appears in Meetric, and how ownership is decided for emails.
1. Configure which email is imported
Select the level of email access that best fits your organization. These settings define which conversations Meetric should consider, while the blocking rules below provide additional ways to narrow the imported content.
- CRM contacts: import a thread only when a recipient is a contact in the connected CRM.
- Known contacts and companies: import threads from people or companies with which the organization has previously had meetings.
- Only external: import messages involving people outside the organization.
- All email: import all messages that are not excluded by blocking rules.
These options define the initial candidate set. Blocking rules can always reduce that set.
When the email integration is enabled, emails are imported shortly after they hit your inbox. It is not possible to import emails that were received before the integration was activated.
2. Apply blocking rules
Use blocking rules to keep irrelevant, sensitive, or automated messages out of Meetric. These rules refine the email scope you selected above, helping your team capture meaningful business conversations while reducing noise and maintaining control over what enters the platform.
Automated email
When enabled, automated messages such as newsletters, bulk mail, and no-reply messages are excluded using common sender addresses, markers, and subject-line patterns.
Custom block rules
Create a rule by selecting an email field and a condition:
| Field | Available conditions |
|---|---|
| Sender | Contains, starts with, ends with, exact match, or regular expression |
| Sender to me | Contains, starts with, ends with, exact match, or regular expression |
| Any participant | Contains, starts with, ends with, exact match, or regular expression |
| Subject | Contains, starts with, ends with, exact match, or regular expression |
| Body | Contains, starts with, ends with, exact match, or regular expression |
Example custom block rules
Use combinations of fields, conditions, and values to exclude common types of email. For example:
| Field | Condition | Example value | What it blocks |
|---|---|---|---|
| Sender | Contains | no-reply | Automated messages from no-reply addresses |
| Sender | Ends with | @newsletter.example | All email sent from a newsletter domain |
| Sender to me | Contains | support@ | Messages addressed to a support inbox or alias |
| Any participant | Ends with | @vendor.example | Threads involving a specific vendor domain |
| Subject | Contains | unsubscribe | Promotional or subscription-related messages |
| Subject | Starts with | Out of office | Automatic out-of-office replies |
| Subject | Exact match | Weekly digest | A recurring digest with a known subject |
| Body | Contains | This is an automated message | Automated messages identified by body text |
| Body | Matches regular expression | (?i)invoice\s+#?[0-9]+ | Invoice messages matching a known pattern |
These are examples only. Choose values that match your organization’s email patterns, and test each rule before enabling it.
Blocked domains
Block messages from specified email domains.
Minimum thread length
Set the minimum number of messages required before Meetric imports a thread. Messages remain outside Meetric until the threshold is reached.
3. Choose deletion behavior
Decide how Meetric should handle an imported conversation if the original email is later deleted from the connected mailbox. This gives your organization control over whether Meetric mirrors the source mailbox or preserves imported conversations as part of the business record.
When a source email is deleted, choose one of these behaviors:
- Also remove it from Meetric: delete the imported conversation when the source message is deleted.
- Keep it as a business record: retain the imported conversation even after the source message is deleted.
4. Test the rules
Before enabling your configuration, use the rule tester to confirm that your settings behave as intended. Enter a sample sender or from-name, subject, and body to see whether the message would be imported or blocked, and adjust your rules before they are applied to live email.
Use the rule tester to enter a sender or from-name, subject, and body. The tester reports whether the sample would be imported or blocked under the current configuration.
5. View imported conversations
Imported email appears in Conversations with other conversation sources. Email is represented as an evolving thread rather than as isolated messages. As the thread evolves, Meetric provides:
- A thread summary
- Topics
- Insights
- Clickable source badges that identify and open the email excerpt used for a summary or insight