Note: The Storm-Ready Generator Service Pro agent is in closed beta and available to a limited number of clients, so it may not appear for you yet.
Add-on required: AI:den+
User role required: Office staff and above
Region: US only
Once the Storm-Ready Generator Service Pro agent is configured and activated, it starts calling customers and booking generator services automatically. While the agent handles the calls, you can monitor its performance and review every conversation from the AI:den+ dashboard.
Managing your active agent
The agent's card on your AI:den+ dashboard is your hub for monitoring its status and performance.
Live status and metrics: The card shows a real-time status badge (such as No call or On call) so you know when the agent is speaking with a customer. It also shows 30-day metrics, including calls made, time saved, and services booked.
Edit: Reopen the configuration wizard to update any setting.
Disable agent: Pause all outbound calls without deleting the configuration. The agent moves to the Disabled tab and can be re-enabled at any time.
Reviewing the agent's calls
From the agent's card, click Call history to open a detailed log of every customer the agent has contacted or is due to call.
Call list: The left panel lists customers with the linked service reminder and a color-coded outcome tag for quick scanning (green for a positive result like Service booked, red for a failed call). Upcoming scheduled calls also appear here with their date and time. You can search by name or address and click Add filter to narrow the list.
Call timeline: Selecting a customer shows a dated timeline of every call and activity. Each outgoing call includes a summary of the conversation, the reason for the call, the call type, and the final call outcome.
Audio playback and transcript: Play the full recording from the timeline, download it, or open the word-for-word transcript.
Scheduled activities: When a call needs follow-up, the scheduled activity the agent created appears in the timeline. A callback the customer requested is assigned to AI:den, which calls them back at the agreed time.
Customer context: The right panel shows the customer's details, their service reminders, and account information alongside the call log, so you can review everything in one place.
Calls are also logged against the customer's record, so your team can see the agent's activity alongside your other communications. The job notes the agent captures, such as gate codes, pet warnings, and backup contact details, are saved to the booked job for your technician.
Call outcomes reference
Every call is logged with an outcome you can see in the call history. Most outcomes are informational; the agent retries failed calls or closes the rest out on its own. A few outcomes need a person to follow up, so the agent flags those by creating a scheduled activity assigned to the user(s) set in the agent's Trigger settings.
Outcomes that need your team
Human callback requested: The customer asked to speak to a person. The agent ends the call politely and creates a scheduled activity for your team to call back.
Sensitive issue detected: The agent picks up on signs of bereavement, illness, or hardship. It responds with care, pauses the chase sequence, and creates a scheduled activity so your team can review the situation sensitively.
Tip: Check your scheduled activities at the start of each working day so none are left waiting.
Outcomes handled automatically
No action is needed for these. They're logged in the call history for reference:
Service booked: The booking is confirmed and added to the diary.
Appointment scheduled with job note: The booking is confirmed and the agent logs the job notes.
Service already done: The customer's service has already been completed.
Call back: The customer asked to be called back at a specific time. The agent creates a scheduled activity assigned to AI:den, which calls the customer back at the agreed time.
Customer declined service: The customer turned down the service this year.
Customer moved property: The customer has moved out, so the agent sets the property to dormant and stops future reminders.
Not connected: The call didn't connect, so the agent retries.
Customer disconnected call: The line dropped, so the agent retries.
System error: The call failed due to a technical issue.
Not connected reasons
When a call is logged as Not connected, a secondary reason is stored in the call record to help you diagnose the issue.
Reason | What it means |
Dial busy | The number was engaged at the time of the call. |
Dial failed | A generic dialing failure; the call never connected. |
No answer | The number rang out without being answered. |
Invalid destination | The phone number is formatted incorrectly (e.g., missing a country code or containing spaces). |
Provider denied | The telephony provider rejected the call. |
Provider unavailable | The telephony provider service is temporarily down. |
Routing error | The call took too many network hops and was terminated. |
Marked as spam | The call was blocked by the recipient's carrier. |
User declined | The recipient manually rejected the incoming call. |
System error reasons
When a call is logged as System error, the specific technical reason is also stored in the call record.
Reason | What it means |
Invalid destination | The phone number is wrong or formatted incorrectly and cannot be routed. |
Dial failed | A generic failure between the agent and the telephone network; the call never left the system. |
Provider unavailable / denied | An issue with the telephony provider, such as the service being temporarily down. |
Routing error | The call got stuck in a loop or took too many network hops, so the attempt was ended. |
Marked as spam | The recipient's carrier flagged the calling number as spam and blocked the call. |
Timeout | The network didn't respond within the expected time, so the attempt was ended. |
What's next?
Read more:
Understanding the Storm-Ready Generator Service Pro agent: How the agent adapts its calls and handles complex scenarios.
How to configure the Storm-Ready Generator Service Pro agent: Set up the agent's identity, conversation logic, triggers, and notifications.
Common questions
Where do I see the outcomes of the agent's calls?
Where do I see the outcomes of the agent's calls?
You can see the outcomes of the agent's calls in two places. On the AI:den+ dashboard, click Call history for a full log of every call, including recordings, transcripts, and job notes. Each call is also logged against the customer's record in the Communications tab, alongside any scheduled activities the agent created.
Who is assigned the scheduled activities the agent creates?
Who is assigned the scheduled activities the agent creates?
Scheduled activities that need a person, such as a Human callback requested or Sensitive issue detected, are assigned to the user(s) you selected in the Users to assign scheduled activity to field in the agent's Trigger settings. A callback the customer requested for a later time is assigned to AI:den, which calls them back at the agreed time. You can change the assigned users at any time by clicking Edit on the agent's card.
What happens when a customer says they've moved?
What happens when a customer says they've moved?
When a customer says they've moved or sold the property, the agent thanks them, ends the call, and logs the Customer moved property outcome. The property record is automatically set to dormant and future service reminders for that property are disabled, so they won't be contacted about it again.