Leads and handoff
When a shopper wants a person, Commerce Pro offers a contact form in the chat, a WhatsApp button, or both. A contact request reaches your store by email, and optionally your CRM or automation tool, so someone can reply. It catches complaints and questions the assistant can’t answer, instead of losing them.
Set up the contact form and handoff
Section titled “Set up the contact form and handoff”- Open Geeky Bot → Commerce Pro.
- Select the Lead and handoff tab.
- Set the switches and fields below.
- Select Save settings.
| Setting | What it does |
|---|---|
| Lead capture | The contact form in the chat, for name, email and question. On its own, it opens when a shopper types “call me” or “email me”. |
| Human handoff | When a shopper asks for a person, offer the contact form and, if a number is set, WhatsApp. Also adds Talk to a human to product cards. |
| Ask for marketing consent | Adds an unticked “news and offers” box to the form, and records the exact words the shopper agreed to and when. See Marketing consent. |
| Send leads to | The address that receives contact requests. Empty uses the WordPress administration email address. |
| WhatsApp number | Your business number with the country code, for example 14155550123. See WhatsApp. Empty: no WhatsApp. |
| Keep leads for (days) | Older leads are deleted once a day. 30 to 1,095 days, or 0 to keep them. Default 365. |
| Lead webhook URL | Optional. Each new lead is also sent here as JSON. See Send leads to another service. |
Lead capture, Human handoff and Ask for marketing consent are on when you first install Commerce Pro. The Handoff readiness badge shows ✓ when Lead capture and Human handoff are both on.
Until Commerce Pro 2.2.0 the form worked only with both Lead capture and Human handoff on. Since 2.2.0, Lead capture alone turns the form on, and Human handoff decides whether asking for a person offers it.
How shoppers reach a person
Section titled “How shoppers reach a person”- Asking for a person, with Human handoff on. For example “talk to a human”, “I want to speak to someone”, “I have a problem with my order”, “I want to complain”, “live support” or “contact support”. The chat says it can pass the request to the store team and opens the form with the shopper’s message filled in as the question. With a WhatsApp number set, a Chat on WhatsApp button follows the form. With Lead capture off but a WhatsApp number set, the reply offers only the WhatsApp button.
- From a product card, with Human handoff on. Each card’s More actions menu (•••) has a Talk to a human button. It opens the form (and WhatsApp button) with “I have a question about [product].” filled in, in your store’s language.
- Typing “call me” or “email me”, with Lead capture on. This opens the form even with Human handoff off.
These phrases are recognised in English only.
The chat doesn’t collect contact details from the message itself. Nothing reaches you until the shopper fills in the form and sends it.
What the shopper fills in
Section titled “What the shopper fills in”
| Field | Notes |
|---|---|
| Your name | Required. |
| Your email | Required, and must be a valid address. |
| Your question | Optional, up to 2,000 characters. |
| Marketing box | Only with Ask for marketing consent on. Unticked. “Send me news and offers from [your store name] by email. I can unsubscribe at any time.” |
Under the fields, the form says “We use your details only to answer your request.”, with a Privacy policy link when a privacy policy page is chosen under Settings → Privacy.
After Send request, the shopper sees “Thanks. A store team member will contact you soon.”
Marketing consent
Section titled “Marketing consent”Answering a contact request doesn’t need consent, but adding the address to a mailing list does, and you need to be able to show what the person agreed to. With Ask for marketing consent on:
- The box is never ticked in advance.
- When the shopper ticks it, the lead stores the exact sentence shown, a short version code of that sentence, and the date and time. If you change your site name, the sentence and its version change too, so older records still show what each person saw.
- The store email ends with “Marketing consent: yes” and the sentence, or with “Marketing consent: no. Reply to this request only; do not add this address to a mailing list.”
- Recent leads, the CSV export, the webhook and WordPress’s personal data export show the consent record.
With the setting off, no box is shown and no consent is stored, whatever the browser sends.
Set WhatsApp number to your business number with the country code. You can type it with spaces, brackets or a plus sign; only the digits are saved, so “+1 (415) 555-0123” becomes 14155550123. A number of fewer than 7 or more than 15 digits isn’t saved.
The Chat on WhatsApp button opens WhatsApp in a new tab with “Hi! I have a question from your website:” and the shopper’s question filled in. The shopper sends the message from their own WhatsApp, so nothing passes through your site and no lead is stored. The button needs Human handoff on.
What the store receives
Section titled “What the store receives”Each request is sent by email to the Send leads to address:
- Subject: “New Geeky Bot lead from [your site name]”.
- Body: the lead ID, name, email, message, “Source: Geeky Bot Commerce Pro”, and the marketing-consent line.
- Reply-To: the shopper’s name and email, so you can reply straight from your inbox.
The request is also saved in your WordPress database with the time, the chat session and, for signed-in shoppers, their user account. If the database can’t save it, the shopper sees “Your request could not be saved. Please try again.” and no email is sent.
Send leads to another service
Section titled “Send leads to another service”Set Lead webhook URL to send each new lead to Zapier, Make, n8n, your CRM or your own code. The address must start with https://. Requests to private or local network addresses are refused, and redirects aren’t followed.
When you save the first URL, Commerce Pro creates a Webhook signing secret and shows it under the field. Copy it into the receiving service. To replace it, tick Create a new secret when saving and save. The secret is never included in the settings file from Copy settings to another site.
Each delivery is a POST with this JSON body:
{ "event": "lead.created", "lead": { "id": 42, "name": "Ana Example", "message": "Do you do gift wrapping?", "status": "new", "marketing_consent": true, "consent_text": "Send me news and offers from Example Store by email. I can unsubscribe at any time.", "consent_version": "1a2b3c4d5e", "consent_at": "2026-12-08T10:15:00+01:00", "created_at": "2026-12-08T10:15:00+01:00", "site": "https://example.com/" }}consent_at is null when no consent was given. Times are in your site’s time zone, as set under Settings → General.
The request carries these headers:
| Header | Value |
|---|---|
X-GeekyBot-Event |
lead.created |
X-GeekyBot-Delivery |
A new ID for each delivery |
X-GeekyBot-Signature |
sha256= followed by the HMAC-SHA256 of the body, keyed with the signing secret |
The lead is sent in the background, so the shopper never waits for the receiving service. If it doesn’t answer with a 2xx status within 10 seconds, the delivery is retried after 5 minutes and again after 30 minutes. Under Recent leads, a line shows when the last lead was delivered, or why the last delivery failed.
To check that a request really came from your store, compare the signature with your own HMAC of the raw body. See the example on Hooks.
Recent leads
Section titled “Recent leads”The Recent leads card at the bottom of Geeky Bot → Commerce Pro shows how many leads are stored and lists the last 10 with Name, Email, the start of the Message, Marketing (Yes or No; hover over Yes to see what was agreed to and when), Status and Date. Select an email address to write to the shopper. Each request also counts toward Leads in the key numbers.
- Status is New, Contacted or Closed. Choosing another status saves it straight away.
- Export all leads (CSV) downloads every stored lead with its status and consent record. Cells that start with a formula sign are written so spreadsheet apps show them as text instead of running them.
When handoff is off
Section titled “When handoff is off”With Human handoff off, or with neither the form nor a WhatsApp number available, there is no Talk to a human button, and a request for a person gets “I can’t pass messages to the store team from the chat.” If one of your Store Knowledge pages has “Contact” in its title, the reply links that page. See Store Knowledge.
Privacy
Section titled “Privacy”Leads hold personal data, so treat them like any other customer contact.
- Export and erase. Commerce Pro adds “Geeky Bot Commerce Pro leads and analytics” to the WordPress personal data tools under Tools → Export Personal Data and Tools → Erase Personal Data. The export includes the marketing-consent record. Erasing removes every lead with that email address or user account, and removes the person’s account and session from Commerce Pro’s activity records.
- Retention. Leads are deleted after Keep leads for (days), 365 days by default, once a day. Geeky Bot’s conversation retention setting doesn’t apply to them. Set 0 to keep leads until you erase them, or until you uninstall Commerce Pro with Delete data on uninstall turned on.
- Your privacy policy should say what the form collects, who receives it, how long it is kept, and any service your webhook sends leads to.
See Privacy and data.
Limits
Section titled “Limits”To stop spam, each visitor can send 5 contact requests in 15 minutes. After that, the chat says “Too many contact requests. Please wait a few minutes and try again.” A visitor is recognised by IP address and browser. Before Commerce Pro 2.2.0, the email typed into the form was part of that check, so a new address each time got past it. Signed-in administrators and shop managers aren’t limited.