// Reference
Limitations & FAQ
What Renewal Radar treats as production renewal evidence today, which dates stay excluded, and how uncertainty affects automation.
Agent Tools and the decision layer
What is Renewal Radar’s decision layer for HubSpot agents?
Renewal Radar turns scattered contract dates, account context and follow-up signals into a clear decision for HubSpot agents and your team. Its deterministic rules resolve which accounts need attention, why and what should happen next. Approved Agent Tools let agents retrieve those decisions and carry out supported actions. The agent handles the conversation; Renewal Radar supplies the decision and evidence.
Are Renewal Radar’s HubSpot Agent Tools approved?
Yes. HubSpot has approved Renewal Radar’s Agent Tools. The four tools cover finding at-risk accounts, explaining company risk, snoozing an alert and recording a confirmed renewal outcome. Use the existing Renewal Radar app and add the tools to an agent in a supported HubSpot account.
How do I add Renewal Radar tools to a HubSpot agent?
Connect Renewal Radar, activate Team or Partner, and complete your first scan. Open your agent in HubSpot’s Agent Hub and use Add action to find Renewal Radar. In Breeze Studio, open Configure and use Add tool. Add the tools, test with a real Company ID, and publish the agent. Your HubSpot account must have the required agent access and permissions.
Which plan includes Agent Tools?
Agent Tools require an active Renewal Radar Team or Partner plan with monitoring enabled. The free scan provides exposure totals and three named accounts; it does not include Agent Tools. HubSpot’s own agent access, subscription requirements and credits apply separately.
What can agents change through Renewal Radar?
Two tools only read decisions. The action tools can snooze an existing alert for 14 days or record an explicitly confirmed renewed or churned outcome. Recording an outcome also completes the open follow-up task. Agents should only use these actions when requested; they must not infer a won or lost outcome from activity.
Does the agent calculate the risk itself?
Renewal Radar calculates the business decision with explicit rules and supported HubSpot evidence. The same evidence and rule version produce the same decision. An agent can explain that output, but its generated wording can vary. Missing dates, uncertain timing and ambiguous company matches stay visible instead of becoming invented answers.
Do I need to use an agent?
No. Your team can keep using Renewal Radar’s HubSpot card, reports and controlled follow-up tasks. Agent Tools give HubSpot agents access to the same decisions and supported actions. You choose how your team works with the output.
Current product boundaries
- Company, Deal, Subscription, Line item, Quote and eligible custom-object sources can be production-authoritative when they pass the deterministic semantic and record gates.
- Generic Quote expiration, billing/payment cadence, forecast/operational and created/modified dates remain excluded from authoritative renewal timing.
- Risk decisions use deterministic rules. HubSpot agents access the results through approved Agent Tools; the decision engine does not use a predictive churn model, sentiment analysis or health score.
- No reading of email bodies, note bodies, call recordings, meeting notes, or ticket content.
- Renewal alert window is 30, 60, or 90 days.
- No real-time CRM object webhooks. Scanning is periodic and can also be triggered manually.
- The record card lives on Company records. Portfolio and configuration views live in Renewal Radar settings.
Automatic source detection
You do not need to pick one contract-end field or confirm one portal-wide source. Renewal Radar discovers supported renewal semantics and resolves timing separately for each Company.
A Company can resolve from eligible Company, Deal, Subscription, Line item, Quote or relevant custom-object evidence, a renewal-specific proxy, an estimate, or no reliable current timing. Estimates remain Low-confidence and task-ineligible.
Task-safety limitations
A High or Critical Renewal Risk does not automatically create a task. The canonical timing must also be task-eligible, the Company must allow tasking, and the task lifecycle/control policy must allow creation.
Medium/Low timing confidence, proxies, estimates, material conflicts, no timing, and incomplete authoritative evidence fail closed for new task creation. Engagement Risk by itself is visibility, not a standalone task trigger.
If required data is temporarily incomplete or unavailable, Renewal Radar does not treat that as evidence that an existing active risk disappeared.
Scan performance
Renewal Radar performs portal-wide candidate discovery before the expensive account-level signal checks. If complete candidate recall cannot be proven, it falls back to the broader Company inventory rather than silently filtering possible renewals.
The latest production read-only validation considered 24,159 Companies, processed 375 canonical candidates, and completed in 12m33s with zero failed Companies. CRM Search completed with zero 429s and zero retries under the production limiter.
Common questions
Does Renewal Radar use AI to decide which date is correct?
No. Source classification and timing resolution use deterministic, versioned rules. Runtime resolution does not use an LLM, embeddings or fuzzy matching.
Is a mapped Company contract end date required?
No. Renewal source discovery is automatic and can resolve from eligible Company, Deal, Subscription, Line item, Quote or relevant custom-object evidence.
Can an estimate create a task?
No. Estimates are Low-confidence monitoring timing and are task-ineligible.
Does Engagement Risk create a task?
No, not by itself. Engagement Risk is supporting visibility and can explain or mitigate Renewal Risk.
What happens when HubSpot data is temporarily unavailable?
Incomplete evidence blocks unsafe new automation and preserves existing active state until a complete authoritative decision is available.
Where can I see the performance evidence?
The published speed and accuracy benchmark documents the 24k-company before-and-after, and the current docs include the latest 12m33s production validation with zero CRM Search 429s.