The Freshworks 360 customer view promises one pane of glass across Freshsales, Freshdesk, Freshchat, and Freshmarketer. Done right, it eliminates the “let me check with another team” pause. Done wrong, it shows you data salad with no insight.
Identity is the foundation
The 360 view aggregates by contact identity. The contact must exist with the same email across products. If the customer is [email protected] in Freshsales and [email protected] in Freshdesk, they are two profiles and the 360 shows half-truth.
Build identity reconciliation rules: match on email, fall back to email domain plus phone. A nightly workflow merges duplicates and updates identifiers.
Without identity discipline, 360 is mostly noise.
Data sources
The view stitches:
- Deals and opportunities (Freshsales).
- Tickets and conversations (Freshdesk).
- Chats and bot interactions (Freshchat).
- Campaigns and engagement (Freshmarketer).
- Custom modules tied to the contact.
Each source is enabled per workspace under the 360 settings. Disable noisy sources for specific roles (sales reps may not need every chat history).
Timeline rendering
Events render in chronological order. Each event has icon, source, summary, and a click-through to the source record.
Performance: rendering 1000+ events is slow. Configure event retention: keep last 90 days in the live view, archive older to a “history” tab loaded on demand.
For long-tenured customers, the live view should show recent activity, not their entire 5-year history.
Custom event types
Beyond default events, push custom events from external systems:
- Product usage (active users, feature adoption).
- Billing events (invoice paid, payment failed).
- NPS responses.
- Onboarding milestones.
Push via the events API. Each event has type, timestamp, summary, link. The 360 view ingests and renders alongside native events.
This is where the 360 view becomes a true customer record, not just a CRM aggregator.
Permissions
Access to 360 honors per-product permissions. A sales rep with Freshsales access but no Freshdesk access sees deals but not tickets. A support agent without Freshsales access sees tickets but not deal history.
For cross-functional roles (CSM), grant access to all sources. For role-specific (BDR), restrict to sources they need.
Filters and search
The 360 view supports filtering by source, by event type, by date. Without filters, a long timeline is overwhelming. Train users to filter to what they care about.
Common filter: “support tickets in last 30 days plus product usage events.” Pre-save as a filter view.
Side panel widgets
The 360 view supports side panel widgets: account health score, churn risk, lifetime value. These are computed from the underlying data and surfaced for quick reference.
Widgets are configurable per role. Sales sees pipeline value; CS sees health score; support sees open tickets.
Mobile
The mobile app shows 360 as a list, not a timeline. Most filtering is restricted. Use mobile for quick lookup (“did this customer have a P1 last week”), not for deep analysis.
Integration with external CDPs
If you use a customer data platform (Segment, Rudderstack, Tealium), push the unified profile into Freshworks via the contacts API. The CDP becomes the source of truth for identity; Freshworks consumes.
This avoids duplicate identity logic in two places.
Reporting on 360 usage
Track:
- Daily active users on the 360 view.
- Average session time on the view.
- Click-through rate from view to source records.
Low usage means the view is not delivering value. Investigate: maybe filters are wrong, maybe data is stale, maybe users find the source apps faster.
What to do this week
Audit your top 10 customer profiles. Confirm each has data from at least 3 sources visible in 360. Fix identity gaps for accounts where data is missing or duplicated.
