Sales Signals in Zoho CRM for timely follow-up: set up a feed your reps act on

Sales Signals in Zoho CRM: what they are and how they speed up follow-up

Using Sales Signals in Zoho CRM for timely follow-up means letting the CRM tell your reps the moment a customer does something worth acting on. An email open, a missed call, a new support ticket or a social media mention each raises a notification. The rep sees it and follows up while the lead is still warm.

A signal, in Zoho CRM, is a notification raised whenever an event occurs that needs your attention. Zoho describes Sales Signals as a way to track real-time customer interactions across channels, from email opens to social media mentions. Every signal is the result of an event connected with your CRM.

Signals do not replace your follow-up process. They tell a rep when to act. Workflows and tasks decide what happens next, and they work best alongside signals rather than instead of them.

This guide covers which customer actions raise a signal, where reps see them and how to add your own. It also covers how to stop the feed turning into noise, which is where most teams lose the benefit.

Response speed: why the first minutes after a customer action count

Response speed is the main reason to use Sales Signals. A 2018 guest post on the Zoho blog about automating CRM workflows cites an MIT study. It found that if you make first contact with a web lead within 5 minutes, the lead is 22 times more likely to convert.

Treat this figure as a direction rather than a promise. The MIT figure is cited second-hand and concerns web leads. The principle still holds for other customer actions: a call made while the customer is reading your quote lands better than one made next week.

The Zoho guest post also notes that its automation ideas depend on a close integration between the CRM and the sales team's telephone system. Signals follow the same logic. A rep can only act fast on events the CRM can see.

Default signals: the email events every new Zoho CRM account tracks

A new Zoho CRM account comes with one set of signals already switched on: Email Insights. Zoho says these are the only default signals in a newly subscribed CRM, because Zoho CRM has its own native email service. The native email signals cover three events:

• Open: the recipient opens the email.
• Click: the recipient clicks a link in the email.
• Bounce: the email bounces and does not reach the recipient.

The default email signals work whether or not you connect a mailbox. They report opens, clicks and bounces on emails sent from Zoho CRM's email server. A rep who sends a quote from the CRM therefore learns when the customer opens it, with no extra technical setup. Open and click tracking still needs to be covered by your privacy notice and consent approach.

Email signals also cover two further events. Incoming emails raise a signal when a customer writes to you. Competitor alerts raise a signal when an email mentions one of your competitors. A competitor alert on an open deal deserves a rep's attention, because it suggests the customer is comparing options.

Signals from integrated Zoho apps and telephony

Each Zoho app you integrate with Zoho CRM adds its own events as signals. Zoho calls these integration-derived signals, from services such as SalesIQ, Desk, Backstage, Survey and Webinar. Zoho SalesIQ is a customer engagement platform that you plug into websites and applications. The table lists the events that Zoho's help page on viewing signals names for each source.

Source	Events that raise a signal	What it tells a rep
Zoho PhoneBridge or Built-in Telephony	Missed calls	The customer tried to reach you and got no answer
Zoho Campaigns	Open, Click, Hard bounce, Soft bounce	How a contact responded to a marketing email
Zoho Desk	New ticket, New comment, New response, Ticket overdue, Ticket Escalated, New rating, Mention	The customer has a support issue, or one is going badly
Zoho Survey	Responded, Visited	The customer answered a survey, or opened it and left
Zoho Social (Facebook)	Post, Comment, Like, Direct Message	The customer engaged with your page
Zoho Social (Twitter)	Mention, Reply, Direct Message	The customer talked to you or about you
Zoho Backstage	Ticket Purchased, Checked In, Ticket Cancelled	The customer's status for your event

A Visited survey signal means the recipient accessed the survey and saw the form but took no action. If you already route social engagement into the CRM, our guide to Zoho Social linked to Zoho CRM covers that setup.

The three kinds of signal, and why customer silence counts

Zoho CRM classifies signals into three kinds. Knowing which kind a signal belongs to helps a rep decide how fast to respond. The three kinds are:

• Customer actions: events observed at the level of customer behaviour, such as opening an email or clicking a link.
• System events: events the system triggers, such as a ticket expiring or an email bouncing.
• Communication-based events: direct one-to-one contact between the customer and the business, such as a missed chat, a missed call or a survey response.

Communication-based events usually deserve the fastest response. A missed call or missed chat means the customer reached out and nobody answered. System events are often housekeeping. A bounced email tells you to fix an address before you try again.

Zoho also makes a point that teams often overlook: non-interaction can count as a signal just as much as interaction does. A survey that was visited but not answered is information. So is a quote email that was never opened. Both tell the rep to try a different channel rather than send the same email again.

Where reps see signals in Zoho CRM and how to act on them

Reps find Sales Signals under the bell icon on the top-right bar of the Zoho CRM interface. Zoho defines signals as notifications about customers' interactions across your channels of communication. The bell is where those notifications collect.

The bell gives a rep a single place to check, so treat it as a queue. Open the signal, open the record, take one action and log it. That action might be a call, a reply or a task for later. Every signal a rep reads should either lead to an action or show you that the event is not worth raising.

Field reps need the same discipline away from the desk. Our post on the Zoho CRM mobile app and what field sales actually use covers how reps work with records on a phone.

Signals are only useful when it is clear who acts on them. A missed call from an existing account belongs with the account owner, not with whoever happens to check the bell first. If your accounts are split by region, territory management in Zoho CRM sets the ownership that follow-up depends on.

Custom signals for customer actions Zoho does not capture

Custom signals are notifications you build for events your business chooses, such as a product added to a cart or a brochure downloaded. Zoho CRM lets you trigger them from a function or through an API call from a third-party application. They fill the gap when the customer action happens outside the Zoho apps.

Each custom signal has a namespace. The namespace is a unique identifier the system generates for the signal, and you use it to trigger the signal from a custom function or the API. You cannot modify it, so record it in your build notes.

One custom signal represents one event. Zoho's own example is MailChimp: to capture more events from it, you create a separate custom signal for each one. Plan the list before you build, because every event you add is another notification in a rep's feed.

Start with events that predict buying. A brochure download on a deal at proposal stage tells a rep something worth a call. A routine event that every customer triggers every week usually does not, and it will bury the signals that matter.

Worked example: following up a quote with Sales Signals

This example follows one rep at a firm that uses the default email signals, Zoho PhoneBridge and the Zoho Desk integration. Each step names the signal and the action it prompts.

1. On day one, the rep emails a quote to a prospect from Zoho CRM. No mailbox connection is needed, because default signals track emails sent from the CRM's email server.
2. An Open signal appears under the bell icon that afternoon. The rep opens the record and calls while the quote is fresh in the customer's mind.
3. The customer does not answer, then calls back while the rep is on another call. With PhoneBridge configured, a missed call signal appears. The rep returns that call before anything else, because the customer made direct contact.
4. Two days later, an incoming email from the customer mentions a competitor. The competitor alert tells the rep the deal is being compared. The rep replies with a clear comparison and books a call.
5. Before that call, a Zoho Desk signal shows a Ticket Escalated event on the same account. The rep checks with support first, rather than pitching into an unresolved problem.

Each signal led to one decision. None of them relied on the rep remembering to check the record. That is the test to apply to any signal you switch on.

Keeping the Sales Signals feed useful rather than noisy

A noisy feed is the most common reason Sales Signals stop working. When reps receive every Campaigns open and every social like, they stop checking the bell. The missed call that mattered then gets buried. The fix is to switch on only the events that change what a rep does.

At Svennis we switch on one source at a time and ask the reps which signals they actually acted on before we add the next. Any event nobody acted on is questioned before it stays in the feed.

Before each source goes live, check these points:

• Does the event change what a rep does today? If not, leave it off for sales.
• Who owns the follow-up: the record owner, support or marketing?
• What is the expected action: a call, a reply or a task?
• Is a bounce a sales matter, or a data-quality job for whoever maintains contacts?
• For custom signals, is each one a single event that predicts buying?
• Does the source track email opens or clicks? If so, check that your privacy notice and consent approach cover tracking in emails before it goes live.

Review the feed again once reps have used it for a few weeks. Remove events nobody acts on, and add the ones reps keep asking about.

Signals and workflow automation: notifying a rep versus acting for them

Sales Signals tell a rep that something happened, but they do not carry out the follow-up. Workflow automation does that part, and a reliable follow-up process uses both. The Zoho blog guest post on CRM workflows describes three telephony workflows that act on customer events:

• Web form to call: as soon as a web form is filled, it is registered in the CRM, which prompts the rep on their system and mobile phone.
• Missed-call tickets: the telephony system compares an unanswered number with CRM data and, if the caller is a new lead, generates a ticket automatically.
• Sticky agents: a lead who calls in is connected automatically to their assigned sales representative.

Signals alone also leave gaps that users raise in the Zoho community. In one thread, a user asked how to give every lead a fixed follow-up sequence of call reminders, email reminders and post cards. In another, a user asked for an option to create a follow-up task when closing an activity, with the last email carried over into it.

Zoho counts non-interaction as a signal too, so plan an automated step for customers who go quiet rather than relying on the bell. If your team is ready to add automation alongside signals, our intermediate Zoho CRM guide goes beyond the basics.

What Sales Signals mean for a UK sales team

For a UK firm with a small sales team, Sales Signals matter most where one person covers both new business and existing accounts. The same rep may see a quote opened, a ticket escalated and a missed call in one morning. Agree as a team which comes first, and write the order down.

Plan cover for absence and for activity outside office hours. Signals arrive when customers act, not when your office is open. Decide who checks the bell when a rep is on leave, so a missed call does not wait a fortnight.

Integrations are where the value builds. If your support runs on Zoho Desk and your marketing on Zoho Campaigns, connecting them to the CRM brings those events into one feed. If you run events, Backstage signals show which customers checked in. That gives a rep an obvious reason to call the next day.

Keep the number of tools in proportion to the team. A firm with a few reps gets more from a short, trusted feed than from every integration switched on at once.

Next steps for setting up Sales Signals in Zoho CRM

These steps take you from the default setup to a signal feed your reps trust:

1. Open the bell icon in your Zoho CRM account and check which email signals already arrive.
2. List the Zoho apps and telephony you use, and match them to the events in the integration table above.
3. Pick the few events that should change what a rep does today, and agree who owns each one.
4. Switch on one source, run it for a few weeks and review which signals reps acted on.
5. Add custom signals only for events outside Zoho that predict buying, with one event per signal.
6. Pair signals with a workflow or follow-up task, so quiet customers are caught too.

If you want help designing the feed and the follow-up process behind it, our page on Zoho CRM implementation and consulting describes how we work on CRM projects with UK firms.

Sources

• Zoho CRM Online Help: View Signals
• Zoho CRM Online Help: Signals, what it is and why it matters
• Zoho Blog: 6 Practical Ways to Improve Sales By Automating Your CRM Workflows
• Zoho Community: Sequence of follow-up in Zoho CRM
• Zoho Community: Better options for follow up and activity last contact communication