When a service order is completed in PestPac, on the Mobile App or posted on the desktop, Reviewflowz asks the customer for a review. The review that comes back is matched to that order and credited to the technicians on it, when the order names them.
How it works
A technician completes a service order on the PestPac Mobile App, or the office posts it in PestPac.
PestPac tells Reviewflowz each time it happens, and Reviewflowz reads the order and the customer on its service location.
The request goes out after your delay.
The customer's review is matched to the order and credited to its technicians.
What triggers a request
Trigger | When it fires | Who is asked |
A service order is completed | The order is completed on the PestPac Mobile App (Complete) or posted in PestPac (Post), or released and invoiced | The customer on the service location |
The trigger is on from the moment PestPac is connected and feeds one request, PestPac review requests. The customer is asked by the email and phone on the service location. An order posted as not serviced isn't asked. Customers aren't asked when your business or the customer is in the EU, the UK or Switzerland.
Connect PestPac
You connect with six values that WorkWave sends with PestPac API access: API Key, Tenant ID (your Company Key), Client ID, Client Secret, Username and Password.
How to get them. Call PestPac Support on (800) 762-0301 or email [email protected] and ask: "Please set up PestPac API access for Reviewflowz on our account, with webhooks." WorkWave sends you the six values. There is nothing to create in a PestPac screen.
Plan. PestPac's pricing lists API Integrations in its Enterprise package.
Cost. WorkWave charges a one-time setup fee for the API platform, plus a cost based on the data you read and your daily API calls. Ask for the amounts when you request access.
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the PestPac card. If you already have an integration connected there, click Connect another integration first. Paste the six values and click Connect PestPac. Reviewflowz names your company, lists your active branches and registers its notifications in PestPac, so completed orders start arriving. The Connection card shows your Company, Tenant ID and API username with Status: Connected.
Link your branches to locations
Under Branches, give each Branch in PestPac the Reviewflowz location whose review profiles its customers should see. Magnolia Shield Pest Control links CHARLOTTE to Magnolia Shield Charlotte and RALEIGH to Magnolia Shield Raleigh. A service order from a branch you haven't linked uses the location in Fall back to. If your Reviewflowz account has one location, every branch is linked to it for you. Opened a branch? Click Refresh list and link it.
Set up the request
Timing. An order counts from the end of the visit PestPac recorded, and your delay comes on top. Magnolia Shield emails 3 hours later, then sends a reminder 3 days after that as Message 2, with the subject "A quick favor, {{first_name}}?" and the button "Leave a review". Follow-ups stop once a customer clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, set per message.
Message. Magnolia Shield's From name is "Magnolia Shield Pest Control", the Subject "How did today's service go, {{first_name}}?", which Dana Whitfield reads as "How did today's service go, Dana?", and the Button text "Review your service". Try yours with Send myself a test.
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Magnolia Shield aims for as many Google and Yelp reviews as possible. Show all options on the email lists every site instead.
Turn it on
The trigger is already on. Open PestPac review requests and click Turn requests on. The status line reads "Sending requests to every new contact", and the Syncing panel's Sending requests for service orders completed since shows the day you connected.
When an order changes
If a service order is deleted, or its invoice is voided, before the request goes out, the request is withdrawn.
See what it brings back
A review that comes back through a request is matched to the customer and the service order it came from, and credited to the technicians on the order, when it names them. Jared Upchurch's four star review, "Quarterly service with Magnolia Shield is easy. Tasha texted before arriving and walked me through what they sprayed.", lands on Tasha Bell. Reports > Dashboard > Team Attribution Leaderboard counts the reviews credited to each technician, Tasha Bell, Jenna Haas, Ramon Luna and Wes Garner at Magnolia Shield. The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped, and the CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from PestPac.
Good to know
Keep the PestPac login WorkWave set up for the API as it is. If its password changes, the card shows Reconnect needed: enter the six values again with the new password, with Enter new credentials. Your branch links and your request stay as they are, and service orders completed while the values were refused are picked up once they work again, for the last 7 days.
If PestPac accepts your API key but doesn't let it set up webhooks, Connect PestPac says so. Ask WorkWave to add webhooks to your PestPac API access, then connect again.
If the card says your API key can't read service orders, invoices or service locations, ask WorkWave to add those, and webhooks, to it. Reviewflowz picks up on its own once it can.
Disconnect withdraws every request that hasn't gone out and removes the Reviewflowz notifications from your PestPac account.
