How it works
- 1Connect your ServiceM8 account to ReviewNudger through ServiceM8's standard OAuth authorization. Your jobs, schedules, and clients stay in ServiceM8; ReviewNudger only listens for job status changes.
- 2When a job is marked Completed in ServiceM8, ReviewNudger receives the event, looks up the job's contact details, and applies your sending rules. It can then send one neutral Google review request by SMS or email.
- 3Every send is tracked with delivery status, opt-outs, and review click-through, all visible from one dashboard.
Why a native connection beats middleware
The same four guarantees on every native integration — because they come from the platform, not the connector.
No middleware account or per-task fees
The connection runs directly between your account and ReviewNudger. There is no third-party automation account to maintain and no per-task metering on your review requests.
No manual field mapping
ReviewNudger already knows the provider's payload. Customer name, phone, and email resolve automatically — there are no field mappings to build or quietly break later.
Built-in duplicate protection
Every incoming event is deduplicated before any message goes out, so provider retries and replays can never double-text a customer.
Opt-out compliance handled
STOP replies and email unsubscribes are recorded per customer and honored automatically on every future trigger.
Set up the ServiceM8 integration
- 1Start a ReviewNudger trial and finish the short signup.
- 2Choose ServiceM8 as your trigger and approve the ServiceM8 connection.
- 3Mark a real job Completed in ServiceM8 to confirm the trigger end to end.
- 4Done. Each completed job can now start one automatic review request under your sending rules.
Related resources
Useful next steps for choosing a trigger, setting up the request, and putting the workflow into practice.
Frequently asked questions
Do I need a Zapier account to connect ServiceM8?
No. The ServiceM8 integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a job is marked Completed in ServiceM8, ReviewNudger records the event and evaluates it against your per-location send delay, cooldown, contact, and channel rules. One matching event can create one review-request journey by SMS or email.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future ServiceM8-triggered event.
Which ServiceM8 contact receives the review request?
ReviewNudger checks the job's own contacts first (the job contact, then the billing contact), and falls back to the client record's primary contact. The job needs at least one usable email address or phone number; otherwise it fails visibly without guessing a customer.
Questions before you start? Email support@reviewnudger.com and a human will answer.