Lead alerts, contact capture and CSV export
Save contact details visitors type in the chat, get an email or a Slack message for each new lead or form submission, and filter and export your leads as CSV.
Besides the lead form, your agent can save an email address or phone number that a visitor simply writes in a message. This page covers that capture, the email and Slack alerts for new leads, and the lists of leads, bookings and return requests on the Leads tab.
Save contact details written in the chat
The switch Save contact details written in the chat is on by default. When a visitor writes something like "my email is ana@example.com", the address is added to your leads and the agent confirms it. This works with or without the lead form, and these leads carry a From chat badge.
What is recognized:
- Any email address.
- A phone number in international format, starting with
+or00. - A local number only when a phone word is in the same message, so prices and dates are not saved. Phone words are recognized in English, German, French, Italian and Spanish, for example "call", "phone", "number", "Telefon", "Handy", "téléphone", "portable", "telefono", "cellulare", "teléfono" or "móvil".
- A local number without a leading 0, such as an Italian or Spanish mobile number, only when a phone word comes right before it, as in "cellulare" or "móvil" followed by the number.
- Order, tracking, invoice, customer, account, reference, booking and VAT numbers are ignored, in the same languages. A number counts as one of these when such a word sits right beside it, for example "order number", "Bestellnummer", "numéro de commande" or "partita IVA".
- Your business's own email address or phone number, found in your instructions, the agent's earlier replies or your knowledge, is never saved as the visitor's.
Email alerts for new leads
- On the Leads tab, switch on Email when a new lead arrives.
- Keep Send to me ticked to get the alert at your account email.
- Under Also send to, add up to 5 more addresses, such as a teammate or a shared inbox. Type an address and press Enter or click Add.
- Click Send test email. A sample goes to the recipients in the form right now, even before you save. Its subject starts with
Test:. - Click Save lead settings.
At least one recipient is required: either Send to me or one address. The same recipients get the emails of hand-off by email, even while lead alerts are off. They also get an email for each chat form submission, but only while Email when a new lead arrives is on.
Each alert has the subject New lead from followed by the agent name and the contact, with the lead's name in front of the contact when they gave one. It contains the name, email address and phone number the lead gave, their answers to your custom fields, up to the visitor's last 3 messages and a See the conversation button. Every recipient gets a separate email, and replying goes straight to the lead's email address.
Only a new contact sends an alert. A returning visitor who submits the same details again does not. To stop a flood of fake submissions from becoming a flood of email, each agent sends at most 30 alerts per hour; leads beyond that are still saved and listed.
For a count of new leads per agent instead of one email per lead, turn on the daily summary email; see Conversations and stats.
Slack alerts
The Slack alerts card at the bottom of the Leads tab posts a message to a Slack channel when this agent gets a new lead, a visitor asks for a person by email or in live chat, a visitor sends one of your chat forms, a visitor books a meeting through Booking with Cal.com or Calendly, or a visitor asks to return or exchange items of an order through Order status and returns. It uses a Slack incoming webhook: intoCHAT only posts to that one channel and reads nothing from your Slack. The alerts don't chat with anyone; to let the agent answer questions in Slack, see Slack agent.
Connect Slack
- In Slack, create an incoming webhook for the channel the alerts should go to. How to get a webhook URL in the card lists the steps: create an app for your workspace in Slack's app settings, or open one you already have, turn on Incoming Webhooks, add a new webhook and pick the channel. Your workspace may need an admin to approve the app.
- Paste the URL into Slack webhook URL.
- Under Post a message for, keep the events you want ticked: New lead, Hand-off request, Form submission, Booked meeting, Live chat request, Return request and Approval request. All seven are ticked at first, and at least one is required.
- Click Connect Slack.
- Click Send test message. Below the buttons you see "Test message sent. Check your Slack channel." or the reason Slack gave, for example that the channel is archived or the webhook was removed.
Only incoming webhook URLs are accepted. They start with https://hooks.slack.com/services/, or https://hooks.slack-gov.com/services/ for GovSlack. Links from Slack's Workflow Builder aren't supported.
Anyone with the URL can post to the channel, so treat it like a password. After you save, the card shows it only in part under Connected to, with the last four characters. To change the events, tick or untick them and click Save. A connection saved earlier keeps its events, so tick Form submission, Booked meeting, Live chat request or Return request and click Save to add them. Replace lets you paste a new URL. Disconnect stops the alerts and deletes the saved URL; to connect again, you paste a webhook URL.
What the messages contain
- New lead: the agent name; the lead's name, email address and phone number, as far as they gave them; whether the lead came from the lead form or the chat; their answers to your custom fields; and links to the conversation and to the Leads tab. Unlike the email alert, it doesn't include the visitor's messages.
- Hand-off request: the agent name; the visitor's address to reply to; their country and the page the chat started on, when known; the agent's summary under What they need; and a link to the conversation. Your team still replies to the visitor by email. A hand-off from the Playground is marked as a test.
- Form submission: the agent name, the form name, each answer the visitor filled in under its label, and links to the conversation and to the form submissions on the Leads tab.
- Booked meeting: "New meeting booked", the agent name and the event type's title; When, with the date, the start and end time and the visitor's time zone; the Name and Email the visitor entered; and links to the conversation and to the bookings on the Leads tab. When you must confirm the booking in Cal.com first, it says "Meeting requested (confirm it in Cal.com)" instead.
- Live chat request: "A visitor wants to chat with a person" on the agent; the visitor's country and the page the chat started on, when known; their last message; a Take it in the Live chat inbox link, a link to the conversation, and a note that the visitor is told nobody could join if nobody joins in time.
- Return request: "New return request" or "New exchange request" on the agent, with the order number; the order's Email and the Items; the visitor's Reason; and links to the conversation and to the returns on the Leads tab.
- Approval request: "Approval needed" on the agent with the action's name (and the procedure's, if any), its Inputs with credentials shown as Hidden, when it expires, and links to the Approvals page and the conversation. Sent once for each request; see Team approval for actions.
When alerts are sent
- Slack alerts go out at the same moments as webhooks. New lead is sent once per new contact; a returning visitor who gives the same details sends none. Hand-off request is sent only when the hand-off email went out, so hand-off by email must be on in the Setup tab. Form submission is sent once for each submission. Booked meeting is sent once for each booking, also for bookings made in the Playground, which are real. Live chat request is sent once for each request, when the agent asks your team to join, so live chat must be on in the Setup tab and someone from your team must be online. It is sent whether or not anyone joins. Return request is sent once for each return request, so Returns and exchanges must be on in the Orders card on the Actions tab.
- They don't depend on the email alerts above. They are sent whether Email when a new lead arrives is on or off.
- intoCHAT tries once, and once more after a network error, a timeout or an error on Slack's side. There is no delivery log, and a message that still fails isn't sent later. Use Send test message to check the connection.
- A duplicated agent keeps the Slack connection and posts to the same channel. Replace or disconnect it in the copy if that's not what you want.
The leads list
Collected Leads shows 10 leads per page with these columns:
- Contact: name, email and phone, with the From chat badge where it applies.
- Answers: the lead's answers to your custom fields, each after its field label. A renamed field shows its current label, a removed one the label it had when answered. On smaller screens this column is hidden and the answers appear under the contact.
- Conversation: the visitor's first message. Click View chat to read the whole conversation. If it was deleted, the lead stays and shows "Conversation deleted".
- Captured: when the lead was first saved.
- Last seen: the latest visit, with a "came back" count when the same person submitted again.
Each contact appears once. If a visitor gives an email address or phone number that is already in the list, the existing row is updated: a blank name is filled in, and newer answers replace older answers to the same field.
Filter the list with Field (All, Email only, Phone only), Start date and End date. Use Refresh to load new leads, and tick rows to remove them with Delete selected.
Export to CSV
Export CSV downloads every lead that matches the current filters, across all pages. The file has these columns: Email, Phone, Name, one column per custom field, Session ID, Conversation ID, Collected At, Last Seen At, Submissions and Source (Form or Chat). Custom field columns use the current labels, in the form's order. A field you removed gets a column after them when an exported lead answered it. Dates are in UTC. Values that start with +, =, - or @ get a leading apostrophe, so spreadsheet apps show a phone number as text instead of reading it as a formula.
Bookings
The Bookings card, below Form submissions, lists the meetings visitors booked from the chat through Booking with Cal.com or Calendly, newest booking first, 20 per page. Until there is one, it says "No bookings yet."
| Column | Content |
|---|---|
| Meeting | The date, start and end time of the meeting, in your own time zone, and below it when it was booked |
| Visitor | The name and email address the visitor entered, and the visitor's time zone |
| Event | The event type's title at the time of booking. A meeting your event type still needs you to confirm in Cal.com is marked "awaiting the host's confirmation". |
The chat icon at the end of a row opens the conversation the meeting was booked in. Refresh loads new bookings.
The list shows what was booked from the chat. Reschedules and cancellations happen in Cal.com or Calendly and don't change the list. Bookings can't be exported or deleted here, aren't leads, and send no email alert. To get them elsewhere, use Booked meeting in the Slack alerts or the booking.created webhook.
Returns
The Returns card, below Bookings, lists the return and exchange requests visitors made in the chat through Order status and returns, newest first, 20 per page. Until there is one, it says "No return requests yet."
| Column | Content |
|---|---|
| Date | When the request was made, in your own time zone |
| Order | The order number and the order's email address |
| Request | Return or exchange, and the items with their quantities |
| Reason | Why, in the visitor's words |
| Status | Mark handled, or Handled once you marked it. The arrow next to Handled marks it as not handled again. |
Nothing changes in your store when a request comes in: handle it there as usual, then click Mark handled. Viewers see the list but can't mark requests. The chat icon at the end of a row opens the conversation. Export CSV downloads every request with the columns Date (UTC), Order, Email, Kind, Items, Reason and Status. Refresh loads new requests.
Each new request is also emailed to the people who get the lead alerts above, while lead alerts are on, and can be posted to Slack as Return request and sent as the return.requested webhook. Requests aren't leads.
Send leads to other tools
To send every new lead to your CRM or an automation tool as it arrives, add a webhook in the Webhooks card on the Leads tab, under Webhooks & Slack. See Webhooks. To get a message in a Slack channel, use Slack alerts, described above; it needs no server of your own.