Review campaign builder

Hard rules

• Nothing is created, sent or spent until the person has seen the full summary and confirmed it in plain words. An earlier go-ahead does not count.
• create_review_campaign starts the campaign as soon as confirmed is true. send_gmail_review_requests queues emails at once, has no idempotency key and has no delivery lookup. Never retry the Gmail send after an uncertain result. Before retrying a campaign create, check show_review_campaign and reuse the same idempotency key.
• A campaign is not incentivized unless the person states a reward amount and a review goal.
• Contacts flagged do not email, unsubscribed or opted out in the CRM are always excluded.
• Never invent a contact, an email address or a score.

Inputs

Ask once for anything missing.

1. Promoter definition: the CRM or survey field and the threshold that marks a promoter. This differs by customer, so never guess it.
2. The G2 product, if the person owns several.
3. Send method: g2_sends (G2 emails the recipients), vendor_sends_manually (G2 builds a landing page and email template and the person sends it), or Gmail send (the person's Gmail connected in myG2, optionally tied to a manual campaign's landing page).
4. Incentive: none by default, or a reward per review of 5, 10, 20, 25, 50, 75 or 100 USD plus a review goal.
5. Campaign title and start date. The title must be unique for the product. The start date must be a Tuesday or Thursday at least two business days away.

Step 1: Resolve the G2 product

Use list_my_products. If the person owns several products, ask which one.

Step 2: Pull promoter candidates from the CRM

Apply the person's promoter definition. Return contacts with an email address at the accounts that meet it. Find fields by meaning: email, account, role or title, opt-out or do-not-contact flags, and the promoter score. Record the exact field names used. If the promoter definition matches no field, ask the person which field to use.

Step 3: Pull recent reviewer companies from G2

Call list_market_intelligence_product_reviews for the person's product with the fields user_company_name and user_updated_at, and filter_updated_at_gt set to 12 months back. Follow the cursor until the pages run out. Matching to CRM accounts is by company name, so mark every match approximate.

Step 4: Add scores and check exclusions

If a survey or customer success platform is connected, read NPS, CSAT or health scores for the candidates. Check the support desk for open escalations and billing for overdue invoices. Write Not connected for any source that is missing, and say the list was not checked against it.

Suppression rules

These are starting defaults set by the blueprint author. Adjust them for your own customers.

Always exclude

• Contacts flagged do not email, unsubscribed or opted out in the CRM.
• Contacts with no valid email address.
• Contacts the person lists as excluded.

Exclude when the source is connected

• Accounts with an open escalation or an open high-severity ticket in the support desk.
• Accounts with an overdue invoice in billing.
• Accounts that left a G2 review in the last 12 months, matched by company name. Mark this approximate in the output, because the match is by name.

One contact per account

Choose the contact with the highest promoter score. If scores tie, choose the most senior title. If neither is available, ask the person. The person may allow several contacts per account.

Reporting

• Show every excluded contact with the rule that excluded it.
• Name every suppression source that was not connected, and say the list was not checked against it.

Plain text. On the Gmail path G2 appends the review link. Mention an incentive only when the campaign is incentivized.

Subject: A request: would you review {{product_name}} on G2?

Hi {{first_name}},

You have used {{product_name}} for a while, and what you think of it matters to people choosing software. Would you write a short review on G2? It takes about five minutes.

{{incentive_line}}

Honest feedback helps those buyers decide, and it shows us where we fall short.

Thank you, {{sender_name}}