You paste two lines on your site. A visitor types their website and their email, and a few minutes later they get a report on how visible their brand is inside AI answers, with your logo on it, sent from your address, opening on your domain.
You get the lead in Prospecting > Leads with the report already attached: the score, the prompts their brand did and did not appear in, and one click through to the report, where the competitors that came up instead are named.
It is the same product you sell, handed over before anyone has agreed to pay for anything.
The widget only goes live once your agency looks like an agency to the visitor. Six things, all shown as a checklist in White label > Widget:
Requirement | Where | Why the visitor needs it |
|---|---|---|
Your app is served on your domain | Domains | The report opens on your domain, not ours |
Your sending domain is verified | Otherwise the report email never arrives | |
Your agency has a name | Branding | It signs the email and the report |
You published a privacy policy | Branding | The form collects an email, so they have to be able to read your policy |
You published your terms | Branding | Shown next to the consent line |
You have a support contact | Branding | Somebody who replies has to be you, not us |
The switch stays off until all six are green. It can always be turned back off.
White label > Widget > Install gives you two lines:
<script src="https://app.youragency.com/embed/widget.js" data-key="wgt_..." data-target="rp-widget"></script>
<div id="rp-widget"></div>Paste them where you want the form. It sizes itself to whatever space it lands in.
Allowed origins is the list of sites that may use your key. Up to 20. A copy of your snippet on a site that is not on the list draws the form and then refuses the submission.
The form itself is framed from our origin so the captcha has a single hostname to trust. The page around it, the loader and the report link are all yours.
The form's page cannot be opened on its own. It only runs inside a frame.
New key invalidates the snippet already on your site, so replace it there straight away.
Setting | Range | Default |
|---|---|---|
Prompts per report | 3 to 20 | 5 |
AI engines | Any mix of the ones on your plan | Standard four |
When the report runs | Straight away, after email confirmation, or automatic | Automatic |
Leads per day | 1 to 500 | 20 |
Leads per month | 1 to 5000 | 200 |
Alert thresholds | Up to four percentages of the daily cap | 80 and 100 |
Form fields | Website and email always, name and company optional | Website and email |
Headline, button and consent line | Your own copy | Ours, in your product name |
Privacy link | Any URL you publish | Your branding privacy URL |
Allowed origins | Up to 20 | Empty, so nothing works until you add yours |
Meeting link, host name and role | Any scheduling URL | None |
Reuse window | 7 to 90 days | 30 |
Who hears about a new lead | Any of your team | The owner |
Retire quiet lead brands after | 30 to 720 days, or never | 90 |
Automatic is worth understanding: the report runs at once when the signals are good, and asks for an email confirmation first when they are not. Either way the lead is captured the moment the form is sent, so you never lose the contact.
A lead report is priced like any other report: prompts x credits per prompt, where a prompt costs 1 credit on the standard engines and 1 more for each premium engine you add. The brand research behind it is included.
Configuration | Credits per lead |
|---|---|
5 prompts, standard engines | 5 |
5 prompts, standard plus one premium | 10 |
10 prompts, standard engines | 10 |
The tab shows the number for your current settings, and next to it what your leads actually cost this month, read from your credit ledger. The two differ when a report failed halfway or a lead inherited a report that already existed.
You pay, always. The visitor never sees a price.
A public form that spends credits needs a floor. Most of it is invisible to a real visitor:
A captcha runs in the background and only shows itself when it is unsure. The Install section shows whether it is verifying.
Two invisible checks: a field only a script would fill in, and a minimum time on the form.
Duplicates: the same address or the same website inside your reuse window gets the report you already paid for instead of a new one.
Caps: the daily and monthly limits are enforced as the lead is saved, not after. Past the cap the lead is still captured, with no report run, so a busy day costs you nothing and loses you nobody.
Automatic pause: a sudden spike against your own baseline pauses the widget and tells you why. Resume is one button.
Throwaway addresses and addresses that cannot receive mail are asked to confirm first.
Whatever the checks decide, the contact is saved. The only thing that ever gets deferred is spending your credits.
No. The 100 client seats count seats over brands you created. A lead's report brand is a different type and sits outside that cap, so a good week of leads can never push out a client who pays you.
The flow stops. No seat is created, nothing is written on their existing account, and they get a note telling them to open the report from the account they already have. You see the lead as pending.
The most common reason is our global suppression list: if that address unsubscribed from any email we have ever sent, it stays suppressed even when the email is yours. The Leads tab shows the delivery state, and you can copy the report link and send it yourself.
One to three minutes in normal conditions. The visitor sees the progress while they wait, and after thirty seconds they are offered the option to have it emailed instead, so a slow run never costs you the lead.
No. The report opens on your domain and the email leaves from your sending domain, so both have to be verified first. That is what makes the whole thing look like yours.
Leads and Webhooks - Work the leads and post them to your own backend
Agency Domain - DNS records, verification, and SSL
Email Sending - Send from your own domain
Client Access - What a lead sees once they claim their report
Contact us at [email protected]