The Save Lead node adds the visitor to Leads, where your team moves each lead from New through Contacted and Qualified to Won or Lost. Each lead links back to the conversation it came from.
{{email}}{{intent}}, so your team can filter the board by themA lead needs at least a name, an email or a phone number.
Pick a Marketing team to route the lead to that team, or leave it empty to use the deployment's default marketing team, or the flow's. Pick a marketing agent under Assign to to give the lead to them. Leave it empty and the deployment's default lead assignee takes it, or the flow's, as long as they are on the lead's team. When nobody is named, the team hands each new lead to its members in turn, starting with whoever has gone longest without one. The person it goes to is emailed.
If a lead with the same email, or failing that the same phone number, is still open, that lead is updated instead of a second one being added, and it keeps its team and the person following it up and, unless this step picks one, its category, and gains this step's tags. Only the values this step has are written, so a phone number saved earlier stays when this step did not ask for one. Once a lead is marked Won or Lost, or archived, the same person coming back starts a new lead.
Each lead counts as one row of your plan's stored row allowance, which it shares with your tables. When the allowance is full, a returning visitor's lead is still updated, but a new lead takes Error.
When you try the flow in the editor's test chat, or run it through the agent API, the step saves a test lead. Test leads stay off the board, nobody is assigned or notified, they don't count against your allowance, and they never update a real lead. They are deleted after a week.
{{variable}}.saved
{{variable}}.created
{{variable}}.lead_id
Name
handlebars
The visitor's name.
Supports Handlebars syntax:
{{variable_name}}
Email
handlebars
Used to recognise the visitor when they come back.
Supports Handlebars syntax:
{{variable_name}}
Phone
handlebars
Used to recognise the visitor when there is no email.
Supports Handlebars syntax:
{{variable_name}}
Message
handlebars
What the visitor is looking for.
Supports Handlebars syntax:
{{variable_name}}
Other details
key_value
Anything else to keep with the lead, each under a name of your choosing.
A list of name and value pairs. Add one pair for each thing you want to keep. Both the name and the value can use variables from earlier in the flow, and a pair whose name comes out empty is left out.
Marketing team
marketing_team_selector
The team the lead goes to. Empty uses the deployment's or the flow's default marketing team.
Pick one of your workspace's marketing teams. New leads routed to a team are handed to its members in turn. Marketing teams are managed under Marketing.
Assign to
workspace_member_selector
The marketing agent who follows the lead up. Empty uses the deployment's or the flow's default lead assignee, or the team's members in turn.
Pick one of your workspace's marketing agents. When a team is picked on the same step, only that team's members are offered. Marketing agents are managed under Marketing.
Category
lead_category_selector
The lead category to file the lead under. Empty leaves a returning visitor's lead in the category it has.
Pick one of your workspace's lead categories. The lead is filed under it, and your team can filter the leads board by category. Lead categories are managed under Marketing.
Tags
handlebars
Comma separated tags to add, such as VIP, {{intent}}. New tags join the workspace's list; a returning visitor's lead keeps its tags and gains these.
Supports Handlebars syntax:
{{variable_name}}
This node stores its output in a variable that can be referenced in subsequent nodes using the {{variable}} syntax.
{{variable}}.saved
boolean
Whether the lead was saved
{{variable}}.created
boolean
True when this step added a new lead rather than updating an open one
{{variable}}.lead_id
number
The saved lead's id
output
error