
Fireberry
Customers ask about their accounts, orders, or open tickets. Your AI agent queries Fireberry in real time, pulls the right records, and delivers accurate answers on the spot. Manual CRM lookups disappear. Response times shrink from minutes to seconds.




From contact lookups to record creation, your AI agent taps into Fireberry's data layer during every conversation, keeping your CRM current without manual entry.
Fireberry
See how businesses use AI agents connected to Fireberry to handle account inquiries, capture leads, and keep their CRM data accurate around the clock.
A returning customer messages your site asking about their subscription renewal date. Your AI Agent queries Fireberry's contacts module by their email address, locates their account record, and returns the renewal date and plan details. The customer gets a precise answer in seconds. Your support team skips another routine CRM lookup.
A prospect browsing your pricing page at 1 AM starts a chat asking about enterprise features. Your AI Agent walks them through qualification questions, collects company size, budget range, and timeline, then creates a lead record in Fireberry with all the context attached. Your sales rep opens the CRM Monday morning to a warm, pre-qualified lead with full conversation notes.
A customer reports a billing discrepancy. Your AI Agent queries Fireberry for their account, checks the associated deal record and payment history, identifies the issue type from picklist values, and creates a new service record assigned to the billing team. The ticket arrives with full context, so no one asks the customer to repeat themselves.

Fireberry
FAQs
The agent uses Fireberry's Query Records API to search any module (contacts, leads, accounts, or custom objects) by field values like email or phone number. It applies filters and retrieves matching records in real time during the conversation. No data is cached between sessions.
The agent can create records in any Fireberry table you authorize, including leads, deals, accounts, service tickets, and custom modules. You specify which tables the agent can write to, so it only creates records where you want them.
In your Fireberry dashboard, click the gear icon in the top right corner. Go to Integration in the settings menu, then click API Forms. Your TokenID appears under the My Token field. Copy it and paste it into the Tars tool configuration screen.
No. Every query runs live against your Fireberry instance during the conversation. Contact details, deal information, and custom field values are fetched on demand and used only to generate the response. Tars does not maintain a separate database of your CRM records.
Yes. The agent calls the Get Picklist Values endpoint to retrieve all active dropdown options for any field, such as lead source, ticket priority, or deal stage. It uses these values when creating or updating records, ensuring data stays consistent with your CRM configuration.
The agent handles empty results gracefully. If a query returns no matching records, the agent lets the customer know it could not find a match, asks them to verify the information provided, and offers to connect them with a human agent or create a new support request.
Fireberry's AI Assistant works inside the CRM interface for your support agents. Tars puts an AI agent directly in front of your customers, on your website, WhatsApp, or SMS, so they get answers before a ticket is ever created. Plus, Tars connects to hundreds of other tools beyond Fireberry.
Yes. The Query Records endpoint supports filtering with operators like equals, contains, greater than, and less than. The agent can find records created after a specific date, filter by status fields, or combine multiple conditions to locate exactly the right record for the customer.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.