Skip to main content

Onfleet integration: review requests after successful deliveries

Connect Onfleet with one API key and text every customer a review request after a successful delivery, with the credit going to the driver.

A
Written by Axel Lavergne

When a driver completes a delivery successfully in Onfleet, Reviewflowz texts the customer a review request and credits the review that comes back to that driver. Setup takes one API key: we add the Onfleet webhooks for you.

How it works

  1. A driver completes a delivery successfully in Onfleet.

  2. Onfleet tells us straight away, and the customer becomes a contact in Reviewflowz.

  3. The text goes out after your delay, by SMS or WhatsApp.

  4. Their review is matched to the delivery and credited to the driver.

What triggers a request

Trigger

When it fires

Who is asked

A delivery is completed

As it happens: Onfleet sends it to us, and an hourly check picks up any delivery that didn't arrive

The customer on a successful delivery

Onfleet gives us each customer's phone number, so your request reaches them by text. Failed deliveries are never asked. Customers who turned off texts in Onfleet, or replied STOP to an Onfleet text, never get a text request for an Onfleet delivery. A customer is asked once, even after a second delivery. Customers in the EU or UK are kept on record and not asked.

We also import your last 90 days of deliveries, so reviews you already have are matched to them. Nobody is messaged for those.

Onfleet setup panel before Finish setup

Connect Onfleet

In Onfleet, an administrator goes to Settings, then API & Webhooks, and clicks + under API Keys. Leave "Limit the scope of this key to the tasks it created" unticked, then copy the key.

In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the Onfleet card. Paste the key into Onfleet API key and click Connect Onfleet. We check the key and add the webhooks we need in Onfleet, so there's nothing to set up on Onfleet's webhook page. A key limited to the tasks it created is refused, with the reason.

Onfleet card in the Reviewflowz integrations directory

Connect Onfleet modal with the API key field

Link your teams to locations, then finish setup

Under Settings, pick the Request your successful deliveries join. It needs an SMS or WhatsApp step to send anything. With one request, it's picked for you.

Under Locations, each Onfleet team, shown with its hub, points at the Reviewflowz location whose review page its customers should see. Juniper Lane Grocers links Northside · Austin Hub to Juniper Lane Grocers Northside and South Congress · Austin Hub to Juniper Lane Grocers South Congress. Teams set to Use the fallback go to the Fallback Location, which is set for you when you have one location. A delivery we can't place on one of your teams is kept on record and not asked. If your account isn't set up by location, there's nothing to link.

Connected organizations lists the brands your drivers deliver for. Their deliveries are asked only once you pick a location for the brand; until then it reads Don't ask. Added a team in Onfleet? Click Refresh teams.

Then click Finish setup. Only deliveries completed after that moment are asked.

Onfleet request and Location settings

Set up the request

  • Timing. Juniper Lane Grocers texts 1 hour after the delivery. Delays go up to 7 days, with up to 3 messages, and follow-ups stop once a customer clicks, reviews or unsubscribes.

  • Channel. SMS or WhatsApp. Juniper's text, "Hi {{first_name}}, thanks for shopping with Juniper Lane Grocers! How was today's delivery? A quick review helps a lot: {{link}}", uses 155 of its 160 characters. Try yours with Send myself a test.

  • Direct reviews to. Smart routing picks the site per customer for your objectives. Juniper keeps a 4.9 average on Google and gets as many Yelp reviews as possible.

SMS editor for the review request after an Onfleet delivery

Review routing options with Google and Yelp objectives

Turn it on

Open the request and click Turn requests on. Until it's on, the panel shows "Your review request is set up but not on yet" with Open the request, and deliveries completed in the meantime are kept on record and never texted. Once you're connected, the panel shows the exact time from which successful deliveries are asked.

Onfleet team to Location mapping with the connected organization row

Connected Onfleet panel

Requests page listing Onfleet delivery customers

When a delivery fails

If a delivery is marked failed or deleted in Onfleet before its text goes out, the request is cancelled. Each delivery asks once. A text already sent can't be pulled back.

See what it brings back

The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. Wes Foster's Google review of Juniper Lane Grocers is credited to Ruben Castro, the driver who made the delivery. Rename a driver in Onfleet and the name follows. The Team Attribution Leaderboard ranks your drivers by the reviews they earn.

Customer review credited to the Onfleet driver

Leaderboard of reviews credited to each driver

Good to know

  • If Onfleet stops accepting your key, the panel asks you to create a new one under Settings, then API & Webhooks, and paste it.

  • Each Onfleet organization connects to one Reviewflowz account.

  • Only the person who connected Onfleet can change its settings.

  • Disconnect stops receiving deliveries and cancels the requests that haven't gone out yet. Your contacts and history stay. Reconnect uses the same key, and only deliveries completed after you finish setup again are asked.

  • Delivery notes, addresses, photos and signatures are never stored.

  • In Onfleet, we only add our webhooks: your tasks are never changed.

Related

Did this answer your question?