Prospecting > Leads. A lead is a prospect that came from your widget or your hosted page, so everything in Prospecting applies to it. The tab adds what only the app can tell you: what the report found, what it cost you, and whether the visitor became a user.
Column | What it tells you |
|---|---|
Company | The business the visitor named, and the email they left |
From | Your site (the form on your own pages) or Your page (your hosted page) |
Stage | Where the lead is: New, Generating, Ready, then the follow-up stages (Contacted, Following up, Replied, Won, Lost) |
Score | The Visibility score of the report they received |
Named | How many of the report's answers named their brand. One prompt asked on 4 AI platforms is 4 answers |
Credits | What this lead actually cost, read from your credit ledger |
Account | Whether they claimed an account on your domain from the report email, and whether that seat is still there |
Whether the report email arrived: Delivered, Bounced, Marked as spam or Unsubscribed | |
Captured | When the form was sent |
A lead at New usually means the day's limit was reached or the visitor still has to confirm their email. A report that fails sends the lead back to New, so it can run again.
Company, Score, Account and Captured sort across every page, not only the one you are looking at. You can filter by stage, by origin and by claimed or not, and search company, site or email. Changing a filter takes you back to the first page.
Export downloads the filtered list as a CSV that Excel opens with accents intact. It holds only what the visitor gave you.
Click a row. The panel shows the score, the answers that name them, the credits spent and each email (the report, the confirmation, the claim link), then two things worth reading:
What the onboarding collected. Once the lead claims their account, the agent asks a few questions to set their brand up. Their answers are here: their role, where they sell, who they sell to, who they compare against and what they want. It is qualification you did not have to run
Conversation. The messages they exchanged with the agent, in order
Both stay empty until the lead claims their account, and the panel says so.
From the same panel you can Send again the report, the confirmation or the claim link (a new claim link replaces the one they hold), and Delete for a data request when somebody asks you to remove their data. Deleting removes the lead and the report brand and seat that came with it, unless another lead still uses that brand. It is refused once the brand has become a real client brand; delete it from Brands instead.
Set them up in the Webhooks section of White label > Widget, or on app.rankprompt.com under Settings > API, Webhooks tab, with Account picked under Webhooks for. Both show the same endpoints. Only the account owner sets these up. You can have up to 5 active endpoints, each subscribed to any of four events:
Event | When it fires |
|---|---|
| The form was sent and the lead is saved |
| The report finished and the email went out, with the share link |
| The report could not be made, so no report email went out |
| The lead opened an account on your domain |
Every event carries the lead as lead_id, so the four match on one field:
Event | Fields in |
|---|---|
|
|
|
|
|
|
|
|
On lead.report_failed, report_id is null when the report never started. failure_reason is out_of_credits (the account ran out of credits), stuck (the report stopped moving and was failed after six hours) or engines_failed (no AI platform answered any prompt), and null for any other cause. Treat a value you do not know like null, since the list can grow. The same lead can fail more than once, for example when the visitor confirms again after a failure, and every failure is its own event.
Send as picks the format: Signed JSON (the event itself, for your server, Zapier, Make or n8n), or a readable Slack or Discord message with the lead's company, site and a link to your Leads table. Send a custom header adds a header name and value, for catch hooks that check one.
Every delivery is signed. Verify the X-RP-Signature header with the signing secret shown once when you create the webhook. Rotate secret makes a new one; the old one keeps verifying for 24 hours, so nothing drops while you deploy.
Send test sends a sample of any event you subscribed to, marked "test": true, and shows the answer and how long it took. A failed delivery is retried with a growing delay. An endpoint that keeps failing turns itself off and you get a notification; fix it and click Enable.
Expand an endpoint for its delivery log: recent attempts with the response code and time, tests marked as such, and Replay for any of them. A replay is a new delivery of the same event: the delivery id (X-RP-Delivery-Id) is new, while the event id (X-RP-Event-Id) and the body are the original's, so a receiver that removes duplicates by event id treats it as the event it already has.
These account webhooks are separate from the brand webhooks on the same tab (Brand under Webhooks for). Nothing here changes those, or the public API.
No. Client seats count seats over brands you created. A lead's report brand is a different type and sits outside that cap.
The flow stops: no seat, nothing written on their existing account, and the lead shows Has an account. They get a note telling them to open the report from the account they already have.
The Email column says why: a mailbox that refused it, a spam report, or an address that unsubscribed from email sent through Rank Prompt, which gets none, even from you. Copy the report link and send it yourself.
A few minutes. The form tells the visitor to watch their inbox, and the report is emailed as soon as it is ready.
Export the CSV, or point a webhook at a Zapier, Make or n8n catch hook.
Lead widget: set the widget up and price it
Prospecting: the outbound half of the same page
Client access: what a lead sees once they claim their report
Email [email protected] and I'll help.
