goodshout

How to send review requests from your emails

Updated 21 September 2026 · 7 min read

Sending a review request from your email takes one of three things after a job: you BCC an address, you forward an email, or you route something through Zapier or Make. All three land in the same place and use the same timing rule you've set on your Ways to send page. None of them need a software integration, and none depend on a particular tool: they work with any email you send.

Find your address

Every business gets one unique Goodshout address. Find it on Ways to send under Your Goodshout address (free on every plan): it looks like yourbusiness-xxxxx@inbound.goodshoutapp.com. Copy it before you start; you'll paste it into whichever method below fits how you invoice.

Method 1: BCC it when you send an invoice

This is the simplest option if you email invoices directly.

  1. Open the email you're about to send your customer.
  2. Add your Goodshout address to the BCC field, alongside the customer.
  3. Send as normal.

Whether you can set this up once, so it is pre-filled and you don't have to remember, depends on your invoicing tool:

  • Tradify has CC and BCC fields in its email templates (Settings), so your Goodshout address can be added once and pre-filled on the emails you send from that template.
  • Fergus lets you set an ongoing BCC in your email settings, up to 6 addresses, applied to every invoice and quote automatically. Set it once and forget it.
  • Xero's newer invoicing screen lets you add a BCC per invoice send, but there's currently no way to save it as a default. You'll need to add it each time (it's usually remembered as a recent recipient, which speeds this up).
  • ServiceM8 and Jobber both let you add extra recipients when sending an invoice by email, but we haven't been able to confirm from their own documentation whether that field acts as a true BCC or is visible to the customer, or whether it accepts any address. If you use one of these, try it, or use forwarding below instead, which we can confirm works regardless.
  • Any other invoicing tool: check its email settings for BCC. Some tools only offer CC or an "extra recipients" field. That works just the same, but your customer can see your Goodshout address on the email (it's a plain address with no personal details). If you'd rather they didn't, use the Zapier or Make method below.

Method 2: Forward an email you already sent

Forgot to BCC? Forward an email you already sent to the customer (find it in your Sent folder) to your Goodshout address. This only works when the email is in your own mailbox. Emails sent from inside an invoicing or job tool usually aren't, so for those use CC or BCC, or the Zapier or Make method.

The email has to have been sent to the customer's email address: a quote, an invoice, a receipt, a booking confirmation, or a plain message. That's how we know who to ask. Something you never emailed to the customer, such as a paper receipt or a cash sale, won't work here. For those, use your QR sticker or add the customer by hand.

  1. Open the email you sent to the customer.
  2. Forward it to your Goodshout address. The customer isn't told, because you're forwarding it to us, not to them.
  3. Send.

We find the customer's address inside the forwarded message and take the first one we come across, so forward just that one email. If the message contains other email addresses, BCC is more reliable.

Method 3: Go hands-off with Zapier or Make

This is the option for anything that doesn't already email the customer itself: a Stripe payment, a Calendly booking, a job marked done in a CRM. Once it's built it's hands-off: your trigger fires, a short email goes to your Goodshout address with the customer's email address in it, and a request is created automatically, every time.

The shape is always the same two steps, whichever tool you use:

  1. Trigger: whatever event means the job's done (a payment, a booking, a status change).
  2. Action: send an email to your Goodshout address (not to the customer). Put the customer's email address in the body of that email. We read the first email address in the body and send the review request to it.

The customer never receives anything from this step: it's a note to us, not to them. Nothing else in the email is read, so keep the body to the customer's email address so we can't pick up the wrong one. To have the request greet them by name, add a line above it that says Name: Jane Smith (map the name from your trigger step). The name is optional.

For the email step, use the sender you already have. Sending from your own Gmail or Outlook works best, because it's connected in a couple of clicks and has no unusual limits. Zapier's built-in Email by Zapier also works, with the limit noted below.

Setting it up in Zapier

  1. Log into Zapier and click Create Zap.
  2. For the trigger, search for the app the event happens in (for example Stripe) and pick the event (for example New Payment). Connect your account, then test the trigger so Zapier can see a real, recent example to work from.
  3. Click the + to add a step. Search for Gmail (or Microsoft Outlook) and choose Send Email, then connect your account. If you'd rather not connect a mailbox, search for Email by Zapier and choose Send Outbound Email.
  4. Fill in the action:
    • To: your Goodshout address.
    • Subject: anything, for example "New job".
    • Body: the customer's email address, mapped from your trigger step. Optionally add a line above it that says Name: followed by their name.
  5. Test the step, then switch the Zap On in the top right.

Zapier's free plan gives you 100 tasks a month, and a two-step Zap like this uses one task per run. One catch: Email by Zapier is limited to 5 emails a day on free plans, so if you might send more than 5 requests in a day, use the Gmail or Outlook step instead.

Setting it up in Make

  1. Log into Make and click Create a new scenario.
  2. Add your trigger module first (for example search Stripe, or Calendly, and pick the event), connect your account, and click Run once so Make can pull through a real example. Where there's an instant version of the trigger (it's labelled "instant"), use it: see the note below.
  3. Click the + on the right of that module to chain the next step. Search for Gmail (or Microsoft 365 Email (Outlook)) and choose Send an Email, then connect your account. Make's plain Email module also works, but it needs your email provider's SMTP details, which is fiddlier.
  4. Fill in the action:
    • To: your Goodshout address.
    • Subject: anything, for example "New job".
    • Content: the customer's email address, mapped from the trigger step. Optionally add a line above it that says Name: followed by their name.
  5. Click Run once to test, then flip the scenario toggle in the top left to ON.

Make's free plan gives you 1,000 credits a month. Instant triggers only use credits when something actually happens. A trigger that checks on a schedule uses a credit on every check, even when there's nothing new, and the free plan checks at most every 15 minutes, which on its own can use up most of a month's credits. So use an instant trigger where you can.

Exact button labels move around a little as both tools update their own UI. If something doesn't quite match what's on screen, the trigger-then-email shape above still holds.

Setting the timing

Whichever method fires a request, it follows the same rule: When should these go out? on your Ways to send page. Change it there once and it applies to all three.

Common questions

Do I need to install anything or connect an account?+
No. BCC and forwarding both just use email. Forwarding works from any inbox, and BCC works from any inbox. A number of tools, such as Tradify, Xero and Fergus, also support Cc and Bcc when sending invoices. Zapier and Make need an account with them (both have a free plan) and a connection to your Gmail or Outlook to send the email, but nothing to connect on our side beyond pasting in your Goodshout address.
What does BCC mean, and will my customer see it?+
BCC stands for blind carbon copy. It's a box next to To and CC in your email app. Anyone you put in BCC gets a copy, but nobody else can see they were included, so if you use BCC your customer won't ever see your Goodshout address. If BCC isn't an option, use CC: it works just the same, but your customer can see the address. It works on any email you send a customer, not just invoices: a quote, a thank-you, or a regular message from your own inbox.
Do you save my invoices or receipts?+
No. Goodshout only picks out the customer's name and email address. We don't save the email itself, its subject, any amounts or line items, or attachments.
How do I know if it's working?+
Open Ways to send in your dashboard and check "Emails we've picked up" at the bottom of the page. Every email that reaches us shows up there, matched to a request or with a reason it wasn't.
I BCC'd it and nothing happened. Why?+
The most common reason is the customer's email wasn't detected. This can happen if your invoicing tool sends the email from a shared or generic address with the customer buried in the body rather than the To field. Check “Emails we’ve picked up” for the exact reason, and forward the same email instead as a fallback; the forwarding parser looks at the body text too.
Is this a Free plan feature?+
Yes, it works on every plan. Sending from your email (BCC, forwarding, and the Zapier/Make route) is included free. The free plan covers 25 customers a month; Pro raises it to 1,000.
Zapier or Make, which should I use?+
Whichever you already know, they do the same job here. If you're choosing fresh: Zapier has the simpler interface and the bigger library of app connections, Make is usually cheaper once you're running more automations than just this one. On either free plan a low-volume setup like this is fine, but check the limits in the steps above: Zapier's built-in email is capped at 5 a day, and Make's free credits go fast if you use a scheduled trigger.
My Zap or scenario ran but no request was created. Why?+
Check “Emails we’ve picked up” on your Ways to send page first, the same place BCC and forwarding failures show up. The most common causes are the email being sent to the wrong address (it should go to your Goodshout address, not the customer), or the customer's email being mapped from the wrong field in your trigger step. Test the action again in Zapier or Make and check the actual email it would send: the body should contain the customer's email address and nothing else.

Ready to set it up?

BCC, forwarding and the Zapier/Make route all work on the free plan, which covers 25 customers a month. Pro raises it to 1,000.