Contents:

• Overview
• Use Cases
• Prerequisites
• Enabling the AI Assistant
• Accessing the AI Assistant
• Using the AI Assistant
• Conversations
• Considerations: Permissions, Security, and Data Handling
• Troubleshooting and FAQ
• Summary

 

Overview

The LeanData AI Assistant is a natural-language chat experience that helps admins investigate audit logs on the Unified Audit Logs page. Instead of opening individual log entries and cross-referencing graph configuration to figure out why a record was processed a certain way, you can ask the assistant questions in plain language and receive answers that combine the record's audit log with the relevant graph topology, match logic, and routing context.

The assistant is built on top of LeanData's routing engine, so it has access to your deployments, your match logic, and the full journey of a record across Orchestration and BookIt audit logs. It can explain single log entries, summarize multi-log journeys, and execute searches on your behalf.

Use Cases

The LeanData AI Assistant helps admins quickly understand and explain LeanData routing behavior. Common scenarios include:

• Explaining a single audit log in plain language to share with a non-technical stakeholder, such as a sales rep asking why a lead was assigned to them.
• Understanding match decisions on Lead-to-Account, Contact-to-Account, or similar match nodes, including which candidate records were considered and why one was selected over the others.
• Exploring the route not taken by asking what would have needed to be different for the record to take a different edge or land on a different owner.
• Summarizing a multi-log journey across Orchestration and BookIt as one narrative, for example a lead that routes through Orchestration and then books a meeting through BookIt for Forms.
• Searching audit logs with natural language when you do not remember the exact filter or field name, for example "show me all logs for leads from Acme that ended in the catch-all queue this week."
• Onboarding newer admins or sales support staff who do not yet have deep familiarity with your routing graphs.

 

Prerequisites

Before the LeanData AI Assistant is available, the following must be in place:

• Unified Audit Logs enabled. Your workspace must have audit logs synced to the cloud and the unified audit log interface turned on. See the Unified Audit Logs Guide for instructions.
• LeanData Remote Site Setting in Salesforce. Your Salesforce org must have the LeanData Remote Site installed so the assistant's endpoints are reachable. For setup steps, see LeanData Admin - Adding the LeanData Remote Site Setting. 
• Initially enabling or disabling the assistant requires the LeanData Custom Objects Full Access permission set.

 

Enabling the AI Assistant

The LeanData AI Assistant is a self-service toggle under AI Tools. To enable the assistant:

1. From the LeanData app, navigate to Admin > Settings > AI Tools.
2. Toggle AI Assistant on.
3. Select your preferred AI model provider from the available options.
4. Click Save.

Once enabled, the assistant becomes available to users who have access to the Audit Logs page (LeanData Dashboard Access).

 

Accessing the AI Assistant

The LeanData AI Assistant is available directly on the Unified Audit Logs page.

To open the assistant:

1. From the LeanData app, click Audit Logs in the left sidebar.
2. In the bottom right corner of the page, click the AI Assistant chat icon.

The assistant opens as a floating chat panel over the Audit Logs page. The panel stays in view as you search, scroll, and open individual log entries, so you can reference logs in the page while you ask the assistant about them.

You can also launch the assistant with a log pre-loaded as context. On any audit log entry, click Explain this Log in the Object panel. The assistant opens with that log already attached to the conversation, ready to answer questions about it.

 

Using the AI Assistant

You interact with the assistant by typing questions into the chat panel. The assistant uses your audit log data, your active graph deployments, and LeanData's routing logic documentation to generate answers. Answers include deep links to the relevant log entries, graphs, and Salesforce records so you can verify the explanation against the underlying data.

Asking About a Specific Log

With a log loaded into the conversation, you can ask questions such as:

• What happened to this record?
• Why was this lead routed to this owner?
• Why was this account matched instead of one of the other candidates?
• Which fields on this record drove the routing outcome?
• What would have needed to change for this record to be routed to a different owner?

The assistant responds with a plain-English explanation that references the specific nodes, edges, and match decisions in the graph that processed the record. Where helpful, the response links directly to the relevant node in the graph, the audit log entry, or the Salesforce record.

Searching Audit Logs with Natural Language

You can ask the assistant to find logs without using the structured search filters. For example:

• Show me all logs for leads from Acme this week that ended in the catch-all queue.
• Find logs where the Round Robin node skipped the assigned rep in the last 24 hours.
• List all audit logs related to johnsmith@companyname.com in both Orchestration and BookIt.

The assistant translates the request into a structured search, runs it against your cloud audit logs, and displays the matching results inside the Unified Audit Logs page. You can refine the search by following up in the same conversation, for example "narrow this to the last 7 days" or "only show me leads, not contacts."

Summarizing a Record's Journey

When a record has been touched by multiple LeanData processes, you can ask the assistant for a single narrative summary that stitches the logs together. For example:

• Summarize the full journey of this lead across all LeanData processes.
• What happened to this lead from the time it was created to the time it booked a meeting?

The assistant produces a chronological narrative across Orchestration and BookIt logs, with links to each underlying log entry.

Drafting an Explanation for a Non-Technical Stakeholder

The assistant can rephrase its explanation at different levels of technicality. After getting an answer, you can ask:

• Rewrite this in a way I can send to the sales rep.
• Make this shorter and remove the graph terminology.

The assistant returns a version of the explanation suitable for forwarding to a non-admin audience.

Suggested Prompts

Suggested prompt buttons appear in the chat panel and on individual log entries to launch common questions with a single click. Quick actions include prompts such as Explain this log, Why this owner?, and Summarize this journey. Clicking a quick action sends the prompt to the assistant with the relevant log already attached as context.

 

Conversations

The assistant organizes your interactions as conversations. Each conversation keeps the assistant's context from one question to the next, so follow-up questions reference the same logs and the same line of inquiry.

• Start a new conversation. Click New Conversation in the assistant panel to clear the context and begin a fresh investigation.
• Switch conversations. Click the conversation list icon in the assistant panel to view your saved conversations and reopen one.
• Rename a conversation. Click the conversation title to give it a more descriptive name, such as "Acme catch-all investigation."
• Delete a conversation. Open a conversation, click the overflow menu, and choose Delete. Deleted conversations are removed from your history.

Conversations are scoped to your user. Other admins in the org do not see your conversation history.

 

Considerations: Permissions, Security, and Data Handling

• Access. Any user who can access the Unified Audit Logs page can use the LeanData AI Assistant once it is enabled for the org. Only users with admin permissions to LeanData settings can enable or disable the assistant.
• Data sent to the model. When you ask a question, the relevant audit log records, the relevant graph configuration, and LeanData's routing documentation are sent to the model that powers the assistant. The model generates a response and returns it to the assistant.
• Data residency. The audit log data the assistant references is the same data already synced to LeanData's cloud audit log storage. The assistant does not introduce additional copies of your CRM data outside of what Unified Audit Logs already stores.
• Model usage. LeanData provides the model within the standard usage envelope. Any data sent to the model is not used to train the model and is not shared with others.
• Rate limits. To protect the service and manage cost, the assistant applies per-user and per-org rate limits. If you reach a limit, the assistant pauses new requests until the limit resets and surfaces a message in the chat.
• PII handling. Audit logs can contain PII such as names, email addresses, and company information. This data is sent to the model only as needed to answer your question and is handled according to LeanData's data processing terms.

 

Troubleshooting and FAQ

The AI Assistant icon is not visible on the Audit Logs page.

• Confirm that Unified Audit Logs is enabled for your org. The assistant requires the unified audit log experience and does not appear on the legacy per-product audit log pages.
• Confirm that an admin has toggled AI Assistant on under Admin > Settings > AI Tools.
• Confirm that your user has access to the Audit Logs page.

The assistant says it cannot find a log I expect it to find.

• Confirm the date range. Cloud audit logs are retained for the configured retention period (90 days by default). Older logs are not searchable.
• Try referencing the record by a more specific identifier, such as the Salesforce ID, rather than a name or partial email.

The assistant gives an explanation that does not match what I see in the graph.

• Confirm that the graph deployment shown in the audit log entry matches the deployment you are reviewing. The assistant explains the log against the deployment that processed the record, which may not be the current active version of the graph.
• If the explanation still appears incorrect, use the thumbs-down feedback control in the chat panel to flag the response. Feedback is reviewed to improve the assistant.

Which model powers the assistant?

• The assistant is currently powered by Google's Gemini model, using a LeanData-provided key.

Can I bring my own model API key?

• Bring-your-own-key is not currently supported. All customers use the LeanData-provided Gemini model.

Does the assistant work outside of the Audit Logs page?

• The assistant is currently scoped to the Unified Audit Logs page and questions about audit log data. It does not currently configure graphs or take actions in FlowBuilder.

Does the assistant answer questions about long-term trends, such as "which node has the most errors in the last 30 days?"

• The assistant is focused on single-record root cause analysis and multi-log journey summarization. Longitudinal trend questions are not in scope. Use Salesforce reports on the LeanData__Log__c object for trend analysis. See the Unified Audit Logs Guide for reporting guidance.

Is my data used to train the model?

• No. Customer audit log data sent to the model is used only to answer your question. It is not retained by the model provider for training and is not shared across customers.

 

Summary

The LeanData AI Assistant gives admins a natural-language way to investigate and explain audit logs. It combines your cloud audit log data with your graph deployments and LeanData's routing logic to answer questions about why a record was processed a certain way, summarize multi-log journeys, and execute audit log searches on your behalf.

For questions or additional assistance, please contact LeanData Support.