AI agents trained on Microsoft Outlook + ServiceTitan data
When work moves from Microsoft Outlook to ServiceTitan, both systems keep a trail: communication history on one side, job and project history on the other. An agent trained on both learns the whole hand-off, not half of it.
Get matched with buyersFree. No obligation. You approve every step.
We may earn a referral fee from buyers we list. Buyers, not us, pay you, and fees can affect which offers we show. See how we make money.
What happens between Microsoft Outlook and ServiceTitan today
Zapier publishes 2 named templates connecting these two apps (Zapier integration page). In plain terms, the most common hand-offs are:
- A new Microsoft Outlook Calendar updates a ServiceTitan Non Job Appointments.
- A new ServiceTitan Appointment creates a Microsoft Outlook record.
On the Microsoft Outlook side the trail runs through Email, Calendar, Contact, Attachment; on the ServiceTitan side through Project, Booking, Call, Employee.
Beyond this pair, Zapier users most often connect Microsoft Outlook to Google Calendar, Notion, Typeform, and ServiceTitan to Google Calendar, Gmail, Gravity Forms.
What an agent trained across both could do
Each of these needs records from both systems at once:
- Customer messages to jobs. An agent that files each Microsoft Outlook Email against the right ServiceTitan Job and drafts replies that quote the job's real status.
- Schedule clash checks. An agent that reconciles Microsoft Outlook Calendar entries with ServiceTitan Appointment records so double-booked crews are caught before the day starts.
- Paperwork chasing. An agent that spots ServiceTitan Estimate records with no follow-up Microsoft Outlook Email and drafts the chase.
Why buyers pay more for linked histories
Joined Microsoft Outlook and ServiceTitan records let a model see a full workflow, not two disconnected logs. SourceX says it prefers many in-scope systems: a complete application list of five or more, with at least three needed to submit (SourceX seller guidance).
Side by side
| Microsoft Outlook | ServiceTitan |
|---|---|
| Project | |
| Calendar | Booking |
| Contact | Call |
| Attachment | Employee |
| Message | Job or Project Note |
| Reply | Lead Notes |
| Forward Email | Location |
| Attendees | Purchase Order |
| Folder | Estimate |
| Flag | Job |
| Email Importance | Appointment |
| - | Customer Contact |
Buyers that want either side
Buyers that license email, chat and meeting history or construction and field-service records, quoted as published.
Mode buyer
- What they buy
- “Email and calendar, documents, operating records (filtered, agreed copy)”
- Size fit
- Minimums vary by industry (Mode's release: 20 US office staff generally, 10 for accounting, 6 for law firms)
- Closed companies
- Not published
- Payout as published
- “$100K–$5M (Mode's headline; calculator is indicative only)”
Mercor buyer
- What they buy
- “Workflow data from Slack, Teams, Gmail, Confluence and similar tools”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Not published (based on data volume and tools connected)”
Ventra broker
- What they buy
- “Email, chat, tickets, CRM, documents; CAD, video and game files”
- Size fit
- 30+ staff in US, UK or Canada (reported)
- Closed companies
- Not published
- Payout as published
- “$100K–$2M potential deals (reported by AI Data Payout)”
micro1 buyer
- What they buy
- “Operational records: SOPs, process docs, knowledge bases, internal comms, CRM and support history”
- Size fit
- 30+ employees
- Closed companies
- Yes: “Separate program for defunct companies”
- Payout as published
- “$100K–$3M+ (marketed range for approved data packages)”
Turing (Lazarus) buyer
- What they buy
- “Communication, work tracking and operating history; licensed non-exclusively”
- Size fit
- Not published
- Closed companies
- Not published
- Payout as published
- “Revenue share: paid each time the record sells (no fixed price published)”
Pewter broker
- What they buy
- “Email, files and operating records; logistics, accounting, engineering, construction, trades”
- Size fit
- 20+ staff, 3+ years, US
- Closed companies
- Yes: “Any status including closed (reported)”
- Payout as published
- “Brings a written offer from a licensing partner; Pewter's fee is 10% of the license price at close (reported by AI Data Payout)”
Buyer terms are quoted from each program's published page as of 2026-11-16; we don't edit them. How we check them: methodology.
What to strip before licensing
- Personal and HR conversations, direct messages and private channels can be excluded by default.
- Names, emails and phone numbers of staff and customers (PII) are removed or tokenised.
- Recordings and transcripts are de-identified; call-recording consent rules are checked.
- Anything privileged (messages with lawyers) or containing health details is excluded.
- Homeowner and client names, addresses and phone numbers (PII) are removed or tokenised.
- Worker personal data (pay rates, IDs, certifications tied to names) is pseudonymised.
- Photos showing people, licence plates or home interiors are excluded or blurred.
- Payment card and bank details on invoices are stripped; client contracts are checked for confidentiality.
- Buyers de-identify records before training, and you can ask for their method in writing.
- An NDA is signed before any sample leaves your systems.
- You approve the data scope: which systems, which years and which fields.
What it could be worth
- micro1's own estimator API returns about $184,925 for a US company with 30 employees and 3 years of records, and about $239,192 at 50 employees and 5 years (low end of its range). Published calculator output (low end), not a quote Source: micro1 data estimate.
- SourceX's public estimator starts at $50,000 for 50-99 employees and $100,000 for 100-999 employees (low end of each band); 50+ peak full-time employees required. Published band (low end) Source: SourceX estimator.
Buyers price the company's whole dataset: how many systems, how many years and how many people produced it, not a single app. No per-app price exists, and these figures are not a quote or a guarantee.
Sources
- Zapier: Microsoft Outlook + ServiceTitan integrations
- Zapier: Microsoft Outlook
- Zapier: ServiceTitan
- micro1 data estimate
- SourceX estimator
- SourceX seller guidance on in-scope systems (no public URL; summarised)
FAQ
Which Microsoft Outlook and ServiceTitan records connect?
Mostly Email and Calendar records in Microsoft Outlook, and Project and Booking records in ServiceTitan. The agent jobs above (customer messages to jobs, schedule clash checks, paperwork chasing) show how they combine.
Do I need both Microsoft Outlook and ServiceTitan to sell data?
No. Either can be licensed alone, but buyers price the whole company dataset, so linked Microsoft Outlook and ServiceTitan history is usually worth listing together.