After the claim: asked, answered, credited

A request goes out only on the events you pick in your agency management system, and an open claim is not one of them, so nobody is asked mid-claim. Pick Claim settled and Renewal completed in EZLynx and leave Policy issued unpicked: the day a water-damage claim settles, the claimant gets one text to that office's Google profile, and a client whose hail claim is still open gets nothing. There is no claim-status filter and no denied-claim rule in the product: what your system records as settled is what sends, so check how your system closes a denied claim before you pick that event. See review generation.

Without discussing the policy, and nothing posts until a person submits it. Set one reply rule, anything below 4★ queued for a person, and write the agent's instructions once: never confirm a policy, name a carrier, repeat a figure or give a coverage opinion. When a one-star names the deductible, the depreciation and the producer, the draft repeats none of it and offers the claims advocate's direct line instead; a person reads it and clicks Submit Reply, which posts it on that office's Google profile once Google is connected. See review replies.

Reviewflowz offers nothing and attaches nothing: every claimant and every renewing policyholder gets the same text and the same link, with no rating pre-screen and no routing by sentiment. Rules on inducements in insurance advertising differ by state, so what you may offer is your state's question, not this page's. Google's terms ban paying for a review whatever its rating, Yelp forbids asking at all, and the help center's reading of US federal law is that an incentive is never tied to the rating you want. See review generation.

EZLynx, AgencyZoom, QQCatalyst and Xanatek, yes: each records a policy issued, a claim settled and a renewal completed (QQCatalyst adds a quote delivered), you pick which of those events sends the request, and the policyholder on that record gets it by text or email. A record that never reaches a picked event sends nothing, and past policyholders imported for reporting are never messaged. Applied Epic, HawkSoft and AMS360 are not connected today; until they are, each office has its own request link and an uploaded contact list goes out with the same reminders. See EZLynx, AgencyZoom, QQCatalyst and Xanatek.

Yes. Attribution reads first names, last names, full names and the nicknames you add, tolerates a typo, and quotes the words it matched, so "Eddie" credits the account manager once you add the nickname, and the claims advocate's first name credits her whichever office the claimant used. The leaderboard, on Premium, ranks your claims advocate, account managers and producers on one board. See review attribution.

Google first, one Business Profile per office: it is where a prospect checks an agency and where your request sends people. Facebook (Recommends, not stars), Yelp and BBB sit in the same feed, each review tagged by its moment, Claim, Renewal or New policy, so you read what claimants say across all four without opening four sites. Never send a request to Yelp, which forbids asking; a BBB or Facebook review arrives on its own, and Trustpilot matters for carriers more than for agencies. See review monitoring.

Yes. EZLynx maps each office to its own Google profile, so a claimant served by one office is sent to that office's page, and on an account billed per location the request link carries the office as well. Every office's profile is in one feed, and the monthly report by email breaks reviews and average rating down by office and by moment (Claim, Renewal, New policy), one table on the first of the month. See review exports and reports.

Both, in that order of use. The request after a settled claim or a completed renewal sends the policyholder to the office's Google profile, and a private form collects what you want to hear about a claim without it going public. Set the form to offer everyone the same public link whatever they tell you: routing by score is the line not to cross. Feedback on each agent is the leaderboard, counting who gets named, by role. See review generation.