What AI Assist does

AI Assist is the layer that turns the campaign widget from a blank text box into a guided three-step flow. It exists because most customers are not writers: when asked to “write a review,” they freeze, and the campaign loses the response.

With AI Assist enabled, a submitter picks a platform, answers one quick chip-based question about what they want to highlight, and gets a starting draft tailored to that platform’s review format. They can edit the draft freely, copy it, post it on the destination platform, then come back and claim their reward by submitting a screenshot or URL as proof.

The feature works the same way inside an embedded widget and on a standalone campaign webpage. It supports 14 platforms out of the box across review sites (G2, Capterra, TrustRadius, Gartner Peer Insights, Clutch, Trustpilot, Google, GetApp, Software Advice, Product Hunt, AppSumo) and social channels (LinkedIn, X, Facebook). Adding a new platform is a single JSON config change.

The three-step flow (platform pick, chip guidance, AI draft and claim)

A persistent progress strip at the top of the widget shows where the submitter is: Choose, Write, Claim. The active step is highlighted; completed steps turn green.

Step 1: Choose a platform. The widget shows two grouped sections: Write a Review and Share on Social. Each platform appears as a row with a favicon, the platform name, an orange AI Draft badge if AI Assist is enabled, a field-complexity tag (for example “3 fields” or “up to 280 chars”), and the reward amount on the right.

Step 2: Write with AI Assist. After selecting a platform, the user lands on the draft screen. A single question with eight chips appears at the top. The user picks one or more chips, then presses Generate my draft. The textarea below fills with a draft formatted for the chosen platform.

Step 3: Claim your reward. Once the user has copied the draft and posted it on the destination platform, they return to the widget to submit proof. A screenshot upload or a direct URL is enough: either one is sufficient on its own.

What marketers configure

AI Assist is configured per campaign, inside the existing campaign settings page. The toggle can be turned on or off at any time, including after the campaign is live; turning it off mid-campaign affects only new sessions.

Configuration is four short steps:

1. Toggle AI Assist on.
2. Write a campaign goal in one sentence. For example: “We want G2 reviews focused on ROI and ease of use for enterprise SaaS teams.” This single sentence is the only structured input the marketer provides.
3. Review the AI-generated chips. The system reads the campaign goal and proposes a chip question (for example, “What do you want to highlight?”) plus eight chip options. The marketer can edit any chip label before publishing.
4. Preview and publish. A split-screen view shows the AI Assist config on the left and a live widget preview on the right. The marketer can press Generate in the preview to see a sample draft before going live.

There is also a fallback draft field the marketer can fill in. This is the pre-cached generic draft shown to submitters if the AI service is unavailable when they reach step 2.

What submitters see

After picking chips and pressing Generate my draft, the draft appears in the same screen. The layout depends on the platform type:

• Structured platforms (G2, Capterra, TrustRadius, Clutch, Gartner) show one textarea per review field, each labeled the same way the destination platform labels it. For G2 that means “What do you like best?”, “What do you dislike?”, and “What problems does it solve?” Each field has its own Copy button and a character-minimum indicator.
• Simple platforms (Trustpilot, Google, GetApp, Software Advice, Product Hunt, AppSumo) show one large textarea pre-filled with a 100–150 word draft, with a single Copy text button.
• Social platforms (LinkedIn, X, Facebook) show one editable textarea with a live character count. X is hard-capped at 280 characters. The platform button (for example Post on LinkedIn →) opens the platform’s composer pre-filled with the current textarea contents, picking up any edits the submitter has made.

The textarea is always editable. A submitter who would rather write from scratch can ignore the chips entirely and type directly. There is no skip button because there is nothing to skip: the field is open the whole time.

Fallback when AI generation fails

If the AI generation service is unavailable when a submitter presses Generate my draft, the widget never shows a raw error. Instead, the textarea fills with the fallback draft the marketer entered at campaign setup. The submitter sees a normal-looking draft and the flow continues without interruption.

If the marketer never set a fallback draft, the textarea remains empty and the submitter writes from scratch: the always-editable textarea ensures there is no dead-end state.

The fallback only kicks in for that one generation attempt. The next generate request is a fresh attempt against the AI service. The submitter is not locked into the fallback for the rest of the session.

Editing and re-generating

The draft is a starting point, not a final answer. Submitters can:

• Edit any field freely, before or after pressing Copy. The Copy button picks up the current textarea contents, not the original AI output.
• Change chip selections and press Generate my draft again to get a new draft. The previous draft is replaced in the textarea. There is no version history in v1 and no regenerate-without-changing-chips button.
• Ignore the chips and write the whole thing themselves. Generate stays available but is not required.

For social platforms, the destination-platform button (for example Post on X →) builds the deep link at click time, so any last-second edits in the textarea are captured before the link opens. The pre-fill works against the LinkedIn share composer and the X intent URL.

Submitting and claiming the reward

Once the submitter has posted on the destination platform, they return to the widget. Step 2 turns green and step 3 activates. The header reads “Submit proof to claim your reward.”

There are two proof methods and either one is sufficient on its own:

• Screenshot upload. A drag-and-drop zone with a click-to-browse fallback. After upload, the widget shows a thumbnail with the filename and a Remove link.
• URL field. A direct link to the published review or social post, for example https://www.g2.com/reviews/....

The Submit for review button stays disabled until either a screenshot is uploaded or a URL is entered. Once submitted, the proof is sent for manual review. Automated verification is not part of v1.

Troubleshooting (no draft, slow generation, wrong tone)

A few common issues and how to handle them:

• No draft appears after pressing Generate. Check the textarea: if the marketer set a fallback draft, that is what is shown when the AI service is down. If the textarea is empty, the AI service is unavailable and no fallback was configured. Type a draft from scratch; the flow still completes.
• Generation is slow. First-time generation can take several seconds. The button shows a loading state while it runs. If it hangs for a long time, refresh the page and try again; chip selections are stored in the session and will return.
• Draft tone or focus is off. The draft is generated from the campaign goal the marketer wrote plus the chips the submitter picked. If the tone is consistently wrong across submitters, the marketer should revisit the campaign goal sentence and tighten it, then re-publish.
• X draft is over 280 characters. The field enforces the limit; the submitter has to trim before the platform button opens. If the AI draft comes in long, the submitter edits down before pressing Post on X →.
• Submitter wants to change platform mid-draft. They can go back to step 1 from the progress strip. Their chip selections do not carry across platforms; chips are per-platform because draft formats differ.

For proof submission rules, see Proof submission rules. For the social posting flow specifically, see Social Advocacy.