The message is new. The issue often is not.
“I am still waiting for an answer.” Without context, that is a vague message. With the relevant ticket and earlier communication, it becomes a case someone can work on.
We developed a HubSpot integration for FRED. It connects the AI agent to contacts, cases and communication. AI contributed to building it and helps interpret information from permitted sources during the workflow.
Context instead of asking everything again
A CRM contains different objects. A contact is not necessarily the current ticket. An old note is not necessarily the current contract position.
Illustrative example: a follow-up belongs to an existing case. AI considers the associated contact and available communication rather than composing a generic response. No actual customer case is used here.

Which information belongs where?
| Source in the workflow | Its contribution |
|---|---|
| Contact | Associate the appropriate person in the CRM |
| Ticket or case | Understand the request and handling status |
| Related communication | See what has already been asked or promised |
| Specialist system | Retrieve current facts, such as invoice information |
The Stripe integration illustrates the last point: payment information is retrieved through its own tool. It is not current simply because an older CRM note exists.

More than an API key
The implemented system includes retrieving information, linking objects and processing changes. Different tasks use live requests or prepared search indexes.
If a relationship is ambiguous or a source is unavailable, part of the evidence is missing. AI must not claim a complete review. Available actions also depend on the channel and granted permissions.
Where this can help your team
The approach is relevant when answering one request repeatedly requires several screens. We start with that task, identify the necessary sources and determine the next permitted action.
Sources.
- SolvraONE: own development and technical source reviewOwn source · As of
- HubSpot: understanding the CRMVendor / primary · As of


