Follow this simple path: tell Lead Intel what you sell, find the right people, send a helpful message, and keep up with replies. You do not need technical knowledge.
In one sentence: your Product gives the system context, your Campaign gives the outreach a purpose, your Discovery Job finds matching people, and Leads are the people you review before they enter your outreach.
Purpose: a Product holds the shared information Lead Intel needs to understand your offer. Every Campaign, Discovery Job, Lead, message, booking, and report stays connected to one Product.
Product: “Bookkeeping for small shops.” Customer: “Independent shop owners in Nairobi.” This is the foundation; it is not a search or a list of leads.
Purpose: a Campaign explains what you want to achieve with this group of leads. It sets the audience, objective, message angle, communication channels, booking link, and optional automation.
The Product explains your business once. The Campaign is one specific effort, such as “September Nairobi salon outreach.” One Product can have many Campaigns.
Purpose: a Discovery Job is a set of search instructions. It searches selected sources using keywords, location, filters, and a result limit. It does not send messages.
The Campaign gives the search extra context about the audience and goal. Leads found by a linked Job are assigned to that Campaign, so you do not have to organise them one by one.
Purpose: Leads are the actual people or businesses returned by Discovery. Each Lead can contain source details, available contact information, a score, status, Campaign, and message history.
Select the Lead and assign it to a different Campaign for the same Product. A Lead can also remain unassigned until you decide how to contact it.
Purpose: Work Queue turns Campaign and Lead activity into a practical to-do list. It is where you handle replies, manual messages, reminders, and other actions that need a person.
No. It is mainly your human action list. When Campaign auto-send is enabled, eligible scheduled messages can go out automatically while replies and manual work return here for attention.
Purpose: outreach moves a Lead from a record into a real conversation. Manual sending lets you approve each message; Campaign automation follows the channel order and wait times you configured.
Before an eligible send, Lead Intel checks the Product, Campaign, Lead, channel readiness, credits, score rules, and sending window. Automation remains optional and can be paused.
Purpose: Bookings gives an interested Lead a clear next step. The Campaign can include a booking link, and each confirmed meeting stays connected to the Lead and Product.
No. Use it when a meeting is the Campaign’s next action. A Campaign that asks people to visit a page or reply with information may use a different link or no booking link.
Purpose: reports summarise the records created by the earlier steps. The Funnel follows Leads from found to contacted, replied, booked, and converted.
Reports use activity recorded by Lead Intel and supported provider events. Check the relevant Lead and Outreach Log before assuming an unreported event never happened.
Purpose: Settings keeps the workflow operational. This includes communication connections, WhatsApp templates, sending hours, booking availability, team access, plan, and credits.
Start with one channel you can manage well. Add more channels and automation only after the Product → Campaign → Job → Leads flow is working clearly.
A product is the thing you are selling. Every lead, campaign, message, and report belongs to one product. You can have multiple products — for example if you run two businesses or sell different services to different audiences — and switch between them with a single click from the top navigation.
Its place in the workflow: start here. The Product supplies the shared business context used by the Campaign, Discovery Job, Leads, messages, bookings, and reports that follow.
Keep product descriptions specific. "I help property managers reduce vacancy by filling empty units faster" produces sharper AI messages than "property software".
Discovery jobs find real businesses that match your target profile. You choose where to search (TikTok, Google Maps, Instagram, and more), set a search term and credit budget, and press Run. The system scans, deduplicates, and imports the results directly into your Leads list.
Its place in the workflow: the Campaign defines who you want and why; the Discovery Job decides where and how to search. Link the Job to the Campaign so the Leads it creates enter the correct outreach plan.
Where supported, you can see an estimated credit cost before a run and review the recorded result afterwards. Discovery jobs can also use a supported schedule. Check the job status and recorded outcome rather than assuming every scheduled run will complete.
Lead Intel reduces duplicate records across jobs for the same product. Review the lead and available source details before contacting someone, especially when a source returns incomplete information.
The Leads page is your master list of every prospect the system has found. Each lead gets a score out of 100 using available profile details, structured checks, and AI-assisted analysis. Higher scores are useful for sorting, but you should still review the lead.
Its place in the workflow: Leads are the output of Discovery, not another search setting. Review them here before the Campaign sends or queues outreach.
Every lead has a status that tracks where they are in your funnel:
Click any lead to open their full profile — contact details, AI score breakdown, full message history, and activity timeline all in one place.
A campaign is your outreach plan: a group of leads, a set of channels, and a message for each. The campaign editor walks through four steps:
Its place in the workflow: create the Campaign after the Product and before the Discovery Job when you want newly found Leads to enter a specific outreach plan automatically.
Automation is optional. You can start with manual sending, learn what works, and switch on automation later:
Auto-send campaigns can chain multiple channels together in sequence. A typical setup might be: WhatsApp on day 1 → SMS on day 2 → Email on day 5. You choose the order and the gap between each channel. The system sends each lead the next channel in the sequence only after the configured interval has passed since the previous send.
A safely matched reply stops the remaining sequence for that lead and brings the conversation back for human attention.
Product Settings controls the guardrails used by automatic sending:
Auto-send is optional. If you prefer to contact every lead yourself, leave the sequence switched off — the campaign will only populate your Work Queue with drafts.
Once a campaign is live you can monitor it from the campaign detail page: recorded messages, replies, conversions, and leads stopped by the auto-send logic when those events are available.
Optional WhatsApp follow-ups can run after an eligible lead has completed the campaign sequence. They require workspace permission, product enablement, approved templates, credits, valid timing, a ready WhatsApp connection, and an eligible lead.
Open Products, select the product, then use its Communication section to set both templates. You also control:
When Lead Intel recognises an opt-out reply such as "stop", "unsubscribe", "not interested", "leave me alone", or "remove me", automated outreach for that lead is stopped and the lead can be marked Not Interested. Review the recorded event in the lead timeline.
When enabled, AI can assist with a WhatsApp reply while the conversation is inside the permitted service window. The channel must be ready, the workspace must have credits, and the lead must not be stopped or handed to a human.
AI auto-reply is a separate switch from the follow-up engine. You can have automatic nudges without AI replies, AI replies without nudges, or both together — configured per product in Product Settings.
Keep your Business Knowledge field up to date and review automated behavior regularly. AI output can be incomplete or wrong, so a person should take over when the answer matters.
WhatsApp Business requires all outbound messages — any message sent to someone who has not messaged you in the last 24 hours — to use a pre-approved template. Lead Intel makes it easy to create, submit, and use these templates without leaving the app.
To create a new template:
{{1}}, {{2}}, etc. for personalisation variables such as the lead's name or business. Keep the message under 1,024 characters.Templates that are rejected by Meta usually fail because of overly promotional language or missing opt-out language. Edit the body and resubmit — there is no limit on resubmissions.
Free-form (session) messages — replies within a 24-hour window — do not require a template. Lead Intel lets you send those directly from the Outreach Log or Work Queue.
The Work Queue is your daily to-do list. It brings together replies, new outreach, and follow-ups that need attention, so you can work from one view instead of scanning spreadsheets.
When a lead replies to an outreach message, they automatically rise to the top of the Work Queue so you never miss a warm response.
The Outreach Log brings recorded sends and safely matched replies into the lead timeline, so you can review the available conversation context before following up.
When a lead is interested, Bookings makes it easy for them to take the next step without back-and-forth. Each lead can be sent a Lead Intel booking link; they click it, pick a time, and the confirmed booking is saved inside Lead Intel.
When the campaign editor supports it, a Lead Intel booking link can be included in the message draft. Review the final message before sending.
The Dashboard gives you a high-level view of your outreach performance — how many leads were found, contacted, replied, booked, and converted in the recorded data. The Funnel view helps you identify where the next experiment may be useful.
AI Insights can analyse recorded outreach history and surface patterns that are hard to spot manually — such as message angles with more replies, lead segments worth comparing, and funnel stages to investigate. Open it when you want to request an analysis; it is not a promise of a background refresh.
How to read the Insights page:
Insights become more useful as more comparable outreach is recorded. Thin history may produce limited or no analysis.
Product Settings is where you configure everything specific to one product — its name and description, AI generation preferences, outreach limits, and booking page settings. Most of this is set once during initial setup and rarely needs changing.
If your AI messages don't feel right, revisit the product description. More specific descriptions produce sharper, more personalised drafts.
Communication settings belong to either your workspace or a product. Open Workspace for shared defaults, or open Products, select a product, and use its Communication section for product-specific settings.
You need at least one send channel (email, SMS, or WhatsApp) configured before you can send or blast a campaign.
You can invite colleagues to your Lead Intel account so they can view leads, send outreach, and manage campaigns alongside you. Each person logs in with their own email and password — there are no shared logins.
To invite a team member:
All team members share the same credit balance. Admins can see a per-member breakdown of credit usage on the Credits page.
Credits are used for discovery, AI work, and outreach actions. Open Billing & plan to view your plan or buy credits, and open Usage to review how credits were used.
Common credit costs at a glance:
Where an estimate is available, the application shows it before a job or campaign action. Review the recorded charge afterwards because actual usage depends on the action and returned data.
To buy a credit top-up:
Check Usage before a large Discovery run or campaign. If an action says Payment required, open Billing & plan and confirm the plan and credit balance.
No sections match.