Contact Info
The Contact Info tab controls what happens the moment a lead hands over a phone number or email. You can send an acknowledgment message to the lead, fire your CRM integrations, and fire your messenger/alert integrations - independently, per contact type.
Getting here
In NZ Leads, go to Sources → select a source → Messaging Settings → Contact Info tab.
Phone section - “When phone number received”
On Yelp sources this section also covers customers who choose to share their phone number on Yelp: NZ Leads fetches their real number directly from Yelp, adds it to the lead, and the CRM and messenger toggles below apply as for any phone number.
Send confirm message to customer (phone)
- Label: “Send confirm message to customer”
- Default: on (Facebook Lead Ads sources have no confirmation message)
- Not with a Short or Long AI conversation: with AI Assistant set to a Short or Long conversation, no confirmation message is sent: while the AI is answering the lead, it reads the phone number and writes its own reply. With Predefined Messages or a welcome-only AI, it is sent.
- When on: a confirmation message is sent when the customer types a phone number in a message. If it’s in their first message, the confirmation goes out instead of the opening message. A phone that comes with the lead itself (for example on Thumbtack) gets no confirmation.
- When off: no acknowledgment message is sent.
- Use this when: you want the lead to know their number was received and what to expect next.
Trigger integrations: CRMs (phone)
- Label: “CRMs” (under “Trigger integrations:”)
- Default: on
- When on: the CRM integrations this source uses fire when the phone is captured (create/update contact, add note, etc.), except those set to Notify this integration only after the AI determines the lead is interested.
- When off: CRM integrations don’t fire at this event. They may still fire at other events (email received, new lead, etc.) depending on each integration’s own setup.
- Use this when: phone capture is the milestone that qualifies a lead for your CRM.
Trigger integrations: Messengers (phone)
- Label: “Messengers” (under “Trigger integrations:”)
- Default: on
- When on: all messenger/alert integrations (SMS, Slack, Telegram, email alerts, etc.) fire when the phone is captured.
- When off: messenger integrations don’t fire at this event.
- Use this when: you want your team notified the moment a phone number comes in so someone can call right away.
Trigger integrations: Other (phone)
- Label: “Other (Voice Agent, Call Bridge, etc)” (under “Trigger integrations:”)
- Default: on
- When on: the Voice Agent, Call Bridge and similar integrations run when the phone is captured (for example, the voice agent calls the lead). During a Short or Long AI conversation, a phone the customer types doesn’t start the Voice Agent from here: the AI can call the lead with it during the conversation instead.
- When off: those integrations don’t run at this event.
Email section - “When email received”
The email section mirrors the phone section: Send confirm message to customer and the same Trigger integrations: checkboxes (CRMs, Messengers, Other (Voice Agent, Call Bridge, etc)).
Send confirm message to customer (email)
- Label: “Send confirm message to customer”
- Default: off
- When on: a confirmation message is sent when the customer types an email in a message.
- When off: no acknowledgment message is sent.
Trigger integrations: CRMs (email)
- Label: “CRMs” (under “Trigger integrations:”)
- Default: on
- When on: CRM integrations fire when the email is captured.
- When off: CRM integrations don’t fire at this event.
Trigger integrations: Messengers (email)
- Label: “Messengers” (under “Trigger integrations:”)
- Default: on
- When on: messenger/alert integrations fire when the email is captured.
- When off: messenger integrations don’t fire at this event.
Customer Confirmation Message (shared across phone / email)
The section’s settings apply to whichever Send confirm message to customer checkboxes you’ve turned on.
Always send (even mid-conversation)
- Label: “Always send (even mid-conversation)”
- Default: on. Checking or unchecking either Send confirm message to customer box sets this box again (checked while either of them is checked), so uncheck it after setting those boxes.
- Availability: only editable if at least one “Send confirm message to customer” checkbox above is on.
- When off: the confirmation is only sent if no one from your business has messaged the customer yet in that thread.
- When on: the confirmation can also be sent after someone from your business has written to the customer.
- After a team member replies: unless Keep sending follow-ups after you reply yourself is on in the Follow-ups tab, a manual reply from your team hands the lead over to you, and from then on no confirmation is sent, even with this box checked.
- Important: the confirmation is not sent when AI Assistant is set to a Short or Long conversation (while the AI is answering, it replies to the phone number or email itself), or during Bot Quiet Hours.
Send when Yelp shares the customer’s phone
- Label: “Send when Yelp shares the customer’s phone”
- Default: off
- Availability: Yelp sources only, and only editable if “Send confirm message to customer” under When phone number received is on.
- When on: if Yelp shares the customer’s phone before your opening message goes out, the confirmation message is sent in its place. If Yelp shares it later, the confirmation is sent then. Either way the lead is marked answered and the follow-ups stop.
- When off: your opening message goes out as usual, and no confirmation is sent for a phone Yelp shares. A phone number the customer types in a message still gets the confirmation.
- Use this when: turn on if you’d rather answer with your confirmation than your opening message once you have the customer’s phone. A welcome delay of about a minute gives Yelp time to share the phone before the opening message goes out.
Message to send during business hours
- Label: “Message to send during business hours: (Configured on Yelp)” (rich-text editor)
- Availability: only editable if at least one “Send confirm message to customer” checkbox is on.
- Default: “Hi #customer_first_name#, Thank you for providing your information! We’ll get back to you as soon as possible. Thank you!”
- What it is: the confirmation message. On every source except Yelp, this message is always used.
Message to send during business OFF hours
- Label: “Message to send during business OFF hours: (Configured on Yelp)” (rich-text editor)
- Availability: only editable if at least one “Send confirm message to customer” checkbox is on.
- Default: the same message, with “as soon as possible, considering our business hours.” in place of “as soon as possible.”
- What it is: on Yelp sources only, the confirmation used when the business hours on your Yelp profile say you’re closed (or your Yelp profile has no hours). The Timing tab’s schedules don’t affect it; its Timezone is used to read your Yelp hours.
- When blank: the business-hours message is used.
- Use this when: your expected response time changes outside your Yelp hours (e.g., business hours: “I’ll call in the next hour”; off hours: “I’ll call first thing tomorrow”).
How it behaves
- The CRMs, Messengers and Other checkboxes are independent. You can fire any combination for each of phone / email.
- Order of events: for a phone or email typed in a message, the confirmation message (if enabled) goes out first and the integration triggers (if enabled) fire right after. For a phone Yelp shares, the integrations fire at once, and the confirmation (with Send when Yelp shares the customer’s phone on) goes out with or in place of the opening message.
- Repeated contact info: once a lead’s contact info has been sent to your integrations, receiving the same phone or email again doesn’t trigger them again. A different phone or email triggers them.
- Bot Quiet Hours: the confirmation message isn’t sent during quiet hours. The integration triggers still fire.
- Facebook Lead Ads: there is no confirmation message, only the Trigger integrations: checkboxes.
- Confirmation vs AI: with AI Assistant set to a Short or Long conversation the confirmation message is not sent, even after the AI has stopped answering the lead; while the AI is answering, it reads the contact info and replies itself. It is sent with Predefined Messages and with a welcome-only AI.
- Yelp phone sharing: a phone Yelp shares by itself gets no confirmation unless Send when Yelp shares the customer’s phone is on.
Troubleshooting
- Confirmation message isn’t sending: confirm AI Assistant isn’t set to a Short or Long conversation, it isn’t during Bot Quiet Hours, the relevant “Send confirm message to customer” checkbox is on and a message body is filled in. If someone from your business already wrote to the customer, check Always send (even mid-conversation); after a team member’s reply it is sent only if Keep sending follow-ups after you reply yourself is on.
- Nothing happens when the customer types a phone or email: check that Skip welcome message & follow-ups is off on Conversation Setup. With it on, a phone or email typed in a message gets no confirmation and triggers no integrations.
- CRM didn’t receive the lead when phone arrived: confirm CRMs under Trigger integrations: is checked in the phone section, and that the CRM integration itself is active on this source in the Integrations tab. A CRM set to Notify this integration only after the AI determines the lead is interested isn’t reached by this event.
- Team got double-alerted: you may have messenger integrations firing both on new-lead and on phone-received events. Pick one milestone per notification channel.
- The off-hours message isn’t sending when I expect: it is used only on Yelp sources, and “off hours” comes from the business hours on your Yelp profile, read in the source’s timezone. Check your hours on Yelp and the timezone on the Timing tab.
Questions? Email support@nzleads.com.