CRM
Detect Contact Role Changes from Outlook Signature Drift and Update Salesforce
Watches inbound Outlook email, parses the sender's signature block, and when the job title differs from the matching Salesforce Contact it updates the role and logs the change.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email arrives in monitored Outlook mailboxOutlook
- ActionExtract sender name, company, and job title from signatureOpenAI
- ActionLook up Salesforce Contact by sender emailSalesforce
- LogicContinue only if parsed title differs from stored Title
- ActionUpdate Contact Title and append change noteSalesforce
- OutputNotify record owner of the detected role changeSalesforce
What it does
This workflow reads the signature of every inbound business email, extracts the sender's name and job title, and compares that title against the linked Salesforce Contact. When the title has changed (a promotion, a lateral move, a new department), it updates the Contact's Title field and writes a note recording the old and new values.
When to use it
Use it when your reps rely on Salesforce titles for routing, sequencing, or org mapping but those titles silently go stale. Email signatures are the most current source of truth a person publishes about themselves, so signature drift is an early signal of a role change you should act on.
How it works
- 1A new email arrives in a monitored Outlook mailbox and fires the trigger.
- 2An OpenAI parsing step extracts the sender name, email, company, and job title from the signature block.
- 3The flow looks up the Salesforce Contact by email address.
- 4A logic step compares the parsed title with the stored Title and continues only when they differ.
- 5Salesforce updates the Contact Title and appends a dated change note.
- 6A summary of the detected role change is delivered to the record owner.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SalesforceAccounts, opportunities, cases.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.