The decisions behind the software.
Inside Emilia, MarginFlow, CLVR Verified and Juris Global: the problems, product choices and workflows that shape each one.
02 / CLVR SYSTEMSLook closer.
Build from there.
A booked client should change a follow-up. A reply should change a reminder. A payment needs an approval to check against. A research answer needs a source. Here is how those details shape the products.
When to follow up. When to stop.
Being due for a return visit is only part of the decision. Emilia helps clinic teams check bookings, replies and contact preferences before following up.
Follow-ups
to review.
Knowing when to stop is part of a good follow-up.System overview
The problem.
A client appears on a follow-up list, but they have already booked. If the booking and treatment history sit apart, the team may prepare a message that is no longer needed.
The product decision.
The review queue brings the relevant checks together. The operator can inspect why a client was flagged, review a draft and hold the follow-up when the circumstances have changed.
- 01
Check the client record
Treatment history and contact preferences inform the review. Missing information or unclear consent needs attention before outreach can proceed.
- 02
Find the right moment
Return windows identify possible follow-ups. Existing bookings, replies, pauses and do-not-contact instructions affect whether a message is appropriate.
- 03
Review the draft
The team can review a prepared message, hold it or mark the client do-not-contact. Review approval does not send a message: live sending is not enabled in the clinic portal.
- 04
Record the decision
Save the review decision with the client history. When a reply or booking outcome is recorded, the team can revisit it before deciding to follow up again.
- The situation
- Alex is due to return and appears in the review queue.
- The decision
- An operator finds an existing booking and holds the draft.
- The record
- The hold and booking note explain why no message was needed.
The next operator can see why the client was flagged and why the message was held. A completed review remains useful even when no outreach follows.
Give every enquiry a next move.
MarginFlow is in development for trades and service teams. Its focus is the work between a new enquiry, a prepared quote and a customer’s response.
Kitchen
refurbishment.
A reminder is useful only when it knows what has already happened.System overview
The problem.
A quote goes unanswered while the team is busy on another job. Without the enquiry, quote and conversation together, it is hard to tell whether to chase, clarify the scope or close the opportunity.
The product decision.
MarginFlow links the quote to the original enquiry and schedules follow-ups around its status. A customer reply or a won or lost decision changes whether another reminder is appropriate.
- 01
Capture the enquiry
Keep the customer’s details and request with the lead. Add the job type, urgency and information needed to prepare a quote.
- 02
Make the quote concrete
Attach the description, line items, price and timeline to the enquiry. The scope stays available alongside the customer conversation.
- 03
Follow the response
Scheduled follow-ups remain tied to the quote. A reply or a won or lost outcome changes whether another reminder should be sent.
- 04
Close the loop
Record whether the opportunity was won or lost. Follow-up checks use that status so a closed opportunity does not receive another scheduled reminder.
- The situation
- A kitchen refurbishment quote is awaiting a reply.
- The decision
- The customer replies before the next scheduled reminder.
- The record
- The reply stays with the quote; the scheduled reminder is skipped.
The design keeps a useful question visible: does this quote still need a follow-up? Its scope centres on enquiries, quotes and replies.
Connect the payment to its approval.
CLVR Verified is designed around one question: does the payment match what was authorised? The request, approval and verification record need to answer it together.
Supplier payment.
Approval attached.
A payment record should make the approval easy to find.System overview
The problem.
An approval sits in one conversation, the invoice in another and the payment reference elsewhere. Reviewing the transaction means reconstructing which details were authorised.
The product decision.
Verified’s design links the recipient, amount and purpose to an approval reference, then compares the recorded payment details against that decision.
- 01
Make the request explicit
Bring the recipient, amount, purpose and supporting invoice into a structured request. These are the details the reviewer is asked to authorise.
- 02
Record the decision
The intended workflow records who reviewed the request and their decision. The approval reference identifies what the subsequent payment should match.
- 03
Connect payment and verification
The payment record is checked against the approved recipient, amount and reference. The design calls for differences to be flagged for investigation.
- 04
Keep the evidence together
Keep the request, approval, payment reference and check result together for later review.
- The situation
- A supplier invoice is submitted for payment.
- The decision
- A reviewer approves the documented recipient and amount.
- The record
- The payment details are compared with the approval and the result is saved.
The aim is a reviewable payment history. The dedicated Verified site describes the proposed workflow; contact the product team to discuss requirements and availability.
A shortlist you can explain.
A useful shortlist comes with reasons, sources and questions still to resolve. Juris Global brings those parts of residency and citizenship research into one place.
Explore programmes.
Compare the details.
Explore the atlas A useful answer should leave a clear path back to its evidence.System overview
The problem.
Three programmes look promising, but their descriptions use different formats. Comparing the details means switching between tabs and keeping track of where each claim came from.
The product decision.
Programme dossiers organise the research consistently. A comparison holds up to three options, while source references give the reader a way to inspect the material behind an answer.
- 01
Explore the landscape
Browse the atlas by region or jurisdiction. Open a country to inspect its programmes and begin a shortlist.
- 02
Inspect the detail
Read the route information, requirements, costs and sources in each dossier. Keep qualifications and unanswered questions alongside the headline details.
- 03
Compare the options
Compare up to three programmes side by side. Save a shortlist and export the research notes for a later discussion.
- 04
Follow the sources
Ask JURIS is designed to answer from published research and include source references. Use the research to prepare an advisory enquiry about your circumstances and unresolved questions.
- The situation
- A researcher has found three programmes worth considering.
- The decision
- Compare the details and revisit the sources behind each option.
- The record
- A shortlist with research notes and questions for an adviser.
The researcher leaves with a brief they can explain: the options considered, the sources used and the questions an adviser still needs to answer.
Talk to CLVR.
Have a question about one of our products? Tell us which one you’re interested in and what you need.
Email CLVR hello@clvrsystems.com