Use cases
These examples showcase how you can leverage Tray.ai's capabilities, including its AI connectors, to enhance the functionality of Microsoft Dynamics 365. Remember to always handle sensitive data carefully, using data masking when necessary before processing with external AI services.
Lead Scoring and PrioritizationCopy
Objective: Automatically score and prioritize leads in Dynamics 365 using AI-powered analysis.
Steps:
Trigger: Use a Scheduled Trigger to run the workflow daily.
Fetch Leads: Use the
list_entities
operation to retrieve all leads from Dynamics 365.Data Preparation: Use Data Mapper to structure lead data for AI analysis.
AI Analysis: Use Merlin functions'
classify text
operation to score leads based on their likelihood to convert.Update Leads: Use the
update_entity
operation to update lead scores in Dynamics 365.Prioritize High-Value Leads: Use Boolean Condition to identify high-scoring leads and create tasks for sales team follow-up.
Customer Sentiment Analysis for Support TicketsCopy
Objective: Analyze customer sentiment from support tickets in Dynamics 365 to improve customer service.
Steps:
Trigger: Use the
list_entities_raw_filter
operation to periodically fetch new support tickets.Data Extraction: Use Merlin extract's
extract text
operation to pull relevant text from ticket descriptions.Sentiment Analysis: Utilize Merlin functions'
sentiment analysis
operation to determine customer sentiment.Update Tickets: Use the
update_entity
operation to add sentiment scores to tickets in Dynamics 365.Alert for Negative Sentiment: Use Boolean Condition to identify highly negative sentiments and send alerts to the support team.
Automated Data Cleansing and EnrichmentCopy
Objective: Improve data quality in Dynamics 365 by cleansing and enriching contact information.
Steps:
Trigger: Schedule the workflow to run weekly.
Fetch Contacts: Use the
query_entity_data
operation to retrieve contacts with incomplete or potentially outdated information.Data Cleansing: Use Text Helper and Regex connectors to standardize formats (e.g., phone numbers, addresses).
Data Enrichment: Integrate with a third-party data provider to fetch additional information.
Update Contacts: Use the
update_entity
operation to update the cleansed and enriched data in Dynamics 365.
Cross-System Lead ManagementCopy
Objective: Synchronize and manage leads between Dynamics 365 and other systems (e.g., marketing automation platform).
Steps:
Trigger: Use webhooks or polling to detect new leads in the marketing automation platform.
Data Mapping: Use Data Mapper to align data fields between systems.
Check Duplicates: Use the
query_entity_data
operation to check for existing leads in Dynamics 365.Create or Update Lead: Use
create_entity
orupdate_entity
operations based on the duplicate check results.AI-Powered Categorization: Use Merlin functions'
classify text
to categorize leads by industry or product interest.
Secure Customer Data ProcessingCopy
Objective: Process sensitive customer data from Dynamics 365 for analysis while maintaining privacy.
Steps:
Trigger: Schedule the workflow to run during off-peak hours.
Fetch Customer Data: Use the
query_entity_data
operation to retrieve customer information.Data Masking: Utilize Merlin Guardian's
mask data
operation to obscure sensitive information like PII.Analysis: Perform necessary analysis on the masked data using appropriate tools or AI services.
Results Processing: Use Data Mapper to prepare results for storage.
Update Dynamics: Use the
update_entity
operation to store aggregated, non-sensitive results back in Dynamics 365.
Automated Sales ForecastingCopy
Objective: Generate sales forecasts using Dynamics 365 data and AI predictions.
Steps:
Trigger: Schedule the workflow to run at the end of each month.
Fetch Sales Data: Use the
query_entity_data
operation to retrieve historical sales data.Data Preparation: Use Data Mapper and Math Helper to structure and normalize the data.
AI Prediction: Utilize an AI service (via OpenAI or AWS Bedrock connector) to generate sales forecasts.
Create Forecast Entity: Use the
create_entity
operation to store the forecast in Dynamics 365.Notify Stakeholders: Use an email connector to send the forecast to relevant team members.