Front
Support
Front holds the shared inbox a support or account team works through, thread by thread. Revenue Labs reads those threads and turns them into an account-health read, so a pattern of complaints or praise shows up before a renewal conversation starts.
Website
Customer Health·12 health states updated overnight
Reading Renshaw Textiles… ›
TriggerHealth signal · Renshaw Textiles - crosses into Average · flagged 7:38 AM
Deploy agentDeploying Customer Health agent on Renshaw Textiles' evidence
Use skillLoading skills · Customer Health Assessment · Value Realisation Assessment · Customer Risk Assessment
Reference memoryReading memory · Customer Health · Value Realisation · Customer Risk
ReasoningRenshaw Textiles' usage hasn't moved, but a support ticket has sat open twelve days and its champion hasn't replied in nine, evidence enough to move health from Good to Average even though no single signal alone would have
ActionReconcile product, support, relationship and value evidence into a health read → write the change to Customer State, surface in the CSM's Daily Briefing
✓Assessed in 6 seconds ›
Surfaces inCustomer Daily BriefingviaSlackTeams
Revenue LabsAPP7:38 AM
LIVE
Customer Daily Briefing · Thu 20 Aug
CSM
CUSTOMER HEALTH
• Renshaw Textiles: health moved Good to Average this week, evidence reconciled from product, support and relationship signals.
Evidence: support ticket open 12 days, champion silent 9 days
Next step: Check-in call queued today
Open Briefing
Review Health Read
Ask Agent
The tool alone > AI bolted on > AI-native
What changes when Front feeds a system that learns
Three jobs Front already does, and what each becomes when its evidence joins live company, contact and deal state.
01 | The tool on its own
02 | With AI bolted on
03 | AI-native
Shared inbox threads
Shared inboxes keep customer threads with the team.
Front holds shared inbox conversations, comments, and assignments. Teammates still decide what matters and who should own the next reply.
Front AI summarises conversations.
Front's summary is shared in Front, but the summary does not attach the thread to a live deal or change another team's view.
Inbox evidence reaches the account.
Front thread, participants, and outcome evidence map to the relevant company, contact, or deal.
Rules and routing
Rules assign, tag, and move conversations.
Front rules route conversations, apply tags, and manage replies. An admin still defines triggers, conditions, and exceptions.
Front AI Topics classify conversations.
Topics label conversations inside Front. The label has no company or deal join, so it cannot tell the forecast which account changed.
Routing follows live account state.
Risk or request maps to the relevant company and deal, so the next action can reflect evidence beyond the inbox.
Topics and analytics
Topics show why customers contact the team.
Front Topics and analytics group conversation reasons and show patterns. Retention owners still decide which pattern matters to retention or expansion.
Front AI finds conversation topics.
Front labels stay a Front classification. They do not test the topic against a closed outcome or update the next account review.
Topic signals follow outcomes.
Renewals, expansions, and losses reveal which conversation patterns mattered. Future account decisions use the conversation signal learned from those outcomes.
Runs on it
Capabilities that act on connected evidence
Customer Success
Customer Risk
Active
›
Risk is named as it forms
Customer State names risk type, evidence and severity when product or relationship evidence changes.
↑
Signals reconcile into one threat
Customer Risk logic weighs support and relationship signals even when usage is stable.
−
Only accounts needing action open the review
Each flagged account carries its risk type, evidence and recommended intervention.
+
Renewal exposure is visible early
Managers and leaders see which accounts carry renewal risk and why.
Evidence-backed early risk detection lowers churn and gives managers more capacity.
Customer Success
Customer Health
Active
›
The health read stays live
Customer Health Memory is applied to Customer State as new evidence arrives.
↑
Conflicting signals are weighed together
Product, support and relationship evidence explains a move from Healthy to Watch.
−
The current read is ready for review
Health, evidence and confidence are attached to the account before the CSM prepares.
+
Managers see only changed exceptions
Managers see which accounts changed and why instead of scanning the whole base.
Reconciled health evidence lowers churn and reduces manual portfolio inspection.
Customer Success
Voice of Customer Analysis
Active
›
Feedback becomes a theme with evidence.
It tags the interaction to segment, adoption and lifecycle state.
↑
The recurring theme carries consequence.
It shows which cohorts it touches and what happens to adoption, value and renewal.
−
The current theme picture is ready.
CS, Product and Marketing review live themes and affected cohorts.
+
The theme is answered against outcomes.
It links the theme to customers who churned, renewed or expanded after raising it.
Humans validate product and strategy implications before action.
BUILT FOR SECURITY, CONTROL AND SCALE
Connect data securely, capture every agent's activity, and enforce permissions with ease.
Learn about our security →CERTIFIED + COMPLIANT WITH:
ISO 27001:2022
GDPR
CCPA
Data Protection Act 2018
The GTM teams that learn fastest will win.
Connect your stack to a system that learns.