Scout is a Slack bot that answers carrier-placement questions in plain English. An agent types @Scout homeowners Houston TX and gets a ranked list of the carriers we already write in that line and area — strategic partners first, sourced straight from our book of business in the data lake. Ask it something more open-ended and a separate tier takes over: Scout writes and runs its own SQL against the book of business or producer-licensing data, asking before it guesses on anything genuinely ambiguous. Usage — who's asking, how often, what's coming back empty — is tracked on an Entra-gated dashboard.
Type it however you'd say it. Scout extracts the line of business, city, and state from casual phrasing — @Scout workers comp near Billings Montana works as well as @Scout homeowners Houston TX. Works as a mention in any channel or as a direct DM.
Every recommendation is grounded in our own book of business — queried live from the Ennabl data lake, filtered by the requested line and a 50-mile radius. Ranks strategic partners first (up to four), plus one non-strategic option so the agent sees the whole picture.
Everyone gets the same placement lookup, but leadership sees deeper detail on identical queries. A separate Tier II tier goes further still: open-ended questions — written premium by LOB, retention trends, a carrier's appointment status — get routed to an agent loop that writes and runs its own SQL against the book of business or producer-licensing data, iterating until it has a real answer and charting results where the shape allows it. It asks before it guesses when a question is genuinely ambiguous. Tier II and Leadership are independent — someone can have one, the other, or both.
A staff-only bot in the YP Slack workspace. Every placement question stays inside the tools we already work in — no new chat window to learn. A separate, Entra-gated usage dashboard exists for tracking adoption and query history, open to a small allowlist.