Use case

Review generation

Asking for a review is easy. Asking the right person at the right time, and then answering what comes back, is the part that needs a system.

Trigger · order completed Approval-first
How it runs

Step by step, with the channel named.

01
An order or a visit completesThe event, not a manual list somebody maintains.WhatsApp
02
A dated step waits, then checks consentConsent is re-checked at send time.WhatsApp
03
The request goes outAn approved template, paced with the rest of your sending.WhatsApp
04
The review is stored structurallyRating, reviewer, text and date as separate fields.Google
05
A reply is drafted and scored for toneA harsh review gets a different tone. You approve before it posts.Google
What runs it

The parts of uxjo doing the work.

ReviewsEvery review, filterable

Search the wording, filter by star, see which are unanswered.

Runs on WhatsAppConsent-checked request

Nobody is asked who has opted out.

ReviewsSentiment and severity

Scored, so the reply matches the review.

GovernanceApproval before posting

The draft is a proposal, never an action.

How it is built

The journey, as it exists in Studio.

A trigger, the conditions that hold it back, and the branches that decide what happens next.

Journey StudioPublished
Order or visit completedTrigger · order event
Wait, then re-check consentDelay · dated step
Ask on WhatsAppTemplate · utility
Or ask by emailEmail · your provider
Review stored, reply draftedGoogle · approval-first

The two send branches are a choice per contact, not two journeys. Whichever channel that person actually uses is the one the request goes out on.

The ask and the answer are one journey.The request, the stored review, its sentiment score and the drafted reply all belong to the same flow.
What changes

The same job, before and after.

Without uxjo

  • Asked by hand, so it happens on quiet days only
  • No idea whether the person opted out
  • Reviews read as screenshots, one at a time
  • A bad review sits overnight because nobody saw it

With uxjo

  • Asked automatically a set time after the order
  • Consent re-checked at send time, not at signup
  • Stored as fields, so you can filter by star or search the wording
  • New reviews in real time, scored, with a draft reply waiting
Every channel

What each channel contributes.

GoogleWhere the review lands

Stored structurally, scored for sentiment, replied to after approval.

WhatsAppWhere the ask goes

An approved utility template, consent-checked.

EmailThe alternative ask

Through your own provider, same journey.

InstagramWhere praise also shows up

Comments and mentions captured against the contact.

Questions

What people ask before they start.

Does uxjo post the review reply itself?

It drafts the reply and waits. You approve, edit or discard, and only then is it posted to Google.

How quickly do we see a new review?

In real time rather than on a nightly sync, so a difficult review does not sit unanswered overnight.

Can we ask on a channel other than WhatsApp?

Yes. The request is a journey step, so it can go by email instead, through your own provider.

Can we see which reviews mention a specific thing?

Yes. Because the text is stored as a field rather than an image, you can search the wording and filter by rating.

Industries

Who runs this most.

Not on this page?

Your journey is the one we have not listed yet.

Every business has a flow that is only theirs. Describe it in a message and we will map it with you, name the triggers, and tell you honestly what runs today and what does not. No form, no wait.

Talk to usStart free