How to Use Freshworks to Turn Product Signals into Leads

The short answer: connect Freshdesk to Freshsales so tickets show on CRM records, install the CRM tracking code and send your product's key events, set Freddy's positive and negative scoring signals, switch on the automation that tags high scorers as product qualified leads, auto-assign those to reps, enrol lower scores in a sales sequence, and have reps check each lead's open tickets, by hand or through Freshdesk's MCP server, before they call.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: your product has a free trial or a free tier, thousands of sign-ups, and a sales team that calls them in the order they arrived. Some of those people invited three colleagues on day two; others never logged in again. Freshsales can score on that behaviour and route the ones worth a call. For what each Freshworks product is and costs, see the Freshworks glossary entry.

Before you switch anything on:

• Price the plan scoring needs. Contact scoring and sequences are listed on Pro. For example, four reps on Pro cost 4 x $39 = $156 a month billed annually, against 4 x $9 = $36 on Growth, per the Freshsales pricing page checked on 24 October 2026: $120 a month is the cost of the scoring.
• List the events your product already logs. Sign-up, inviting a teammate, importing data and asking for a trial extension are the kind Freshworks' scoring guide suggests. Start with the three your strongest customers did early.
• Write down what a sales-ready contact is in your own words, then compare it with Freddy's top-rated contacts after two weeks.

What you need

• Freshsales Pro or Enterprise, and Freshdesk on any plan if support history should inform sales.
• A developer for an hour, to place the tracking code and the event calls.
• A consent position for tracking. The tracking code records page visits and events against contacts, so it belongs behind your cookie banner's analytics choice.

Step 1: Connect support and sales

In Freshsales, open your profile, Settings, the API settings tab, and copy your API key. In Freshdesk, as an administrator, go to Admin, Support Operations, Apps, Get More Apps, install Freshsales and enter the username and key, per the integration guide. Choose up to 10 fields each for contacts, leads, deals and accounts to show in Freshdesk. Agents now see a requester's five nearest open deals, and Freshsales users see linked tickets on the record.

Step 2: Install the tracking code

In Freshsales, go to Admin settings, CRM Tracking Code, and paste the snippet before the closing head tag of your site and app pages, per the tracking code guide. Enter the domains to track. The code shows a chat widget by default; untick the box, or add chat=false, if you do not want it. Test form capture in a private browsing window, because the same cookie in a normal session updates one contact instead of creating new ones.

Step 3: Send the product events

Call trackCustomEvent from your app when a user does one of the actions on your list, with the user's email, which the guide makes mandatory. Before the first call, fix each event's attributes and data types: Freshworks' custom events guide says a data type cannot be changed later, and data arriving in a different type is not recorded. Segment can send the same events instead, from the contact scoring page.

Step 4: Teach Freddy what counts

Go to Admin Settings, Leads, Contacts, & Accounts, Contact Scoring, and add signals, per the scoring guide. Positive: the countries and job titles you sell to, account size and industry, and your product events. Negative: unsubscribing, cancelling an account, removing users. Freddy combines your signals with patterns it finds in the account's own data to produce a score from 0 to 99 and a one-to-five-star customer fit rating.

Step 5: Tag and route the ready ones

Switch on the automation that tags contacts above a score you set as Product Qualified Lead, or Likely to buy for non-SaaS businesses, and moves their lifecycle stage, per the score automation guide. Then go to Admin Settings, Teams & Territories, Auto-assignment rules, create a rule for Contacts with the tag as its condition, and pick the reps to receive them in rotation, per the auto-assignment guide. Rules run in priority order, so number this one above any catch-all rule.

Step 6: Nurture the rest with a sequence

Create a sales sequence with the audience set to a contact score below your threshold, per the sequences guide. Pro allows 10 sequences per user. Keep the default exits: all steps done, a reply, an unsubscribe or a bounce, per the entry and exit guide, and add one custom exit for contacts who gain the PQL tag, so they leave nurture when sales takes them.

Step 7: Check support history before the call

A contact who scores high because they use the product heavily may also have three open tickets. With step 1 done, the rep reads the linked tickets on the contact before calling. To speed that up, an AI client can connect to Freshdesk's MCP server under Admin Settings, Apps & Integrations, MCP, with a user's API key, and list each new PQL's open tickets and their last replies.

The assistant drafts the briefing; the rep decides whether to call, wait or loop in support. The MCP FAQ says every tool is available to anyone who connects, with actions limited only by that user's Freshdesk role, and the tools include updating tickets, so connect it with a user whose role you have checked.

Step 8: Read the result

In the contacts list, filter by the PQL tag or by four and five stars, and hover over a score to see its key scoring factors, per the scoring use guide. After two weeks, set Freddy's top contacts beside your written definition from the start, and adjust the signals where they disagree.

Where Freshworks' guides warn you

• An outbound sequence cannot be paused. Once started it cannot be edited either; clone it to make changes and disable the old one.
• Event data types are permanent. A wrong type means events that are silently not recorded.
• Sync needs an identifier. Only contacts with an email address or a unique external ID sync between Freshdesk and Freshsales, per the integration guide.
• Multiple leads on one email. Freshdesk then shows the top five matches, and the agent has to pick the right one.

A scoring model that a vendor trains on your data is also a reason to keep your data with that vendor. Keep your own definition of sales-ready in writing, so the score stays a tool you check rather than a judgment you inherit.

FAQ

Do I need Freshdesk for this?

No. Steps 2 to 6 run in Freshsales alone. Freshdesk adds the support history in step 7, which stops a rep from pitching to a customer with an open complaint.

Can I score contacts without a developer?

Partly. Contact properties, account attributes and sales activity signals need no code. Product events need the tracking code or Segment, which usually means a developer.

What does the PQL tag change?

It marks the contact as a product qualified lead and moves its lifecycle stage, per the score automation guide, which your assignment rule and sequence exit condition can then use.