How It Works · Buying Signals
Know what they want, before they ask.
Visitors rarely say “I am ready to buy.” They say “can you start next month?” Fred reads what people mean, not just what they type: intent, sentiment, and urgency, on every conversation.
What that means for your team.
Fred’s conversation signals and summaries help your team review inquiries and choose the next step. Consider the visitor’s request alongside any score before prioritizing follow-up.
The hot lead gets flagged
- Buying language spotted and weighed, not skimmed past
- Urgency read from the conversation, not guessed from a timestamp
- Your team knows who to call first, with the reason attached
Contact details for follow-up
- Contact details collected through your consent process
- The relevant page or product surfaced as interest builds
- Review consent and contact-collection steps during setup
Prioritize complaints for follow-up
- Pricing questions, demo requests, and complaints routed by intent
- High-priority conversations reach specific people or workflows
- The angry customer gets a human, fast, with context attached
Every conversation becomes intelligence.
While they talk
- 30+ intent categories tracked with confidence scores
- Sentiment read as the conversation moves
- Fred adjusts what it surfaces and when it asks
The moment they share
- Send captured contact details to your configured CRM
- Delivery timing depends on the integration and receiving system
When the session ends
- Intent, sentiment, urgency, and a summary on every completed session
- Lead score and conversation summary in your configured CRM
Review supported fields and delivery requirements on Integrations. For an overview of using conversation signals in follow-up, see the signal guide.
Every conversation tells you who to call first.
Talk to Fred.
For the person who asks how.
What exactly does Fred track?
30+ intent categories with confidence scores, sentiment classification per conversation, and urgency. At session end, every completed conversation also gets a summary. None of that requires extra configuration; it is the baseline.
How does this feed the lead score?
The score is built in three layers: a heuristic score from 0 to 100, a signal breakdown your reps can read, and a written narrative explaining the number. The signals include buying language, engagement, urgency, and what Fred surfaced crossed with what the visitor did about it. Fred scores the conversation, not the browser URL, because when Fred is the navigation, the URL means nothing. Review the available signal breakdown for your deployment alongside the conversation; the score is an indicator, not a probability of purchase.
When does Fred ask for contact details?
Fred collects contact details through a consent step. Review the collection flow and consent language for your deployment during setup. Captured details can be sent to your configured CRM; delivery timing depends on the integration and receiving system.
Can I route conversations by intent?
High-priority intents such as pricing inquiries, demo requests, and complaints can route to configured team members or workflows. Test delivery and define how your team handles missed or delayed notifications.
Does sentiment change how Fred behaves?
Yes. A frustrated visitor is a routing decision, not a sales opportunity. Negative sentiment biases Fred toward de-escalation and handoff, and the sentiment is recorded with the conversation so your team sees the temperature before they pick up the phone.
Is there a deeper e-commerce module?
Yes. Stores that need product-level intent, like detecting when a shopper is comparing two specific items, can add the advanced e-commerce intent module. It is a separate capability for stores that want it, on top of the conversation intelligence every Fred already ships with.
Stop reading cold chats to find the hot one.
Use conversation signals to help your team prioritize follow-up. Configure and test the workflow before launch.