Radar is Hook's AI agent for external signal detection. It continuously monitors everything Google indexes (industry news, press releases, company announcements) across every account in your portfolio.
This article explains how to customise Radar so that it identifies churn risk and expansion opportunities most relevant for your CS team.
👤 Managers and Technical Admins have access to these settings in Hook
Pre-requisites
Radar agent created during Hook implementation
Manager or Technical Admin access to your Hook instance
Related Articles
Customisation Guide
Edit the Agent Prompt
The prompt for the Radar AI agent can be updated in Agent configuration settings.
The Radar prompt tells the LLM how to evaluate external news articles and decide whether they represent a risk, an opportunity, or neither. Editing it lets you control what Radar flags and how it frames those signals to your team.
Navigate to Agent configuration settings and select the Radar agent.
Review the existing prompt text in Instructions. This defines the criteria Radar uses when scanning and interpreting external news.
Edit the prompt to reflect your organisation's priorities - for example, specifying the types of events most relevant to your customers, or adjusting how Radar should weight certain signal types such as M&A activity or leadership changes.
Save your changes.
Example Radar view in Agent configuration settings
Update the Automation Trigger
Radar checks for risks and expansion opportunities based on the criteria set in the corresponding radar automation. Customise which customers Radar searches for by updating the automation trigger e.g. customers in a specific segment.
Navigate to Agent configuration settings and select the Radar agent
Select the Radar automation
Edit the Customer filters are met trigger to the new trigger criteria
Click Save
Ensure the automation is set to Active so that the agent is enabled in Hook
Updating Customer filters are met automation trigger for Radar agent
Verification
After saving your prompt changes:
Check the Signals table to confirm that new signals generated from external news reflect your updated prompt criteria.
Confirm that any plaibook actions queued by Radar are assigned to the correct team members.
Troubleshooting
Radar is not generating signals after a prompt change
Ensure the automation for the agent is activated and does not have any errors - see this automation troubleshooting guide.
Signals are being generated but don't match the updated prompt
Check the prompt changes were saved and that the automation is set to active. View the automation logs to see the most recent runs for the agent.
Radar is flagging irrelevant news articles
Review your current prompt. If the criteria is too broad, Radar may surface signals that aren't commercially relevant to your team.
Tighten the prompt to specify the event types, industries, or signal characteristics that matter most to your portfolio.
Contact Hook support ([email protected]) if signals remain noisy after prompt adjustments.
❓ Frequently Asked Questions
Can I have different prompts for churn risks and upsell opportunities?
Separate sections can be added in the Radar agent prompt to define criteria for churn risks and upsell opportunities.
Will changing the prompt affect signals that have already been generated?
Updating the prompt will apply to new signals created after the prompt is updated.
Who can edit the Radar prompt?
Managers and Technical Admins have access to Agent configuration settings in Hook, including Radar prompt configuration.
Does Radar only monitor news, or does it also use data from emails and meetings?
Radar monitors external sources - everything Google indexes, including industry news, press releases, and company announcements. It is distinct from Echo, which ingests emails, meetings, and support tickets. The two agents complement each other: Echo surfaces signals from your internal customer interactions, Radar surfaces signals from the public web.