While Restaurantology provides built-in tools for enriching Account and unit-level fields, Salesforce Flow allows admins to automate alerts and conditional actions that go beyond enrichment. Flows can help users stay informed of key account changes without manual monitoring.

Example use cases

[01] Send alerts when unit counts cross a threshold
Trigger an email or Slack alert when a multi-unit Account exceeds a specified number of locations (e.g., 20+ units).

[02] Notify teams when a tech detection changes
Create a Flow that monitors the Latest Restaurantology Tech Data field and sends a message when a key vendor (e.g., Toast, Popmenu) appears or changes.

[03] Flag high-growth prospects
Use the Growth Trend, 6-month Growth (%), or Inferred Status RestaurantologyLog fields to trigger internal alerts for the sales team when an Account is flagged as rapidly expanding.

Example: Flagging and alerting high-growth Accounts

Step 1: Update the Account field

• Trigger: RestaurantologyLog’s Inferred Status equals Rapid-growth.
• Condition: Account’s High Growth Account__c equals FALSE.
• Action: Update High Growth Account__c to TRUE.

Step 2: Alert the team

• Trigger: Account’s High Growth Account__c changes from FALSE to TRUE.
• Action: Send an email or Slack alert to notify sales or customer success teams.

[!TIP]
Since RestaurantologyLogs are refreshed monthly without a “prior value” for fields like Total Locations Overall, monitoring a boolean field on the Account record ensures you can compare historical state and avoid repeated alerts.

Best practices

• Use Record-Triggered Flows for real-time updates.
• Limit alerts to meaningful changes to avoid notification fatigue.
• Test Flows in a Sandbox environment before deploying.
• Coordinate with Restaurantology enrichment mappings to prevent duplicate automation.