ServiceM8 integration guide

You need an existing ReviewNudger account, a ServiceM8 account, and a ReviewNudger location with its Google review destination and at least one sending channel configured. ReviewNudger is currently available to United States businesses.

Confirm permission to contact your customers, review your send delay and cooldown, and turn off overlapping review-request automation that could ask the same customer twice. The ReviewNudger account owner connects and disconnects ServiceM8.

You do not need Zapier, Make, or a manually copied API key for this native connection. ReviewNudger reads the ServiceM8 business, job, and contact details it needs and registers a job-status notification subscription. It does not create or edit your ServiceM8 jobs, clients, schedules, or invoices.

An active ServiceM8 job whose current status is Completed can start one review-request journey. ReviewNudger checks the current job after receiving a status notification; other job statuses, deleted jobs, and payments alone do not trigger this integration.

ReviewNudger processes notifications in the background, usually on the next worker run, approximately once per minute. ServiceM8 delivery delays and processing retries can add time. Your configured initial delay and sending rules then determine when a message can send.

The job needs usable customer contact details. ReviewNudger checks active job contacts in this order: job contact, billing contact, then other job contacts. If none has an email or phone, it checks the client’s active contacts, preferring the primary contact. If no usable contact is found, the event shows a non-send reason; ReviewNudger does not guess a recipient.

Retries and repeated notifications do not create a second journey for the same job. Reopening and completing the same job again does not create a new journey. A different completed job may still be skipped when the customer is inside your cooldown or has opted out.

Review requests are neutral. Customer permission, do-not-contact settings, channel opt-outs, cooldowns, pauses, subscription status, and sending readiness still apply. Follow-ups stop when the customer acts. Clicking a public-review link does not prove that the customer posted a Google review.

The standard 14-day trial requires a card and includes up to 50 account-wide SMS attempts, including initial requests, reminders, tests, and failures. Failed attempts are not refunded, and changing numbers or resubscribing does not reset the allowance. Email follows its own sending rules.

Your included toll-free texting number sends only after carrier approval. While verification is pending, or for up to 30 days after rejection while correcting the filing, eligible active accounts with sending turned on may use a disclosed ReviewNudger sender, subject to daily limits and availability. Those texts use standard copy and end with “Sent via ReviewNudger”; trial sends count toward the same 50-attempt allowance. Blocked accounts cannot use that sender. Sending switches to your own number once approved.

The base plan costs $29 USD per month per location, billed directly by ReviewNudger. Paid SMS/email requests and follow-ups have no monthly message cap or per-message fee, subject to sending rules and availability. A local texting number is an optional $100/year add-on requiring a paid plan and separate approval.

The account owner can open Dashboard → Settings → Connected apps → ServiceM8 and select Disconnect. ReviewNudger clears its stored access and refresh tokens and disables the connection’s incoming notification address. New ServiceM8 notifications cannot start requests through that connection.

Disconnecting ServiceM8 does not cancel your ReviewNudger subscription or automatically cancel previously created requests. If you also need to stop existing journeys, pause sending and check those requests in ReviewNudger.

To reconnect, use Connect again and approve ServiceM8’s authorization. Confirm the business name and connection status before checking a new completed job.

No event appears: confirm ServiceM8 is connected and the job is active and currently Completed. Allow time for notification delivery and background processing. If connection or webhook setup shows an error, reconnect and test with a fresh job.

The event shows a non-send reason: check the job and client contacts for a usable email or phone, and read the displayed reason. A missing contact, opt-out, cooldown, or disabled automation can prevent a request.

A request exists but is queued or failed: check its initial delay, subscription and pause status, SMS verification or trial allowance, channel readiness, and individual delivery outcome. Connecting ServiceM8 alone does not make SMS ready.

The same job does not create another request: duplicate protection also covers reopening and re-completing a job. Use a fresh test job and contact for a reviewer demo.

Authorization is revoked or expired: reconnect through Settings. A revoked connection may appear as an error when ReviewNudger next detects it.

Contact support@reviewnudger.com with your business name, ServiceM8 job number, approximate completion time, and the event or request status you see. Never send passwords, OAuth tokens, secret keys, or unnecessary customer contact details.