Benefits of Connecting Front to Windmill
Connecting Front to Windmill brings customer-facing work into performance conversations — so support, success, and ops teams get recognized for the real work they do every day.- Automatically captures meaningful customer interactions without manual reporting
- Ensures employees get credit for responsiveness, problem-solving, and tone
- Reduces time spent preparing for reviews, calibrations, and promotions
- Provides managers with context for coaching and development conversations
- Makes performance reviews more fair and grounded in actual customer impact
Connected Data
When connected, Windmill securely reads metadata about activity in Front:| Data Type | How Windmill Uses It |
|---|---|
| Message + thread metadata (timestamps, participants, volume) | Tickets solved, follow-through, and workload patterns |
| Conversation assignment + ownership | Attributes work to the correct agent or team member |
| Tags, status changes, and resolution outcomes | Helps surface patterns in problem-solving and support quality |
| Comment / internal note metadata | Adds narrative coaching context without exposing sensitive content |
Windmill does not ingest full message bodies by default. Only metadata and summaries where explicitly approved.
Permissions
Windmill requests read-only access to selected inboxes or teams in Front.| Permission | Purpose |
|---|---|
| Read conversation metadata | To reflect workload, responsiveness, and contribution patterns |
| Read assignment + user ownership | To associate work with the correct employee in Windmill |
| Read tag + status metadata | To surface coaching and performance trends |
| No write access | Windmill never sends messages or modifies conversations in Front |
FAQs
Does Windmill write anything to Front?No. The integration is strictly read-only. How often does Windmill sync data?
Continuously. Interaction context appears in Windmill shortly after it occurs in Front. Is this integration secure?
Yes. All data is encrypted in transit and at rest. Windmill meets SOC 2 security controls and uses least-privilege scoped API access. What happens if an employee transitions roles or leaves?
Their historical contributions remain accessible for context, but Windmill stops associating new activity once they are deactivated.