Legal · Stowe Family Law

The case closes, the client is invited to review, and the right office gets the credit. Nobody remembers to do it.

Asking a finished client for a review depended on a fee earner or a marketer remembering to do it, so invitations were missed and landed against the wrong office.

Talk to us about something similarAll case studies
ClientStowe Family Law
SectorLegal
WhenLive
Used byNo interactive users. Proclaim calls it when a case reaches the review stage
Plugs intoProclaim, Trustpilot Invitations API, Review Solicitors
AINone. This one runs on rules, not models.
What we built

One URL a legacy system can call, that does the modern work for it.

A single endpoint that accepts name, email, case reference, branch and platform, and sends one review invitation per call.
A branch table translating Proclaim's internal office number into that office's Trustpilot location and Review Solicitors firm ID.
A full log of the URL Proclaim sent, the client details, the platform and the platform's verbatim response.
Validation that sends nothing and lists exactly which fields were missing, so a broken Proclaim workflow is easy to diagnose.
Forced HTTPS so client names and emails never travel unencrypted.
pattern

Fire-and-log webhook

One stateless URL that validates, acts, logs and reports back, letting a legacy system drive APIs it could never call itself.

portability

Central ID translation

The caller only knows the internal branch ID, which is why the planned migration to another CRM needed zero mapping work.

support

Raw responses kept

Every 'did this send?' question is answerable years later, including the platform's own error text.

How it plugs in

Proclaim's workflow does the triggering.

When a case reaches the review-request stage, Proclaim calls the endpoint twice, once per platform. The client gets an email and the review appears on the correct office's profile.

The applicationProclaimTrustpilot Invitations APIReview Solicitors
job Triggered from Proclaim's case workflow, two calls per client, one per platform
job Every request and response written to the database as a side effect, nothing recorded by hand
What changed

Eligible clients are asked at the right moment with zero staff effort, and each invitation is attributed to the correct office so per-office ratings stay accurate.

one detail only this project hasThe project record shows about 850 invitations sent in the first nine months, across a lookup of around 40 offices.
Figures from the project record: about 850 invitations in the first nine months; around 40 offices in the lookup table
Something similar?

Which step in your process only happens if someone remembers?

Book a walkthroughRequest a callback