Special Rules - Ticket Email to Contact

Overview

Special Rules are pre-built automation features that solve common HubSpot association challenges. Currently, Auto Associations Pro includes one special rule: Ticket Email Address to Contact.

What it does: Automatically creates contacts from ticket conversation email addresses and associates them with the ticket.

When to use it: When you need visibility into all participants in a support ticket conversation, not just the primary contact.

Business value: Complete conversation tracking, better team coordination, improved support context, and automated contact creation.

The Problem

When tickets are created in HubSpot through email conversations, HubSpot only associates the contact from the first email address in the “from” field. This creates several issues:

• CC’d participants are ignored - People in CC don’t get linked to the ticket
• Reply-all threads lose context - Additional participants who join the conversation aren’t tracked
• Manual association required - Support teams must manually link contacts as they appear
• Incomplete conversation history - You can’t see who’s involved in the thread

The Solution

The Ticket Email to Contact special rule monitors conversation threads on tickets and automatically:

1. Extracts all participant email addresses from from, to, cc, and bcc fields
2. Searches for existing contacts in your CRM by email
3. Creates new contacts if they don’t exist (optional behavior)
4. Associates all contacts with the ticket automatically
5. Filters excluded addresses based on regex patterns you configure

How It Works

Step-by-Step Process

1. New Message Arrives: A new message is added to a ticket conversation thread

2. Email Extraction: The system identifies all unique email addresses from:

   • From field
   • To field
   • CC field
   • BCC field
   • All messages in the thread

3. Filtering: Email addresses are checked against your excluded regex patterns

   • Internal addresses like support@yourcompany.com can be filtered out
   • System addresses like noreply@hubspot.com are excluded
   • Patterns are case-insensitive

4. Contact Search: For each remaining email:

   • Search HubSpot for an existing contact with that email
   • If found, use that contact
   • If not found, create a new contact (if configured)

5. Association: All identified contacts are associated with the ticket

6. Visibility: All team members can now see full participant context on the ticket

Configuration

Accessing Special Rules

1. Navigate to Auto Associations Pro settings
2. Find the “Special Rules” section
3. Locate “Ticket Email Address to Contact”

Enable/Disable Toggle

Enabled (On):

• The rule actively monitors all ticket conversations
• New participants are automatically associated
• Works on existing and new tickets

Disabled (Off):

• No automatic association happens
• Existing associations remain unchanged
• You can re-enable at any time

Excluded Email Regex

This field allows you to filter out email addresses you don’t want to become contacts or associations.

Format: Comma-separated regular expressions (case-insensitive)

Example Configuration:

support@, noreply@, no-reply@, donotreply@, @yourcompany\.com

What This Does:

• support@ - Excludes any email starting with “support@” (like support@yourcompany.com)
• noreply@ - Excludes noreply addresses
• no-reply@ - Excludes hyphenated variations
• donotreply@ - Excludes donotreply addresses
• @yourcompany\.com - Excludes all internal company emails

Common Patterns:

Pattern	Matches	Use Case
support@	support@anything.com	Exclude support team addresses
@yourcompany\.com	All company emails	Exclude internal team
noreply	Any noreply variation	Exclude system emails
^admin	Emails starting with “admin”	Exclude admin accounts
bot@	bot@anything.com	Exclude automated senders

Regex Tips:

• Use \. to match literal dots (e.g., @company\.com)
• Use ^ to match the start of the email (e.g., ^support)
• Use $ to match the end (e.g., noreply$)
• Patterns are case-insensitive by default

Use Cases

Multi-Participant Support Tickets

Scenario: Customer emails support and CC’s their entire team. You want all team members visible on the ticket.

Without Special Rule:

• Only the sender gets associated
• CC’d participants are invisible
• Support team has incomplete context

With Special Rule:

• All participants automatically become contacts
• Full team visibility on the ticket
• Support can @mention or contact any participant

Result: Complete conversation tracking and better customer service.

---

Reply-All Email Threads

Scenario: A ticket conversation grows as more people join via reply-all.

Without Special Rule:

• New participants aren’t tracked
• Manual association required for each new person
• Easy to lose track of stakeholders

With Special Rule:

• Every new participant is automatically associated
• Real-time stakeholder tracking
• No manual work required

Result: Effortless multi-party conversation management.

---

Partner/Vendor Support Coordination

Scenario: Support tickets involve both customers and third-party vendors/partners.

Without Special Rule:

• Partner contacts must be manually linked
• Conversation history is fragmented
• Hard to track who’s involved

With Special Rule:

• Partners are automatically associated
• Full visibility into all parties
• Complete communication audit trail

Result: Streamlined multi-party support workflows.

---

Executive Escalations

Scenario: High-priority tickets get escalated with executives CC’d on the thread.

Without Special Rule:

• Executive involvement isn’t tracked
• Support team might not realize they’re watching
• Incomplete escalation records

With Special Rule:

• Executives automatically associated
• Team aware of all stakeholders
• Complete escalation documentation

Result: Better escalation awareness and accountability.

Best Practices

Configure Exclusions Carefully

Do Exclude:

• Internal team email addresses (if you don’t want them as contacts)
• System addresses (noreply@, donotreply@)
• Bot/automation addresses
• Shared mailboxes (support@, info@)

Don’t Exclude:

• Customer email domains (unless they’re all internal)
• Legitimate business contacts
• Partner/vendor addresses you need to track

Start With Broad Exclusions

Begin with obvious system addresses:

noreply@, no-reply@, donotreply@

Then add company-specific patterns as needed:

noreply@, no-reply@, donotreply@, @yourcompany\.com, support@

Test on Existing Tickets

1. Enable the special rule
2. Check a few existing multi-participant tickets
3. Verify expected contacts are being associated
4. Adjust exclusion patterns if needed

Monitor New Associations

• Review newly created contacts weekly
• Check if unwanted addresses are slipping through
• Refine exclusion patterns based on actual data

Document Your Patterns

Keep a record of why each exclusion pattern exists:

noreply@ - System emails
@ourcompany\.com - Internal team
vendor-bot@ - Vendor automation emails

Troubleshooting

Contacts Not Being Created

Check:

• Special rule is enabled (toggle is ON)
• Email addresses aren’t matching exclusion patterns
• Your HubSpot account has permissions to create contacts
• Existing contacts might already exist with those emails

Solution:

• Review exclusion regex for over-matching patterns
• Verify app permissions in HubSpot settings
• Check if contacts already exist manually

---

Too Many Contacts Created

Symptoms:

• System emails becoming contacts (noreply@, etc.)
• Internal team members becoming contacts
• Bot addresses creating contacts

Solution:

• Add exclusion patterns for system addresses
• Test patterns against recent tickets
• Use more specific regex to filter unwanted addresses

---

Existing Contacts Not Associated

Symptoms:

• Contact exists but isn’t linked to ticket
• Email matches but association doesn’t happen

Check:

• Contact email field is exactly the same (no typos)
• Case sensitivity isn’t an issue (should be case-insensitive)
• Association creation succeeded (check app logs if accessible)

Solution:

• Verify email addresses match exactly
• Check HubSpot association limits (unlikely but possible)
• Contact support if issue persists

---

Regex Pattern Not Working

Common Issues:

Wrong: @company.com (matches any character before company)
Right: @company\.com (matches literal dot)

Wrong: support (matches "support" anywhere in email)
Right: ^support@ (matches emails starting with "support@")

Testing Patterns:

• Test regex online at regex101.com
• Use the “i” flag for case-insensitive matching
• Start simple and add complexity as needed

Advanced Configuration

Complex Exclusion Patterns

Exclude multiple domains and prefixes:

noreply@, donotreply@, @(company1|company2|company3)\.com, ^(support|admin|bot)@

This excludes:

• noreply@ and donotreply@ addresses
• All addresses from company1.com, company2.com, company3.com
• Addresses starting with support@, admin@, or bot@

Domain-Specific Rules

Exclude all subdomains of a domain:

@.*\.yourcompany\.com, @yourcompany\.com

This excludes:

• subdomain.yourcompany.com
• yourcompany.com
• any.subdomain.yourcompany.com

Getting Help

If you need assistance with configuration:

• Email: contact@daeda.tech