Lead qualification
Use Lead qualification when you want every customer enquiry to include a consistent set of confirmed details. Wabery records the enquiry in Qualifying. Your team decides whether it becomes qualified, won, or lost.
Leads does not scrape prospects, start campaigns, predict a sale, collect payment, or promise an outcome.
Set up the questions
Section titled “Set up the questions”- Open Leads, then switch to Lead settings.
- Describe the business outcome you want from an enquiry.
- Answer the optional setup questions when they help Wabery suggest more useful customer questions.
- Review every suggested field. Edit, reorder, or remove fields that the team does not need.
- Name the person or team responsible for follow-up.
- Save the configuration, then turn on Lead qualification.
Wabery can use the active project’s name, description, and business brief to prepare more relevant starter questions. Treat them as a draft: the business is responsible for deciding what it is appropriate to collect.
New setups include customer-confirmed signals for desired outcome, timing, and decision readiness. Do not ask for sensitive information unless the workflow genuinely needs it and you have an appropriate reason to collect it.
Publish the agent
Section titled “Publish the agent”Lead qualification and the agent are controlled separately:
- The Leads switch controls whether the saved lead actions are available.
- Agent → Review & publish controls which agent draft answers customers.
There is no separate Leads approval or launch page. Organization owners and administrators can publish the project agent without requiring a client approval. You can still invite the client to review their project and business details before launch.
For WhatsApp, connect and publish the project’s business number before relying on live lead actions there. Other supported customer channels use the project’s active agent and routing. Provider-specific limitations still apply to each channel.
What the customer sees
Section titled “What the customer sees”The agent gathers the configured answers and asks the customer to confirm the exact details. Wabery creates the lead only after that confirmation. Repeated delivery of the same confirmed submission returns the existing result rather than creating a duplicate lead.
Removed fields are not shown in new customer-facing results. Invalid calendar dates are rejected instead of being stored as a valid answer.
Review and update leads
Section titled “Review and update leads”Open Leads to inspect:
- the confirmed answers;
- the responsible person or team;
- the current stage;
- the interest signal; and
- the event history.
New leads start in Qualifying. An authorized person deliberately moves them to another stage.
The interest signal groups confirmed timing and readiness answers as Hot, Warm, Exploring, or Unknown. It is a follow-up aid, not a probability of purchase. Older leads without the required answers remain Unknown.
Give a client access
Section titled “Give a client access”Invite the client from Settings → Project access. A View-only person can read leads. An Editor can update their stages and details. Project access does not expose your organization billing, credentials, or other client projects.
Enable Email activity alerts when the invited person should receive an email for new leads. They can turn those alerts on or off from their project workspace.
Optional WhatsApp staff alerts
Section titled “Optional WhatsApp staff alerts”Choose Manage alerts from Leads or Bookings to open the shared project alert settings. Select the connected business number, a staff recipient, and New leads.
The recipient must consent and verify their number. The project owner must accept Meta’s message charges, complete the alert test, and activate the policy. WhatsApp staff alerts and email activity alerts are independent; neither is a silent fallback for the other.